You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example the mail originated from example.com, but was delivered through Amazon SES (which added it's own DKIM signature).
In this case this leads to a warning that the DKIM signature for amazonses.com does not belong to this domain (supposedly example.com).
Other DKIM verification tools (like Google Header Analyzer) conclude that everything is fine. So I guess only one of these two DKIM signatures is considered by the plugin, which leads to the incorrect warning.
The text was updated successfully, but these errors were encountered:
Note that the add-on does verify all DKIM signatures, but it will only show one signature. Mainly because of space reasons in the GUI.
More about it in #48 (comment).
My guess is that the signature for example.com fails to verify. The add-on will then consider the valid signature from amazonses.com the "better" one to show.
As part of #160, which is planned for the next version, all DKIM signatures will be probably be visible in the GUI. But still not directly in the header. Instead I plan to extend the pop-up for the DKIM button in the header, that currently only has buttons to trigger actions.
When a mail contains multiple DKIM signatures, the plugin seems to only parse one of them (the first/last). Consider this mail header...
In this example the mail originated from example.com, but was delivered through Amazon SES (which added it's own DKIM signature).
In this case this leads to a warning that the DKIM signature for amazonses.com does not belong to this domain (supposedly example.com).
Other DKIM verification tools (like Google Header Analyzer) conclude that everything is fine. So I guess only one of these two DKIM signatures is considered by the plugin, which leads to the incorrect warning.
The text was updated successfully, but these errors were encountered: