-
Notifications
You must be signed in to change notification settings - Fork 35
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
Exception (NS_ERROR_MALFORMED_URI) while looking for favicon #229
Comments
Thanks a lot for reporting. Seems to be a bug how the quoted AUID ( Note as ARHs that cause this bug do not seem to be common, I do not plan to fix it in an 3.x.x version, but only in the upcoming 4.0.0. |
Note that if ARH reading is not enabled just to avoid local DKIM verifications, try disabling Reading the Authentication-Results header replaces the add-ons verification in the advanced option as a woraround, |
Now I'm running DKIM Verifier 4.0.0pre4 of December 29, 2020, with TB 78.6.0 . I tried to open the same message that caused that error. Although I have debug enabled, the error console shows only this:
FWIW, the From: line was:
Curiously, I cannot reach DKIM Verifier's options. It doesn't show in Tools/ Add-on Options. I have to use Config Editor and search for dkim_verifier. I have this (using grep on prefs.js):
I'm not clear what should I try to change... |
I only go to fix this issue yesterday, so in 4.0.0pre4 it is still broken. Just uploaded a 4.0.0pre4.1 at #199 (comment), there the issue with quoted AUID is fixed. The issue you just reported seems to be something else, will look into it. Regarding the options: The |
The error you saw seems to be a duplicate of #232, which should also be fixed in 4.0.0pre4.1. |
Yup, version 4.0.0pre4.1 of February 8, 2021 works well. Thank you very much! I copy some text from the console, in case it's useful.
|
Thanks for letting me know that it work now. Will close this issue. The last log you posted seems fine. The |
Here's the log:
A-R fields seem to parse correctly:
Signatures:
The text was updated successfully, but these errors were encountered: