https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6196
--- Comment #6 from Sidney Markowitz <[email protected]> 2009-09-11 16:01:53 PST --- Created an attachment (id=4533) --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4533) Tom's test case as an attachment It is obvious that it is the 'localhost.' that triggers the rule, but I can't come up with a combination of settings that for trusted_network and so on that actually makes the rule trigger on that example. If you look at the headers, you see that if mailtrap.fortressitx.com is trusted, then you trust the Received header in which it gets the mail from 'localhost.' which means that the next Received header that says that localhost received from busyagentpro.com is trusted, and that is the HELO that the rule looks at. Otherwise, if mailtrap.fortressitx.com is not listed as trusted, then you move up another two Received headers to find the one that is used, still skipping the 'localhost.'. Perhaps the parsing of Received: from busyagentpro.com (busyagentpro.com [65.98.14.130]) by localhost. (TC-3.1.040); Fri, 11 Sep 2009 17:52:26 -0400 has changed between 3.2 and the 3.3 trunk that I am testing with. I don't have a 3.2 test setup handy where I am right now to see. Are you able to run Spamassassin on the same machine that is producing this with the -t -D -L options to produce a debug log file and attach it to this bug report (as an attachment, not pasted in a comment)? If anyone has 3.2 handy to test, I'm attaching Tom's example after I cleaned up the line wrap issues from the copy and paste from the comment. To test it, try adding trusted_networks 69.72.141.51. to your local config, as I don't see how the rule can possibly trigger without that. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
