According to Tobias Fiebig via mailop <tob...@fiebig.nl>: >Moin, > >to share some closure on this with the rest of the list; What was >ultimately the issue was an RFC8616 based DKIM-Signature header, i.e., >containing UTF-8 encoded fields (in this case, even though there were >no non-ascii characters in them). ...
If you're not sending SMTPUTF8 mail, the DKIM signature headers should be ASCII with no encoding needed. But if you are ending SMTPUTF8 mail, you can put UTF-8 directly in the header and it doesn't need any futher encoding either. Can you give an example of the signature headers that caused a problem? They just sound wrong. R's, John _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
