Mailing List Archive

[Bug 3515] empty body, corrupted header for no-spam-mails when recipient in BCC
http://bugzilla.spamassassin.org/show_bug.cgi?id=3515





------- Additional Comments From thomas.marquardt@mtf.de 2004-06-16 13:55 -------
Created an attachment (id=2040)
--> (http://bugzilla.spamassassin.org/attachment.cgi?id=2040&action=view)
Sample for corrupted and correct mail-header




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 3515] empty body, corrupted header for no-spam-mails when recipient in BCC [ In reply to ]
http://bugzilla.spamassassin.org/show_bug.cgi?id=3515





------- Additional Comments From jm@jmason.org 2004-06-16 14:53 -------
there's too many additional components there. how exactly is spamassassin run?
can you log a SINGLE message that fails,just before and just after it passes
through SA?



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 3515] empty body, corrupted header for no-spam-mails when recipient in BCC [ In reply to ]
http://bugzilla.spamassassin.org/show_bug.cgi?id=3515





------- Additional Comments From thomas.marquardt@mtf.de 2004-06-17 14:35 -------
Created an attachment (id=2049)
--> (http://bugzilla.spamassassin.org/attachment.cgi?id=2049&action=view)
concated log- config- and script-files

Spamassassin is called as application from a filter-script which is started
from postfix. The script is modified for logging the mail before/after
spamassassin. The log-output shows that spamassassin returns an empty mail. The
following sanitizer-process adds his header-statements....



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 3515] empty body, corrupted header for no-spam-mails when recipient in BCC [ In reply to ]
http://bugzilla.spamassassin.org/show_bug.cgi?id=3515





------- Additional Comments From jm@jmason.org 2004-06-17 18:21 -------
ok, that's definitely odd. ;) it seems to be working OK on 3.0.0:

$ ./spamassassin -x < tst
[...headers as before...]
X-Spam-Checker-Version: SpamAssassin 3.0.0-r20550 (2004-05-28) on
radish.jmason.org
X-Spam-Level:
X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO,
MISSING_SUBJECT,UNDISC_RECIPS autolearn=no version=3.0.0-r20550

test
--

$

does it act similarly for you when run from the command-line? if not, I'd
suspect something in the postfix environment (CPU/memory ulimits?) might be
killing it.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.