https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6645
--- Comment #12 from [email protected] 2011-08-07 17:44:08 UTC --- > I used spamassassin 3.3.1 for experimenting. There the code for catching the > case # Received from x1-6-00-04-bd-d2-e0-a3-k317.webspeed.dk ... seems to > catch > the qmail-scanner line In the qmail-scanner line there is "([email protected]@188.45.128.1)" which causes the regular expression to match. Received: from 188.45.128.1 ([email protected]@188.45.128.1) by firstmailserver (envelope-from <[email protected]>, uid 201) with qmail-scanner-2.05st If I remove the "([email protected]@188.45.128.1)" from qmail-scanner's received line, spamassassin seems to correctly handle the mail and triggers the qmail-scanner-handling-code. I'm unsure whether the "([email protected]@188.45.128.1)" is a feature of the newer qmail-scanner versions (and spamassassin has not been adjusted) or if the examples in Received.pm were incomplete (only using unauthenticated sessions). --> A new qmail-scanner check would have to be moved before the x-1-6-00-04-bd-d2-e0-a3-k317 check to fire. --> The qmail-scanner-expression would have to be rewritten to something like if (!\S+ \(.{0,100}\) by \S+ \(.{0,100}\) with qmail-scanner/) originally it was if (!\S+ by \S+ \(.{0,100}\) with qmail-scanner/) the $envfrom= expressions behind might also need adjustment to contain something useful. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
