sendmail rejecting messages with error connection limit rate exceeded.
I am running debian jessie with sendmail 8.14.4. I do not find where is the setting to disable the mails to be rejected for a certain host and i get periodically this message:
Code:
May 28 16:20:30 mx6 sm-mta[14808]: ruleset=check_relay, arg1=[x.x.x.x], arg2=x.x.x.x, relay=[x.x.x.x], reject=421 4.3.2 Connection rate limit exceeded Code:
define(confCONNECTION_RATE_THROTTLE',15')dnl is there a way to disable for certain domains that there is no connection limit at all? need to recompile? downgrade? I am using sendmail installed via apt-get. thank you. |
sendmail rejecting messages with error connection limit rate exceeded.
CONNECTION_RATE_THROTTLE
This sets a limit on the number of new connections per second. It helps protect you against mail-bombs and similar denial-of-service attacks. define(`confCONNECTION_RATE_THROTTLE', `100')dnl If the rate goes above the limit, new connections are rejected and the sending mailers have to retry later. |
Quote:
Code:
m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf Or you can just disable throttling for the host in question. Edit/etc/mail/access and add: Code:
ClientRate: x.x.x.x 0 Code:
makemap hash /etc/mail/access < /etc/mail/access |
Hello,
thank you for your help.. I understand that CONNECTION_RATE_THROTTLE delays the message do not reject it. i see this on the doc online i find: define(`confCONNECTION_RATE_THROTTLE', `5')dnl This defines the overall number of concurrent connection the server accepts per second, before queuing incoming connection-request regardless of the host. The connections will not be rejected but stalled until the next second. This means that for the above example that when 20 connection-requests arrive, the first five (1-5) are processed in second one, the second five (6-10) in second two, the third five (11-15) in second three, and the final five (16-20) in second four. this is not my case as my connection are simple rejected I think I may have found the issue: sendmail.mc has this two rules: dnl # Stop connections that overflow our concurrent and time connection rates FEATURE(`conncontrol', `nodelay', `terminate')dnl FEATURE(`ratecontrol', `nodelay', `terminate')dnl but how can I find the current connection rates. I will test with applying the rule ClientRate on the access DB. thank you all for your answers. Mario. |
All times are GMT -5. The time now is 10:16 AM. |