You'll avoid the forgery problem outright.
At 04:43 PM 1/21/2004, Brad Hazledine wrote:
Has anyone written a rule that catches mail supposedly sent by yourself to yourself?
Example here...
Received: from WIN-SYEZX91ADBP ([61.50.222.200]) by fargo.caledoncard.com (8.12.10/8.12.10) with SMTP id i0L6pDT5006761 for <[EMAIL PROTECTED]>; Wed, 21 Jan 2004 01:51:14 -0500 Message-ID: <[EMAIL PROTECTED]> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
I whitelist everything from our own domain due to the fact that reports were constantly getting marked as spam for one reason or another. Therefore this triggers the whitelist and the spam gets through. It is starting to become more frequent.
I have tried to write a rule that says "if it is from yourself to yourself but not received from your server then clobber it".
However, the rule seems to pick up the "by fargo.caledoncard.com" in the header and thinks that all is well.
If anyone out there has encountered this and found a way around it then I would appreciate some input.
Thanks.
Brad
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
