On Mon, Feb 24, 2014 at 09:50:30AM -0500, Nigel Horne wrote: > >>I mailed a simple e-mail to myself and it was scanned. Why? Everything > >>I can find on the web says that by default this e-mail should not be scanned > >>but it is, look at the headers: > >This is under your control when you configured spamassassin to run on > >your incoming email. SpamAssassin itself is simply the mail scanner. > >It only classifies messages. The configuration of what email you send > >into it is up to other additional software. > > > >How did you configure it? > > I used the supplied Debian configuration to Spamassassin, which is > why I'm reporting it. But still, any help would be really > appreciated.
There would be no way for spamassassin to recognize a mail as originating from localhost without scanning it. If you don't want spamassassin to look at locally originated mail, that's a local configuration issue. Or, to put this another way, by default spamassassin doesn't see any mail at all. It's entirely up to you to pipe mail to spamassassin or spamc/spamd. If you choose to pipe locally generated mail to the filter, there's nothing spamassassin can do to avoid seeing it. If milter includes rules by default that pass mail through spamassassin, then you may want to follow up with the milter maintainers to ask them about changing that behavior. Note that spamassassin did recognize that the message originated within your local environment, which is why it triggers the ALL_TRUSTED rule. That rule has a negative spam score and helps to ensure that locally generated mail isn't flagged as spam regardless of content. You could even consider looking at "short circuiting" based on that rule. See the references to Mail::SpamAssassin::Plugin::Shortcircuit in /etc/spamassassin/local.cf and man Mail::SpamAssassin::Plugin::Shortcircuit noah
signature.asc
Description: Digital signature
