So I checked, we do support it, we just don't announce it as part of the ehlo response, which of course means that no one knows we support it. I know we had some legacy reasons for disabling 8BITMIME and a few other things in our ehlo response, but I'll ask to see if we can turn them back on.
PAUL ROCK Senior Programmer/Analyst | AOL Mail P: 703-265-5734 | C: 703-980-8380 AIM: paulsrock 44900 Prentice Dr. | Dulles, VA | 20166-9305 On Aug 6, 2014, at 10: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 > > How do other handle that situation? > Do that recoding also break some opaque S/MIME signatures? > > I'm confused... > > Andreas > > _______________________________________________ > 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)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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)
