http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4988
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2006-07-15 20:43 -------
ok, good news -- it wasn't produced by SpamAssassin, it comes from
the formail command. See:
: jm 270...; formail -d -I "From " -a "From " -s < ~/DL/bug4988-message.txt > o
: jm 271...; diff ~/DL/bug4988-message-mbox.txt o
1,4c1
< From [EMAIL PROTECTED] Sat Jul 15 00:39:27 2006
< Received: from power2u.zmi.at [195.202.170.130]
< by localhost with IMAP (fetchmail-6.2.5)
< for [EMAIL PROTECTED] (single-drop); Sat, 15 Jul 2006 00:39:27 +0200
(CEST)
---
> From [EMAIL PROTECTED] Sat Jul 15 21:39:05 2006
55a53
> X-UID: 14695
111c109
< From [EMAIL PROTECTED] Sat Jul 15 00:39:27 2006
---
> From [EMAIL PROTECTED] Sat Jul 15 21:39:05 2006
(in other words, it's missing the harmless fetchmail Received hdr,
and the datestamps in the From lines are different -- but the
second, problematic From line was added.)
Here is the culprit -- formail's "-d" switch:
-d Tell formail that the messages it is supposed to split need not be in
strict mailbox format (i.e., allows you to split digests/articles or
non-standard mailbox formats). This disables recognition of the Con-
tent-Length: field.
remove that switch, and it works fine. ;)
Michael, would it be possible to alter the fetchmail command line accordingly?
Regarding the other issue: what mass-check should do -- I think we can
simply close this bug, since this is an "artificial" issue created entirely
by that formail command; it wasn't caused by the "real" spam itself in any
way. Marking INVALID.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
