> > 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 (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). > > 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
