I guess you are right. It looks like a second didn't go by, before the message got on a queue. Is that right? I had previously understood that in delays=a/b/c/d c is time elapsed from hand off from client to queue.
Oct 29 16:56:39 pmx1 postfix/smtpd[7978]: EF7454059D: client=unknown[192.168.0.209], sasl_method=PLAIN, sasl_username=user1 Oct 29 16:56:39 pmx1 postfix/cleanup[8023]: EF7454059D: message-id=<527020c8.3090...@mydomain.com> Oct 29 16:56:39 pmx1 postfix/cleanup[8023]: EF7454059D: info: header Subject: test from unknown[192.168.0.209]; from=<us...@mydomain.com> to=<u...@gmail.com> proto=ESMTP helo=<[127.0.0.1]> Oct 29 16:56:39 pmx1 postfix/qmgr[2892]: EF7454059D: from=<us...@mydomain.com>, size=582, nrcpt=1 (queue active) Oct 29 16:57:10 pmx1 postfix/smtp[8024]: EF7454059D: to=<u...@gmail.com>, relay=gmail-smtp-in.l.google.com[173.194.68.26]:25, delay=31, delays=0.02/0/30/0.55, dsn=2.0.0, status=sent (250 2.0.0 OK 1383080173 nl1si12576362qeb.75 - gsmtp) Oct 29 16:57:10 pmx1 postfix/qmgr[2892]: EF7454059D: removed On Tue, Oct 29, 2013 at 5:13 PM, li...@rhsoft.net <li...@rhsoft.net> wrote: > > Am 29.10.2013 22:08, schrieb Roman Gelfand: >> Sorry about that one. In fact, the other address was unreachable >> than. Please, keep in mind, it is the hand off from thunderbird to >> postfix I am interested in. >> >> Here is a good example. >> >> Oct 29 16:57:10 pmx1 postfix/smtp[8024]: EF7454059D: >> to=<u...@gmail.com>, >> relay=gmail-smtp-in.l.google.com[173.194.68.26]:25, delay=31, >> delays=0.02/0/30/0.55, dsn=2.0.0, status=sent (250 2.0.0 OK 1383080173 >> nl1si12576362qeb.75 - gsmtp) > > a good example for what? > status=sent -> what is your problem? > > "cat maillog | grep EF7454059D" to filter anything related to this message > from the logfilesand the "delay=31" is most likely because the message > was queued on your server for whatever load-reason or because temporary > not reachable destination (network, name-resolution, one of them at googles > side) > >> On Tue, Oct 29, 2013 at 5:02 PM, li...@rhsoft.net <li...@rhsoft.net> wrote: >>> >>> >>> Am 29.10.2013 21:55, schrieb li...@rhsoft.net: >>>> Am 29.10.2013 21:46, schrieb Roman Gelfand: >>>>> How did you decide this is a network issue? >>>> >>>> Connection timed out? >>> >>> [harry@srv-rhsoft:~]$ telnet 96.57.168.248 25 >>> Trying 96.57.168.248... >>> telnet: connect to address 96.57.168.248: Connection timed out >>> >>> and BTW: >>> >>> mail.domain.com[96.57.168.248]:25: Connection timed out >>> >>> if you think you need to anonymize informations do *not* >>> use random domains: http://tools.ietf.org/html/rfc2606#section-3 >>> and if you need help generally avoid to do so without >>> very good reasons >>> >>> [harry@srv-rhsoft:~]$ host mail.domain.com >>> mail.domain.com has address 72.5.54.21 >>> >>>>> How would you go about determining which router which switch? >>>> >>>> it's hard to explain how to debug network issues >>>> >>>>> On Tue, Oct 29, 2013 at 4:33 PM, li...@rhsoft.net <li...@rhsoft.net> >>>>> wrote: >>>>>> >>>>>> >>>>>> Am 29.10.2013 21:25, schrieb Roman Gelfand: >>>>>>> The client is thunderbird. Correct me if I am wrong, it appears it 40 >>>>>>> seconds for the client to hand over the email to the server? If so, >>>>>>> where should I troubleshoot? are there maintenance >>>>>>> tasks/configuration changes to improve this situation. >>>>>>> >>>>>>> BTW... from the inception there was no or negligible delay. Several >>>>>>> months later, I am seeing this on regular basis even hourly volume is >>>>>>> not large. >>>>>>> >>>>>>> Oct 29 16:06:10 pmx1 postfix/smtp[7414]: 200AC43831: >>>>>>> to=<u...@domain.com>, relay=none, delay=40, delays=0.01/0/40/0, >>>>>>> dsn=4.4.1, status=deferred (connect to >>>>>>> mail.domain.com[96.57.168.248]:25: Connection timed out) >>>>>> >>>>>> this is clearly a *network* problem on the server *or* the client >>>>>> *or* somewhere between (routers, switches....)
