SA Bugzilla – Bug 2797
blank subject line not modified or tagged as spam
Last modified: 2004-03-01 10:16:11 UTC
The subject line on occassion is not being modified when spam has a black subject. Although the filter identifies the message as spam, and the message body is replaced, the subject is left blank and not replaced. This means that people who have a rule to put all messages with the subject line "***spam***" into a folder find these cleaned messages in their inboxes. In my limited testing it did not seem to apply when a user was in the black list. The only messages that got through were ones that were marked based on the scoring. I will try to attach some sample messages showing this behavior.
Created attachment 1589 [details] blank subject
Created attachment 1590 [details] blank subject
Created attachment 1591 [details] blank subject
Created attachment 1592 [details] blank subject
Created attachment 1593 [details] blank subject
Created attachment 1594 [details] blank subject
All attachments are in Outlook format.
it works for me. btw: we can't read outlook formatted messages ...
Created attachment 1809 [details] Text version of message with no subject line that didn't modify I am seeing this same problem with SpamAssassin 2.63. The attachment is the headers of a message with no subject that qualifies as spam, but the subject wasn't modified. Please re-open.
Subject: Re: blank subject line not modified or tagged as spam On Mon, Mar 01, 2004 at 07:16:12PM -0800, bugzilla-daemon@bugzilla.spamassassin.org wrote: > I am seeing this same problem with SpamAssassin 2.63. The attachment is the > headers of a message with no subject that qualifies as spam, but the subject > wasn't modified. I piped that message through SpamAssassin 2.63 and the Subject is rewritten just fine. Looking at the message, however, it's looking like you're passing the message through some qmail-milter thing? The X-Spam-* headers are ordered wrong (should be at the end), there's an X-Spam-Filtered header which we don't add, X-Spam-Status is missing some data, and there's no X-Spam-Checker-Version header. In short, if you're not running through one of our methods (spamassassin or spamc/spamd), the "problem" is very likely (given past history) due to whatever you're running SA through.