-
Notifications
You must be signed in to change notification settings - Fork 56
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
Opendmarc crashes with 'milter unix:/run/opendmarc/opendmarc.sock: can't read SMFIC_BODYEOB reply packet header: Application error' #213
Comments
What opendmarc version? Config? How to reproduce? |
We currently use opendmarc version 1.4.1.1-r2
AuthservID boss.staszic.waw.pl Remaning values are set to its defaults
It crashes while processing email from list.uvm.edu. Unfortunately we haven't intercepted that email. Everything we know is attached in mail log above |
I got today also such a message: Postfix's milter log:
Opendmarc (Version 1.4.0~beta1+dfsg-6+deb11u1) has logged:
This message was sent from xxx.outbound.protection.outlook.com. We temporary suspended the milter result in case of an error.
did not bypass the problem. |
I am running into the same issue and from what I can see, it affects only certain senders (most of them seem to be using Exchange Online). Maybe it is caused by some of the headers Microsoft adds to the message or the double-DKIM signatures of outbound.protection.outlook.com? |
Ironically despite running Postfix, I'm seeing this in announce messages from the Postfix Announce mailing list: Mar 9 16:41:10 tornado.reub.net postfix/cleanup[7072]: warning: milter inet:localhost:8893: can't read SMFIC_BODYEOB reply packet header: Application error And it dies like this: Mar 9 16:41:10 tornado.reub.net kernel: opendmarc[7147]: segfault at 0 ip 00007fe74a4b44f0 sp 00007fe7492691b8 error 4 in libbsd.so.0.11.7[7fe74a4ac000+c000] likely on CPU 1 (core 0, socket 1) It's killing opendmarc every time it tries to send a message to me which then causes all sorts of problems because with the milter dead - everything else then starts being deferred. |
Possible fix #183 |
Find mail logs attached below:
In kernel log I found the following:
[35266.313292] opendmarc[19208]: segfault at 0 ip 0000148cd4fc76d0 sp 0000148cc7dd9138 error 4 in libbsd.so.0.11.3[148cd4fbf000+c000]
The text was updated successfully, but these errors were encountered: