Outgoing email flagged as spam then deleted
admin at thenamegame.com
Thu Jul 27 21:01:20 IST 2006
Ok, I believe I can add 127.0.0.1 to spam.whitelist.rules. That should work.
Don't have a problem with user abusing forms as we have strict mod_security
rules that prevents these things. Nice thought though.
From: mailscanner-bounces at lists.mailscanner.info
[mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Alex Neuman
van der Hans
Sent: Thursday, July 27, 2006 3:39 PM
To: MailScanner discussion
Subject: Re: Outgoing email flagged as spam then deleted
Michael S. wrote:
> We are seeing a lot of users emails being deleted, outbound because
> its scoring higher than our threshold, 5.0.
> I though messages from 127.0.0.1 outbound was not checked? It seems
> like it is. Which setting in MS prevents
> Outgoing emails from 127.0.0.1 from being checked for spam?
The same that prevents outgoing emails from any IP from being checked
for spam. Rulesets. Look for "spam checks = " and implement a ruleset.
You *may* want to hold off on *not* scanning messages sent from
127.0.0.1 if, for example, you host a webserver with forms. Some web
forms can be tampered with in order to make them send out spam. Unless
you've taken good care not to allow MIME injection within your web
forms, you could be vulnerable
Good luck with that in any case.
> Eg Jul 27 10:12:02 orion MailScanner: Message 1G66an-000Equ-O1
> from 127.0.0.1 (user at orion.server.com) to domain.com is spam,
> SpamAssassin (score=5.216, required 3.5, BIZ_TLD 2.01, HTML_90_100
> 0.11, HTML_MESSAGE 0.00, HTML_MIME_NO_HTML
> _TAG 1.08, HTML_SHORT_LENGTH 1.57, MIME_HTML_ONLY 0.00, NO_RELAYS
> -0.00, X_PRIORITY_HIGH 0.43)
MailScanner mailing list
mailscanner at lists.mailscanner.info
Before posting, read http://wiki.mailscanner.info/posting
Support MailScanner development - buy the book off the website!
More information about the MailScanner