Hi it seems to be a layer 3 issue, according to the description I will check 
any firewall or router at the perimeters end.

Have you checked that? Have you tried tcpdump to check if those packets are 
leaving the box?

Thats just a thought, I hope it helps.

Regards.


Saludos 

Ing. Alfonso Alejandro Reyes Jimenez 
Coordinador de Seguridad - SASI 
E-mail: aare...@scitum.com.mx 
Telefono: 91507489 
Movil: (044) 55 85 81 04 62
 

De: Gonzo Fernandez [mailto:go...@usaepay.com] 
Enviado: Monday, January 30, 2012 06:46 PM
Para: postfix users <postfix-users@postfix.org> 
Asunto: Re: Mail stuck (Connection Timed-Out) 
 

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?

[root@mx-server ~]# cat /var/log/maillog | grep B0847E8491

Jan 30 08:44:38 mx-server postfix/cleanup[24478]: B0847E8491: 
message-id=<20120130164438.B0847E8491@mxser...@example.com>
Jan 30 08:44:38 mx-server postfix/qmgr[16186]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 08:44:38 mx-server postfix/bounce[24473]: 2604BE84D6: sender 
non-delivery notification: B0847E8491
Jan 30 08:45:01 mx-server postfix/smtp[24278]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=23, delays=0.03/0/23/0, dsn=4.4.1, 
status=deferred (connect to example.com[1.2.3.4]: Connection timed out)
Jan 30 09:08:09 mx-server postfix/qmgr[16186]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 09:08:32 mx-server postfix/smtp[24522]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=1434, delays=1411/0/23/0, dsn=4.4.1, 
status=deferred (connect to example.com[1.2.3.4]: Connection timed out)
Jan 30 09:41:31 mx-server postfix/qmgr[16186]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 09:41:52 mx-server postfix/smtp[24793]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=3434, delays=3412/0.1/21/0, dsn=4.4.1, 
status=deferred (connect to example.com[1.2.3.4]: Connection timed out)
Jan 30 10:48:09 mx-server postfix/qmgr[16186]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 10:48:15 mx-server postfix/smtp[25097]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=7417, delays=7411/0.06/5.9/0, 
dsn=4.4.3, status=deferred (Host or domain name not found. Name service error 
for name=example.com type=A: Host not found, try again)
Jan 30 12:11:30 mx-server postfix/qmgr[16186]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 12:11:53 mx-server postfix/smtp[25539]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=12435, delays=12411/0.05/23/0, 
dsn=4.4.1, status=deferred (connect to example.com[1.2.3.4]: Connection timed 
out)
Jan 30 13:22:45 mx-server postfix/qmgr[26236]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 13:23:12 mx-server postfix/smtp[26261]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=16713, delays=16687/0.56/26/0, 
dsn=4.4.1, status=deferred (connect to example.com[1.2.3.4]: Connection timed 
out)
Jan 30 13:53:27 mx-server postfix/qmgr[26443]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 13:53:55 mx-server postfix/smtp[26593]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=18556, delays=18529/6.5/21/0, 
dsn=4.4.1, status=deferred (connect to example.com[1.2.3.4]: Connection timed 
out)
Jan 30 15:14:54 mx-server postfix/qmgr[27600]: B0847E8491: from=<>, size=3456, 
nrcpt=1 (queue active)
Jan 30 15:15:21 mx-server postfix/smtp[27790]: B0847E8491: 
to=<m...@example.com>, relay=none, delay=23443, delays=23416/5.9/21/0, 
dsn=4.4.1, status=deferred (connect to example.com[1.2.3.4]: Connection timed 
out)
[root@mx-server ~]# telnet 1.2.3.4 25
Trying 1.2.3.4...
telnet: connect to address 1.2.3.4: Connection timed out
telnet: Unable to connect to remote host: Connection timed out

Gonzo Fernandez

On Jan 30, 2012, at 3:36 PM, Noel Jones wrote:


        On 1/30/2012 5:07 PM, Gonzo Fernandez wrote:
        

                Hi All,
                


                My relay servers have mail being received but unable to send. 
When I
                

                type "mailq" I see: Delivery temporarily suspended….Connection 
timed
                

                out. I also noticed this line:
                


                Tarpitting active for [1.2.3.4)
                


                I restarted postfix, flushed mailq and still everything is 
stuck.
                

                Now the mail is building up and I don't know what else to do. 
I'm
                

                still continuing to work on it but I figure I might as well ask 
the
                

                postfix team members. Can anyone help me figure this thing out 
please? 
                


                mailq:
                


                Jan 30 13:53:27 mx-server postfix/qmgr[26443]: BC535E8264:
                

                from=<m...@example.com <mailto:m...@example.com>>, size=805, 
nrcpt=1
                

                (queue active)
                

                Jan 30 13:53:55 mx-server postfix/qmgr[26443]: BC535E8264:
                

                to=<m...@example.com <mailto:m...@example.com>>, relay=none, 
delay=357647,
                

                delays=357619/28/0/0, dsn=4.4.1, status=deferred (delivery
                

                temporarily suspended: connect to example.com
                

                <http://example.com>[1.2.3.4]: Connection timed out)
                



        (please post in plain-text only)
        (please use example.com rather than real domain names.  thanks)
        
        
        Looks as if the destination 1.2.3.4 doesn't like your server.
        You'll need to check with them about why.
        
        One possibility is that you've been flooding them with backscatter
        and they've blacklisted you for that.  If that's the problem, the
        solution is to not accept mail you can't deliver.
        
        Or maybe you've got a spam-bot on your network that's spewing stuff
        they don't like.
        
        But that's just speculation... Only they know the reason.
        
        
        
         -- Noel Jones
        


Reply via email to