Hi, >> Yes, understood. There are two MXs for the domain that has the bulk >> mailing overload problem and the one I'm adjusting the >> default_process_limit. There is one MX for the domain that has the >> always_bcc issue and the submission port auth issue. > > Let's concentrate on the connection load issue. Both servers in > question are MX servers, correct? Set > smtpd_client_connection_count_limit=1 on both. Leave > default_process_limit at the default of 100. That will fix both your > queue clogging and timeout problems.
I've set this on both the primary and secondary MX servers now. Can you explain how this parameter actually works? Currently, services such as constantcontact make many thousands of connections to the server at a time. I'm assuming each connection represents one message. By setting smtpd_client_connection_count_limit to 1, isn't it only regulating the number of messages per connection, not the actual number of connections? In the docs it says it shouldn't be used to limit legitimate traffic. Is that not the case? Maybe it's premature to mention it now, but I believe it was rob0 that had previously mentioned using the anvil_rate* and smtpd_*rate parameters. Are the others not necessary? Thanks, Alex
