Start sending after client was idle for a while: tcp write: broken pipe

[phev8]

Hi!

We observed an issue when starting to send a batch of emails using a pool, when the client was idle for a while. In this case, the first couple of emails (50-200) are failing with the error "broken pipe". After that, it starts to send the messages normally again.

write tcp <local server ip> -> <ip-of the mail-server>: write: broken pipe

The setup is using exchange mail servers (list of pools initialised as shown in the documentation).

Is there any configuration option/recommended use, we can prevent this happening, or tell the client it should renew the connection?

[gregseb]

I'm also seeing this.

[al-ship]

It effects me too.

[oblq]

Me too.

[Kryan90]

For anyone else with this issue, I switched to this fork that has some better pooling and haven't hit this since: https://github.com/knadh/smtppool