On Aug 6, 2014, at 7:21 AM, A. Schulze via dmarc-discuss <[email protected]> wrote:
> > Hello, > > yesterday I noted that a testmessage to an aol.de account was delivered to > the spam-folder @AOL. > I guess dkim=fail for that message was the reason. > > Some testmessages later i found AOL does not announce the 8BITMIME smtp > extension. > My outbound mta has to recode the content and break the already existing > signature. > > * is there a reason AOL does not support 8BITMIME? > RFC1426 is 20 years old and updated by RFC6152 in 2011 It's an optional service extension and they're under no obligation to offer it. I thought I'd seen them offer it in the past, but maybe not. > How do other handle that situation? Send 7 bit messages; we have quoted-printable encoding for that. 8BITMIME isn't universally supported, so it's not a great thing for your message composition code to assume. > Do that recoding also break some opaque S/MIME signatures? It shouldn't. S/MIME is quote robust. > > I'm confused... DKIM isn't the most robust way of signing email, but it can work quite reliably if you're careful about how you structure your mail so as to avoid reformatting or recoding. Using quoted-printable encoding for all text elements is one of the easiest ways to avoid many of the potential problems. Cheers, Steve _______________________________________________ dmarc-discuss mailing list [email protected] http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
