Two suggestions: For whitelist traffic within your private network you can use WHITELIST AUTH to whitelist users who authenticate with your servers for sending, and/or whitelist sending IPs so that all traffic from those IPs is whitelisted. This can be done by CIDR.
Regarding catching spam that forges your domain, the most successful method for us has been using SPF, weighting only on fail. By specifying in your SPF record what servers can send mail for your domain, you can effectively block forging spam, since they will not be sending from your mail servers. You can generate the text of your SPF record at spf.pobox.com, then just add that as a TXT record to your DNS domains. Darin. ----- Original Message ----- From: "Kevin Stanford" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, October 26, 2006 11:17 AM Subject: [Declude.JunkMail] Whitelist our domain on private network Is there a way to whitelist our domain within our private network but will still catch spam that is forging our domain? I have a lot of spam that is forging our domain but sometimes I get false positives with our users here and I have to sort through a huge list of spam to find them. Thanks for any help offered! Kevin --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
