Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internal error on emails from spothero.com #321

Closed
Pascal666 opened this issue Jul 22, 2022 · 3 comments
Closed

Internal error on emails from spothero.com #321

Pascal666 opened this issue Jul 22, 2022 · 3 comments
Assignees
Labels
Milestone

Comments

@Pascal666
Copy link

v5.1.0 on TB 91.11.0 (64-bit)

DKIM_Verifier.Verifier FATAL verifier.mjs.js:1335:8
_handleException moz-extension://c59aead9-8e8f-4b9a-827f-4513ce0adfbe/modules/dkim/verifier.mjs.js:1335
_processSignatures moz-extension://c59aead9-8e8f-4b9a-827f-4513ce0adfbe/modules/dkim/verifier.mjs.js:1378

@lieser
Copy link
Owner

lieser commented Jul 23, 2022

Thanks for the report. Unfortunately the error message does not provide enough information to see what is going wrong.

Could you please send me an affected email as a saved eml file via email (lieser+dkim@posteo.net)?

@lieser lieser self-assigned this Jul 23, 2022
@lieser lieser added the bug label Jul 23, 2022
@lieser
Copy link
Owner

lieser commented Jul 23, 2022

Thanks for sending me the example mail.

The problem is the empty Reply-To: header. Will have a look if that is valid.
But regardless of that, how the add-on handles an invalid Reply-To header needs to be improved.

A workaround would be staying with the 5.0.0 version for now, as the Reply-To header is only read as part of the new warning about unsigned headers.

The reason for the incomplete error message is that how Thunderbird shows log messages of add-ons in the error console is broken. Using the debugging view of the add-on shown a more useful message. Will update the wiki about this problem.

@lieser lieser added this to the 5.1.1 milestone Aug 11, 2022
lieser added a commit that referenced this issue Aug 15, 2022
@lieser
Copy link
Owner

lieser commented Aug 15, 2022

This should be now fixed in the 5.1.1 version.

@lieser lieser closed this as completed Aug 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants