Lisa Casey wrote: > I've looked in the headers of some of my email that has been labeled as > spam, and don't have a X-Spam-Status header.
Does it have an X-Spam-Checker-Version: header? I think if you are not seeing an X-Spam-Status: header then it isn't being processed through spamassassin. Perhaps another spam processor is running instead. > The rules that get triggered appear in the X-Spam-Score line as so: > X-Spam-Score: 7.559 (*******) DEAR_WINNER,KAM_LOTTO1,KAM_LOTTO2,RDNS_DYNAMIC That isn't a SpamAssassin header. That is from MIMEDefang. http://www.mimedefang.org/ > Would it work to use this line in procmailrc by doing something like this? > > :0: > * ^X-Spam-Score: ANY_BOUNCE_MESSAGE > /lisa/mail/vbounce > > or is the fact that the score appears on the X-Spam_Score line between the > "X-Spam-Score: " and the names of the rules that were triggered going to > keep this from matching? The other stuff in the middle will keep it from matching. The procmail rule is a pattern. The pattern matches or doesn't match lines in the mail message. So to match something later in the line you would need to put a pattern in that can stretch to it. Something like this would do it for SpamAssassin. The ^ anchors at the beginning of the line. The . matches any character. The * says match any number of the previous . meaning match any number of any character any number of times. The .* makes a match against anything and is a very common idiom for matching anything. The \< matches only at the beginning of word. Putting it all together: :0: * ^X-Spam-Status:.*\<ANY_BOUNCE_MESSAGE /lisa/mail/vbounce But again, the lines you are seeing are not coming from spamassassin but from MIMEDefang and therefore this will never match. Bob
