Christian Purnomo put forth on 6/24/2010 11:33 PM: > /etc/postfix/transport: > server2.com: relay:[10.0.2.73] > > /etc/postfix/master.cf: > relay unix - - n - 200 smtp > -o smtp_helo_timeout=3s > -o smtp_connect_timeout=3s > -o disable_dns_lookups=yes > -o fallback_relay=
This was answered by Wietse 4 years ago on this list. Took me ten seconds to find it via Google. Read the entire thread on Neohapsis carefully and you'll find your answer, which is to remove all this custom stuff and go back to the defaults. The first 2 of 4 above are the cause of your immediate problem, as they are waaaay too low. The other two are just unnecessary. And change max_proc back to 100. You're probably not getting close to 100 processes running anyway. http://archives.neohapsis.com/archives/postfix/2006-01/thread.html#1866 > Server 2 has the following configurations: > > /etc/postfix/master.cf: > smtp inet n - - - 200 smtpd Change the max process limit back to 100. If everything else is configured correctly, you can drain an unbelievable amount of mail with less than 100 smtp/smtpd processes. > Could you please tell me what I'm missing here? I would like to improve > the rate that Server1 can relay messages to Server2. If I may be frank, you missed the fact that you shouldn't mess with the default settings unless you really know what you're doing. Custom settings here would require an extreme scenario. I don't believe your scenario is extreme, but rather common. I'm not pretending to be an expert on this, or to create the image that _I_ know how/when to customize these settings. I simply know when _not_ to. -- Stan
