Assigning SCL to messages scanned by 3rd-party antispam filters

The Unix/Linux/Security folks in your organization don't trust Exchange to do the filtering. They insist on using open source anti-spam software, such as SpamAssasin on the non-Exchange SMTP gateways. After tweaking it for a number of weeks, they are able to make it work the way they want it to, or are close to it.

Their solution is to insert an X-header in messages that looks like this:

X-Spam-Status:yes

That's it. Their job ends there.

As the Exchange team/administrator, your job is to ensure messages with that header end up in users' Junk Mail folder.

Now what?

http://exchangepedia.com/blog/2008/01/assigning-scl-to-messages-scanned-by.html

Exchange.2007.Assigning.SCL.to.Messages.Scanned.by.3rd.Party.Filters.pdf (164.02 KB)


 
Comments are closed.