Page 1 of 1

Milter "can't read SMFIC_OPTNEG"

Posted: 03 Mar 2021 19:14
by pingu
Hello,

I run a high traffic server and lately I've been seeing these errors in the Maillog just after the servers stops processing incoming emails:

Code: Select all

Mar  3  postfix/cleanup[152480]: warning: milter inet:127.0.0.1:8891: can't read SMFIC_OPTNEG reply packet header: Success
Mar  3  opendkim[1618]: OpenDKIM Filter: accept() returned invalid socket (Numerical result out of range), try again
Netstat shows:

Code: Select all

netstat -an | grep 8891
tcp      126      0 127.0.0.1:8891          0.0.0.0:*               LISTEN     
tcp       17      0 127.0.0.1:8891          127.0.0.1:41374         ESTABLISHED
tcp        0      1 127.0.0.1:41426         127.0.0.1:8891          SYN_SENT   
tcp       17      0 127.0.0.1:8891          127.0.0.1:41156         ESTABLISHED
tcp        0      0 127.0.0.1:41114         127.0.0.1:8891          FIN_WAIT2  
tcp       17      0 127.0.0.1:8891          127.0.0.1:41444         ESTABLISHED
tcp       18      0 127.0.0.1:8891          127.0.0.1:40706         CLOSE_WAIT 
tcp       17      0 127.0.0.1:8891          127.0.0.1:41112         ESTABLISHED



After I reboot the eFa-project servers, the emails resume processing and the incoming queue starts to go down in count.
I've looked everywhere and cannot find the cause for this.

Does anyone here have any experience with the "can't read SMFIC_OPTNEG" error?

Re: Milter "can't read SMFIC_OPTNEG"

Posted: 10 Jun 2021 20:35
by pingu
In case someone bumps into this thread:

I believe this to have been an issue with OpenDkim.



I noticed that since I run a high load Efa-project server, and my DNS is hosted outside this server, I enabled "query cache" in my opendkim.conf options.
This seems to improve stability of Opendkim crashing.

Re: Milter "can't read SMFIC_OPTNEG"

Posted: 15 Jun 2021 11:43
by scl402a
I just started to have the same issues on 2 of my 4 EFA appliance. Config are all identical. Since disabling DKIM, seem to be stable. Hope to get a bug fix soon.