bve32k Posted March 8, 2012 Posted March 8, 2012 Hello all, We currently have an issue with someone sending emails to users at our company. Right now we are trapping the emails into a folder as a txt file (so the users are not able to view the emails), but is it at all possible for me to create a new email address and have all those emails from the external user forwarded to the new email account? This would need to be done globally. Any pointers would be appreciated. Thanks, Ken
mattx Posted March 8, 2012 Posted March 8, 2012 Depends on what Exchange ver you are using - if 2007 SP1 then I'm sure you can using the transport rules. Controlling Email Messages using Exchange's Transport Rules We tend to stop this sort of thing even before it hits exchange as we have Watchguard in place.
bve32k Posted March 8, 2012 Author Posted March 8, 2012 We currently have Exchange 2003. My boss still wants to look over the emails that are being sent, but does not want the other employee's to see the emails.
MatthewL Posted March 8, 2012 Posted March 8, 2012 Some sort of black list/email filtering device is what you want where they are held. It's not my area of specialism so sorry to be vague.
PiqueABoo Posted March 8, 2012 Posted March 8, 2012 Exchange 2003 you can make an SMTP event sink (ISMTPOnArrival) with VBS or JS. Haven't made one for this kind of scenario, but I expect you can check the mail sender and if it matches "someone's" address, change the recipient to a specific mailbox
sukh Posted March 9, 2012 Posted March 9, 2012 Doing this natively with Exch 2003 isn't possible as it is with Exch 2007/2010 using transport rules. An archive event sink MAY work but you will need to create a custom script around to do this, using the archive event sink on it's own wont work. Got budget for a gateway? You could use a 2010 Edge server and you the transport rules on that if you wish.
PiqueABoo Posted March 9, 2012 Posted March 9, 2012 Archive? If it's mail from an external source it's normally arriving via SMTP and an SMTP OnArrival event sink is the obvious choice surely? As above I have made them for other scenarios and :checks API:: you can rewrite envelope receipients.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now