Best practice - limiting SMTP traffic to email server

Whenever I have utilized a cloud-based spam filtering service, I have always adjusted the SMTP rule on the firewall to only accept traffic from said service. However, I have recently seen docs/articles directing to adjust your email server to do this task instead (i.e. locking down the receive connector on the Exchange server).

My thinking to this would be that the less work the server has to do the better, and it seems a job more suited for the firewall anyway.

Am I missing something? What would be the advantage(s) to having the email server handling this task, over the fw?


Who is Participating?
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
I think the reason that a lot of documents say to get Exchange to do it, is simply because a lot of sites are using "home" type routers supplied by ISPs which are unable to restrict the traffic at the firewall level. Many sites will continue to use those routers because if they use something else ISP support stops if they have an internet connection. They keep the router to keep support.

These are the same sites that are unable to block port 25 traffic outbound for anything but Exchange and then get blacklisted.

If you are able to do the restricting on the firewall, then I would do it there. Also block all other SMTP traffic on the firewall as well.

tnormanAuthor Commented:
Thanks for the time on this one, Simon.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.