On 5/1/2010 12:58 PM, Gary Smith wrote:
Lately I have found that my outgoing queues are getting a little clogged for
yahoo and sbcglobal.net. This usually coincides with a bulk set of news
letters sent out from a couples clients. Typically we are seeing that they
dump about 2000msg/per batch, with no more than one batch per week (usually on
Friday nights). The problem is they do it in one fatal swoop. When this
happens, we seem to get rate limited from yahoo/sbcglobal for a few hours,
which directly affects our other users.
Some time ago I put a rate limiter in place for AOL/yahoo/sbcglobal/gmail so we
wouldn't be bombarding but I don't think that it's being honored, probably
because I missed something. When I do a postconf I don't see my rate limiter,
which is in main.cf, listed there. I'm not sure if that's by design or part of
a misconfiguration on my part. Mail goes out from different sets of servers,
with the same public IP, so rate limiting will only affect the bulk mail queue.
"custom" parameter names don't display in postconf output by
design.
Is there something obvious that I missed?
master.cf:
ratelimit unix - - n - 3 smtp
rate_limit_transport:
aol.com ratelimit:
yahoo.com ratelimit:
sbcglobal.net ratelimit:
gmail.com ratelimit:
main.cf:
ratelimit_destination_concurrency_failed_cohort_limit = 100
ratelimit_destination_concurrency_limit = 10
This looks reasonable to me; no more than 3 connections should
be made at a time to any combination of those destinations.
Why don't you think it's working?
Hint: it's helpful to add a custom log name to a master.cf
transport entry to make sure it's being used.
-o syslog_name=postfix-ratelimit
http://www.postfix.org/postconf.5.html#syslog_name
postconf -n:
[not examined]
-- Noel Jones
