Email forwarded within Office365 may have DKIM breakage, Microsoft has been addressing the issue, I believe.
Mimecast is a known to me to break DKIM when forwarding. On Thu, Feb 11, 2016 at 3:53 AM, Chris Burton <ch...@7of9b.org> wrote: > Hi, > > > Did anyone notice DKIM issues (mails failing signature verification or > body > > hash not matching) with mails coming from these servers? > > We're also using exim and seeing signature_incorrect and > bodyhash_mismatch issues via > > emea01-am1-obe.outbound.protection.outlook.com > emea01-db3-obe.outbound.protection.outlook.com > EUR01-HE1-obe.outbound.protection.outlook.com > EUR01-VE1-obe.outbound.protection.outlook.com > na01-bl2-obe.outbound.protection.outlook.com > na01-bn1-obe.outbound.protection.outlook.com > > And some being relayed out via mimecast.com that show errors > validating DKIM on a *.onmicrosoft.com sender. > > Could this be a similar issue to > https://bergs.biz/blog/2014/04/10/outlook-com-breaks-dkim-signatures/ > ? > > I've only got an outlook.com account to test with (which doesn't use > DKIM) but relaying an email via smtp-mail.outlook.com without quotes > on the Content-Type charset they are added in by the time the mail > reaches our exim server. > > Chris. > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
