>>> support <[EMAIL PROTECTED]> 12/11/08 2:52 AM >>> Prempting some responses: What about external remote workers? What about those who email stuff to themselves? I hear this kind of thing all the time when people moan about spoofing.
On Wed, 2008-12-10 at 12:19 -0500, Kevin Parris wrote: > You do not have a SpamAssassin problem, you have a Communigate problem. > Present this issue to your support resources for that product. > > The basics of what you want to do are something like this: > > When a message is arriving from the internet, and has your own domain in the > Return-path, it should be REJECTED immediately. The detection of this > condition, and the Rejecting of the message, should occur entirely within > Communigate so that the item does not survive long enough to be presented to > SA for analysis. > > I believe the common wisdom is something like: your own remote users will be configured for some sort of VPN or other authentication mechanism, therefore the mail they send will not be "arriving from the internet" thus the mailserver can distinguish their items from those that need to be rejected. People who email stuff to themselves will either be local in the office, or remote and authenticated as above, therefore the items they generate will not be "arriving from the internet" thus the mailserver can distinguish them from those that need to be rejected. If you have a mailserver that is not able to make this distinction, or you have remote users who do not have a VPN or other authentication mechanism, you should consider replacing or reconfiguring some components in your facilities.
