Thomas Young
New Member
- Outlook version
- Outlook 2013 64 bit
- Email Account
- Office 365 Exchange
A majority of my clients are running SBS 2011 and Exchange 2010. We've begun rolling out Microsoft Exchange Online Protection (EOP) to our clients because it's less of an administrative overhead for us and is an excellent SPAM and anti-virus solution.
I have found most of the documentation published by Microsoft (TechNet) for Configuring EOP, that includes but not limited to Best Practices, Anti-Spam Protection, data center IP addresses used by EOP, Configuring Content Filter Policies for Junk Email, etc. What I'm unable to find it anything that suggests, recommends or flat out says disable the on-premises anti-spam features from the hub transport. I opened a case with Office 365 to ask this question and they basically refused to advise me on how to configure Exchange 2010 citing it was out of their scope. They did said it was my choice whether or not I wanted to continue to leave those features enabled. However, I cited the fact that because I'm using it in a hybrid scenario that their support extends to local server configuration and that their documentation online clearly shows it's within their scope, e.g. http://technet.microsoft.com/en-us/library/jj837173.aspx. They simply would not listen and said I would need to pay to speak with the Exchange team. A very disappointing experience but not surprising for a company that used to have the best interests of SMB IT support companies in mind. Anyway, not to digress, my receive connector only receives email from EOP so I don't accept SMTP traffic directly to my client's public IP address and therefore wouldn't need the anti-spam enabled. Does anyone know of any published documentation that states the on-premises anti-spam features can safely be disabled once EOP has been implemented and is the only source of inbound mail delivery? I don't see any reason to leave it enabled simply because it seems to be redundant and it has caused some issues with false positives.
I thank everyone in advance for their advice.
I have found most of the documentation published by Microsoft (TechNet) for Configuring EOP, that includes but not limited to Best Practices, Anti-Spam Protection, data center IP addresses used by EOP, Configuring Content Filter Policies for Junk Email, etc. What I'm unable to find it anything that suggests, recommends or flat out says disable the on-premises anti-spam features from the hub transport. I opened a case with Office 365 to ask this question and they basically refused to advise me on how to configure Exchange 2010 citing it was out of their scope. They did said it was my choice whether or not I wanted to continue to leave those features enabled. However, I cited the fact that because I'm using it in a hybrid scenario that their support extends to local server configuration and that their documentation online clearly shows it's within their scope, e.g. http://technet.microsoft.com/en-us/library/jj837173.aspx. They simply would not listen and said I would need to pay to speak with the Exchange team. A very disappointing experience but not surprising for a company that used to have the best interests of SMB IT support companies in mind. Anyway, not to digress, my receive connector only receives email from EOP so I don't accept SMTP traffic directly to my client's public IP address and therefore wouldn't need the anti-spam enabled. Does anyone know of any published documentation that states the on-premises anti-spam features can safely be disabled once EOP has been implemented and is the only source of inbound mail delivery? I don't see any reason to leave it enabled simply because it seems to be redundant and it has caused some issues with false positives.
I thank everyone in advance for their advice.