Closed Reiner030 closed 8 years ago
The DKIM_SIGERROR_CORRUPT_BH
error is caused by a modification of the e-mail body, and not not a problem in the headers. Adding a header can only cause a problem if the DKIM signature specially specifies that a certain header is not allowed to be added.
The server has no problem verifying the e-mails, because the modification happens afterwards. DKIM was never meant to be checked by the e-mail client, so thinks like this can happen. As you can see in the FAQ, Microsoft is not the only one doing so.
parameter field which email headers should be filtered out in email (mime-parts/bodies)
As I already stated above, the headers are not the problem in the particular case you posted. Even if a header is causing the problem, it will be because it was modified. Simply ignoring the header is not possible in this case.
I already tried ones to revert all changes done by Outlook.com, with are probably the same as in Office365. But I soon realized that some changes will be very hard to revert back, so I gave up. There still exist a hidden preference from this (extensions.dkim_verifier.error.contentTypeCharsetAddedQuotes.treatAs
). Activating it may result in at lest a few more e-mails verifying without error.
notify body changes only as warning / full ignore? I think this would make any result pretty much worthless. So unless someone convinces me otherwise, I don't think this will be included.
use found "Authentication-Results" only for verification in TB This is already included in the Add-on.
Hi,
with Office365 I see often on emails with attachment or mixed plain/html content (=> multipart mime emails) an DKIM warning by your addon while the headers show that incoming mail servers checked them without differences found:
e.g.:
and I think this comes from the header in each mail part like:
This is from TB debug log:
It would be nice if such header addition could be optionally ignored by e.g. one or multiple of these ideas: