On 5/1/2010 1:31 PM, Gary Smith wrote:
rate_limit_transport:
aol.com ratelimit:
yahoo.com ratelimit:
sbcglobal.net ratelimit:
gmail.com ratelimit:
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?
I'm not sure why I think it's not working. Skimming the log file, shortly
after the back was launched, we saw several of these messages:
connect to sbcgloabal.net[208.73.210.27]:25: Connection refused
connect to comcst.net[216.240.187.144]:25: Connection refused
connect to eathlink.net[216.65.41.185]:25: Connection refused
These are dead domains, either owned by squatters or web
redirectors owned by the "real" domain. The domains exist but
will never accept mail, so postfix will retry until the mail
expires. You can instruct postfix to reject common
misspellings like this by adding transport map entries such as:
# transport
eathlink.net error:5.1.2 no such domain
sbcgloabal.net error:5.1.2 no such domain
comcst.net error:5.1.2 no such domain
(obviously the last two aren't on the list, but will be added). Anyway, I will
start logging see if it's working. I also just noticed that the rate limiting
file was touched this week, so I need to find out what was touched (which it
hasn't been touched in a year since we set it up).
For misspelled domains, either ignore them or add a transport
entry to reject them right away. Obviously you can't add
every possible bad domain, but it's helpful to add the top 10
or so for your users.
-- Noel Jones
