Error Broken Pipe

[rodrigues8]

Good afternoon,

First of all thank you to the project, it's been very useful for our structure, great work. I would like to ask for help with a slightly unusual situation, as we realize that sometimes we are encountering the following errors in the milter:

warning: milter inet: 127.0.0.1: 3690: error writing command: broken pipe

With this we had to change the milter_default_action setting to accept because before the messages were following the default and generating error 4xx causing delay in receiving.

Do you know what may be causing this? Is it something related to the load / excess of messages?

I await contact.

Kind regards.

[sbidy]

Hey, what version do you use? You can find the version number in the first log entry.

[rodrigues8]

Good evening,

Thanks for the quick feedback, we are currently using the latest version, we have just implemented this new check in our email queues.

Kind regards.

[rodrigues8]

Good night,

Another important detail I found in the logs, this mainly happens with messages received from office365 and gsuite.

Kind regards.

[sbidy]

Can you please set the log level to debug in the config and restart the milter? Are there any errors or exceptions logged while receiving the message? Can you reproduce the error? Are there any attachments within the mail?

Thank you for your support! 😉

[controljb]

Not sure if our issue is related we are using 3.4.3-1 through a yum install. Using unix sockets we will start seeing this error in our smtp logs:

Milter (macromilter): write(Q) returned -1, expected 5: Broken pipe Milter (macromilter): to error state

Not seeing anything in the macromilter logs even with debug enabled, the process seems to be running fine and the .sock exists. It only seems to be doing it for random emails not every single email.

Weve also tried this using version 3.6.1 and got the same thing.