robbie_woodley
asked on
Exchange 2007 Transport Rule Not Working
Hello Experts,
I have set up an Exchange 2007 transport rule that should be rejecting email messages to a specific member inside our environment from anyone outside our environment. It should prepend the Subject line, send a bounce message, and silently drop the message...but it is doing none of these. I have tested sending a message to this user from a Yahoo! address and it routes to him properly. I have included a screenshot of my settings, the rule is enabled...if you need any further info just let me know.
Thanks!
I have set up an Exchange 2007 transport rule that should be rejecting email messages to a specific member inside our environment from anyone outside our environment. It should prepend the Subject line, send a bounce message, and silently drop the message...but it is doing none of these. I have tested sending a message to this user from a Yahoo! address and it routes to him properly. I have included a screenshot of my settings, the rule is enabled...if you need any further info just let me know.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I do have several other transport rules and they are working. I did wonder about the time to take effect, I created this on Friday and waited over the weekend and it is still not working today. Will restarting the MsexchangeTransport service have any effect on our email uptime? We have a large enterprise and cannot take down email for any time. Thanks!
If you have multiple HT servers in the same AD site then they will automatically be fault tolerant. The only thing you need to worry about us if your inbound Internet mail is pointing at a single HT. When the transport service restarts on the inbound HT, external servers will not be able to send to that server and will look at sending to other MX records in your domain.
That said, the Transport service restarts really quickly so there is minimal downtime anyway.
ASKER
I recreated the rule, restarted the service and tested and now working properly.
Thanks for the update and the points
ASKER