Klaus Engelmann put forth on 8/20/2010 11:25 AM: > Hi list, > > I searched the forum looking for some ideas about the following error > that is growing increasingly in my POSTFIX deployment: > > Aug 20 08:41:40 prometeu postfix/smtpd[16568]: lost connection after > EHLO from mail2.netpoint.com.br[187.16.24.50]
I doubt this has anything to do with load. Look at _all_ the log entries for this transaction queue ID, and the others. I'm guessing you'll see that the following restrictions are likely involved. These entries are _not errors_ but are informational only. These disconnections all occur during the helo phase, which is likely due to the client hanging up after a Postfix rejection based on a helo restriction. reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, check_helo_access regexp:/etc/postfix/helo-blacklist/smtp_helo_blacklist, Also, I recommend moving reject_unauth_destination to just below permit_sasl_authenticated. Having it after your whitelist checks, as you currently do, could potentially make your host an open relay under some circumstances. -- Stan
