-
Notifications
You must be signed in to change notification settings - Fork 103
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
ARC :: signer died because of a message #988
Comments
Hi @Philippe34 , Could you please attach the message that caused death of bulk daemon? And, if possible, please tell the versions of "Mail-DKIM" and "Mail-AuthenticationResults" Perl modules. |
Hi @Philippe34 , Could you please apply this patch and check if the problem will be solved? |
Hi @ikedas , I've applied the patch to Message.pm I can check there is no disgression and ARC-Seal, ARC-Message-Signature and ARC-Authentication-Results are in the headers when Message.pm is patched. It seems goods for me. Thank you very much @ikedas, and when the sympa 6.2.58 will be released, i will upgrade to this version. |
ARC::Signer died because of a malformed "Authentication-Results:" header field (#988)
@Philippe34 , thank you for reporting bug and confirming fixes! |
ARC features is on in my sympa.conf since several months. But a few days ago, a message could make an issue in sympa which could not send any messages anymore.
Version
6.2.52
Installation method
It is a centOS 7.8.2003 and I installed sympa with rpm repository
Expected behavior
Yesterday, an user need help because the subscribers does not receive any messages since last week.
I did not know, sympa processes were always running for me.
I could notice that in Aug 27 09:37, a message sent to a list made an issue in Mail::AuthenticationResults::Parser and the consequences were that sympa didn't deliver any messages since a week.
I was very annoyied for the users who could lost important messages.
Actual behavior
How did I solve this issue in the instant ?
I disabled arc feature in sympa.conf
arc_feature off
Then I restarted sympa and immediatly all the suffering messages were delivered.
I reenabled arc_feature in sympa.conf, but, I disabled this feature to the list at the origin of the problem
Do you this is enough for this incident did not happen again in the futur ?
Is there a possibility to prevent this issue in sympa code ?
Additional information
From the archives in sympa, if you want, I can provide the message which made the issue.
Sympa logs
The text was updated successfully, but these errors were encountered: