jerry.benton at mailborder.com
Tue Mar 3 15:16:10 GMT 2015
Or just enable recipient verification on your end and let 365 deal with the backscatter.
> On Mar 3, 2015, at 9:33 AM, James Nelson <James.Nelson at vgt.net> wrote:
> I also use office 365 for an edge filtering. Mine is synchronized with my internal active directory via the Microsoft Dirsync tool, but aside from the additional load you will place on your internal servers by not offloading directory based blocking at the office 365 level, there's not technically any harm in what you describe, as long as you configure your internal servers not to send NDRs, which in addition to creating additional traffic can be used by spammers for address validation
>> On Mar 3, 2015, at 8:22 AM, Denis Beauchemin <Denis.Beauchemin at usherbrooke.ca> wrote:
>> We are about to move our MX to the cloud in Microsoft 365. The way it would work would be to scan the emails there and then deliver them to our servers.
>> The problem is that we can't for the moment tell MS365 which email addresses are valid and which are not (the data is in an LDAP server that is not synchronized with our AD). Thus MS365 will be forwarding all harmless emails to our internal servers who will reject invalid email addresses.
>> I seem to remember this is really not a good idea but I can't remember why. Can someone shed some light on this please?
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> Before posting, read http://wiki.mailscanner.info/posting
>> Support MailScanner development - buy the book off the website!
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> Before posting, read http://wiki.mailscanner.info/posting
> Support MailScanner development - buy the book off the website!
More information about the MailScanner