I was reading about "Defferred queue full of dictionary attack bounces" which I
think might be an issue here.
So i performed a qshape analysis and I got this:
command: qshape deferred | head
T 5 10 20 40 80 160 320 640 1280 1280+
TOTAL 583 0 0 0 0 0 1 8 47 25 502
adbaa.org 214 0 0 0 0 0 0 0 0 0 214
onramp.bz 191 0 0 0 0 0 1 6 26 10 148
unitedimagingpartners.com 62 0 0 0 0 0 0 0 7 5 50
mmvacations.com 26 0 0 0 0 0 0 0 1 0 25
fishwindowcleaning.com 12 0 0 0 0 0 0 0 3 1 8
warrensouth.com 5 0 0 0 0 0 0 0 1 0 4
ecodiscoverypark.com 5 0 0 0 0 0 0 1 0 0 4
pfg.com 4 0 0 0 0 0 0 0 1 2 1
Luckily the active and and incoming queues aren't showing any signs of
backscatter. I'm going to be checking firewall tomorrow to see if there's an
issue there. Thanks for your help.
Gonzo Fernandez
On Jan 30, 2012, at 9:09 PM, Noel Jones wrote:
> On 1/30/2012 10:30 PM, Noel Jones wrote:
>> On 1/30/2012 6:46 PM, Gonzo Fernandez wrote:
>>> Thank you Noel. Our server sends out copies of email confirmations
>>> to our clients and if the client decides to make a large order they
>>> end up pushing our volume up and we end up getting blocked by their
>>> mail server. I seem to be getting connection timed out on a lot of
>>> the hosts. I even try to telnet to ip and port 25 but it keeps
>>> timing out. I used "grep" to search in /var/log/maillog and I got
>>> this. Any ideas?
>>
>>
>> This isn't a postfix problem. If you can't telnet to any client
>> port 25, then you have a connectivity problem; maybe your ISP is
>> blocking that port, or some firewall has been misconfigured.
>> Contact your networking team or your ISP.
>>
>> If you can't telnet to this one destination port 25, they're
>> blocking you. You'll need to contact them to get this resolved.
>>
>>
>> Good luck.
>>
>>
>>
>> -- Noel Jones
>
>
> If the destination can't handle the load you're sending it, you can
> slow postfix down. Details here:
> http://www.postfix.org/QSHAPE_README.html#active_congestion
>
> Of course, this won't help until they stop blocking you.
>
> -- Noel Jones
