-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Invalid value separators in notification email headers #22815
Comments
One more issue of the unmaintained gomail package? |
This comment seems to be not related. Hide the content. I think the problem might not be related to gomail, but somewhat/somehow related to:
And then it's changed to I haven't read the standard yet, but it looks related to the error message: "worker.go:536: could not get message info: mail: missing '<' in msg-id" So, maybe it's time to check some standard documents 😀 |
The error message is (just a first look) because the parser wants to read a |
Description
Hi,
I've been trying out email replies merged in #22056.
They are breaking aerc (the email client) with this message:
https://github.com/emersion/go-message/blob/master/mail/header.go#L174-L181
Naturally, I thought the issue was with the client, but after digging for a while found out that gitea joins email header values (
References
,List-Unsubscribe
, probably others) using commas as separators.I don't think this is valid email. RFC5322 requires CFWS to separate header values (which is either comments or whitespace), and does not allow commas.
Could you please confirm if this is a bug?
Gitea Version
1.19.0+dev-444-g2c6cc0b8c
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker,
gitea/gitea:dev
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: