Seperating emails addressed to old domain? RSS Back to forum
@matt.reed:
Hi Matt,
ORF could maybe do this using a relative simple custom External Agent, but I think you can archieve this a lot easier using Exchange Transport Rules, assuming you run Exchange 2007, 2010 or 2013. Find more about Transport Rules at http://technet.microsoft.com/en-us/library/bb125138(EXCHG.80).aspx (from PowerShell) and at http://technet.microsoft.com/en-us/library/bb123927(EXCHG.80).aspx (from Exchange Management Console). One notable limitation of this approach is that Transport Rules work with the P2 recipient list (that is, recipient information from the email headers, which may be different from the P1 recipient information and this latter is used for actually delivering the email), so some spam that uses different P1 and P2 recipient may slip through this redirection.
As for the External Agent approach, this would require you to write a Windows script (e.g. in VBScript or JavaScript) or a small program that examines the recipient list received via command line and returns the a different exit code if the recipient is in your old domain. The Vamsoft Self-Spam Protection Agent is an example of such agent: http://vamsoft.com/support/docs/articles/how-to-blacklist-self-spam (the code is explained at http://blog.vamsoft.com/2009/01/06/self-sending-spam-2/)
We kept our old domain active when changing to our current domain. I noticed that we get a large amount of spam addressed to our users at the old domain.
How can I redirect all email that is addressed to our old domain to a separate email address or public folder during the On Arrival testing?
I want to review these for spam and ask the users to send a notification of their new email address to any legitimate sender still using our old domain.
One way to do this is to have a separate Recipient blacklist for Before Arrival vs. On Arrival.
Can you think of any other way to do this?