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

Auth results from google mails not correctly read #135

Closed
bonanza123 opened this issue Jan 12, 2019 · 3 comments
Closed

Auth results from google mails not correctly read #135

bonanza123 opened this issue Jan 12, 2019 · 3 comments
Assignees
Labels
Milestone

Comments

@bonanza123
Copy link

bonanza123 commented Jan 12, 2019

For most of the mails coming in via google (gmail or one of google services itself), the A-R does not seem to be read correctly.

E.g. for the header

Authentication-Results: mail-in-2.itc.mail.com; spf=Pass smtp.mailfrom=user@gmail.com; dkim=pass (signature verified) header.i=@gmail.com

The plugin in thunderbird says: No Signature

Here some output from the log in debug mode:

16:43:51.617 1/12/2019, 16:43:51	DKIM_Verifier.AuthVerifier	ERROR	Ignoring error in parsing of ARH: Error: Parsing error (resource://dkim_verifier/ARHParser.jsm:292:9) JS Stack trace: match@ARHParser.jsm:292:9
parseResinfo@ARHParser.jsm:201:15
_ARHParser_parse@ARHParser.jsm:170:21
getARHResult@AuthVerifier.jsm:252:10
_authVerifier_verify/promise<@AuthVerifier.jsm:138:20
 1 AuthVerifier.jsm:254
lieser added a commit that referenced this issue Jan 13, 2019
@lieser lieser self-assigned this Jan 13, 2019
@lieser lieser added the bug label Jan 13, 2019
@lieser lieser added this to the 2.0.1 milestone Jan 13, 2019
@lieser
Copy link
Owner

lieser commented Jan 13, 2019

Thanks a lot for reporting this issue. The problem was the casing in spf=Pass (the ARH RFC only specifies lower case results, but old SPF RFCs used mixed case).

The upcoming 2.0.1 will also accept the mixed case results specified in the old SPF RFC.

@lieser lieser closed this as completed Jan 13, 2019
@bonanza123
Copy link
Author

@lieser thanks so much for the swift fix. Is there an ETA for the 2.0.1 release?

@lieser
Copy link
Owner

lieser commented Jan 15, 2019

I'm currently planning to release it in a few days latest. Note that review on ATN will probably take at least a few days, if not weeks, so automatic update may take more time.

But you will be able to manually download it here on GitHub before that already. You can watch the repository for releases to get a notification.

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