https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6450
--- Comment #4 from David Pottage <[email protected]> 2010-06-14 10:04:21 EDT --- > Agreed. Why are you passing purely-internal mail through SA in the first > place? > This is not the only rule that such a comment could apply to. > > Your MTA should have rules to bypass SA completely on internally-generated > email, especially on administrative emails of this sort. I am processing all mail through SA, as that is the simplest setup, and is the default for Ubuntu. You are correct that it is not the optimal way to do things, but I have plenty of cycles to spare, so I don't want to complicate the config of my MTA unless there is a need. > A question, though, so I'm not just saying "it's not my problem": do those > messages hit ALL_TRUSTED? I'd be willing to add !ALL_TRUSTED to the meta. Those messages do hit that rule. The complete analysis I am getting is: Content analysis details: (5.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 HTML_MESSAGE BODY: HTML included in message 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.4752] 0.7 MIME_HTML_ONLY BODY: Message only has text/html MIME parts 0.4 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 4.3 TO_EQ_FM_HTML_ONLY To == From and HTML only -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
