Question about Tracking Center status

Feb 27, 2019
2
0
1
29
Hi everyone :)


For my first question here, I'll ask something "simple" (I hope :D )

This question is only for inbound messages (outbound isn't setup yet).

In the Tracking Center, some messages are defered due to my end server blocking the request... whish I should have fixed by now.

Well, prior that, I saw something that's odd for me, the status.

Status display the first "end" message. Let me explain further:
If the message is accepted, but the relay isn't accessible, we get the status : "accepted/deferred"
When the relay is back online, the message is sent but the status... well, didn't change :/

I also get another situation where status is set to "queued/deferred" or also "queued/delivered" but then it is fully delivered and accepted to the end server.


My question ? is this a bug that the status didn't update after the first failed delivery attempt ?


As a solution, I could flush the log and "voilà", but, maybe there is a more elegant way to do that :D

Thanks


An example:

Status is "accepted/deferred" there:
Feb 27 23:05:10 ///// postfix/lmtp[26185]: 594D7410A0: to=</////>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.2, delays=0.06/0/0.04/1.1, dsn=2.5.0, status=sent (250 2.5.0 OK (410A45C7709956622B))
Feb 27 23:05:10 ///// postfix/qmgr[24401]: 594D7410A0: removed
Feb 27 23:05:40 ///// postfix/smtp[26190]: 6F07A410CB: to=</////>, relay=none, delay=30, delays=0.04/0.01/30/0, dsn=4.4.1, status=deferred (connect to /////[/////]:25: Connection timed out)
Feb 27 23:05:40 ///// postfix/qmgr[24401]: 6F07A410CB: from=<sd-pro-return-15106-/////@ml.ovh.net>, size=4774, nrcpt=1 (queue active)
Feb 27 23:05:50 ///// postfix/smtp[26190]: 6F07A410CB: to=</////>, relay=none, delay=40, delays=30/0/10/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=///// type=MX: Host not found, try again)
Feb 27 23:11:34 ///// postfix/qmgr[26408]: 6F07A410CB: from=<sd-pro-return-15106-/////@ml.ovh.net>, size=4774, nrcpt=1 (queue active)
Feb 27 23:11:35 ///// postfix/smtp[26410]: 6F07A410CB: to=</////>, relay=/////[/////]:25, delay=385, delays=384/0.02/0.48/0.57, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 2918F126043)
Feb 27 23:11:35 ///// postfix/qmgr[26408]: 6F07A410CB: removed
 

dietmar

Proxmox Staff Member
Staff member
Apr 28, 2005
16,600
339
103
Austria
www.proxmox.com
Maybe you useed a search filter? Or just restricted the search time to much, so that it does not include the time when the message gets delivered?
 
Feb 27, 2019
2
0
1
29
Nope, the time filter is set 2 or 3hrs prior the actual time until next day midnight. Those are default value, and for those example, the timeframe is in, widely :D
 

EUSAN

New Member
Jul 18, 2019
7
0
1
28
Hello

Jul 18 10:54:41 pmg postfix/smtpd[13512]: connect from localhost.localdomain[127.0.0.1]
Jul 18 10:54:41 pmg postfix/smtpd[13512]: 3E962301033: client=localhost.localdomain[127.0.0.1], orig_client=maill.heves.gob.pe[192.168.32.200]
Jul 18 10:54:41 pmg postfix/cleanup[13525]: 3E962301033: message-id=<646111607.230983.1563465264084.JavaMail.zimbra@heves.gob.pe>
Jul 18 10:54:41 pmg postfix/qmgr[25032]: 3E962301033: from=<gino.soto@heves.gob.pe>, size=10225539, nrcpt=2 (queue active)
Jul 18 10:54:41 pmg postfix/smtpd[13512]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 xforward=1 mail=1 rcpt=2 data=1 commands=6
Jul 18 10:55:11 pmg postfix/smtp[13516]: 3E962301033: to=<megas@minsa.gob.pe>, relay=none, delay=31, delays=0.5/0/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 10:55:11 pmg postfix/smtp[13516]: 3E962301033: to=<oga99@minsa.gob.pe>, relay=none, delay=31, delays=0.5/0/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:01:34 pmg postfix/qmgr[25032]: 3E962301033: from=<gino.soto@heves.gob.pe>, size=10225539, nrcpt=2 (queue active)
Jul 18 11:02:05 pmg postfix/smtp[13587]: 3E962301033: to=<megas@minsa.gob.pe>, relay=none, delay=444, delays=414/0/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:02:05 pmg postfix/smtp[13587]: 3E962301033: to=<oga99@minsa.gob.pe>, relay=none, delay=444, delays=414/0/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:11:34 pmg postfix/qmgr[25032]: 3E962301033: from=<gino.soto@heves.gob.pe>, size=10225539, nrcpt=2 (queue active)
Jul 18 11:12:04 pmg postfix/smtp[13711]: 3E962301033: to=<megas@minsa.gob.pe>, relay=none, delay=1043, delays=1013/0.02/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:12:04 pmg postfix/smtp[13711]: 3E962301033: to=<oga99@minsa.gob.pe>, relay=none, delay=1043, delays=1013/0.02/30/0, dsn=4.4.1, status=deferred (connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:16:04 pmg postfix/qmgr[25032]: 3E962301033: from=<gino.soto@heves.gob.pe>, size=10225539, nrcpt=2 (queue active)
Jul 18 11:16:29 pmg postfix/error[13806]: 3E962301033: to=<megas@minsa.gob.pe>, relay=none, delay=1309, delays=1283/25/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)
Jul 18 11:16:29 pmg postfix/error[13806]: 3E962301033: to=<oga99@minsa.gob.pe>, relay=none, delay=1309, delays=1283/25/0/0.01, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to minsamail.minsa.gob.pe[181.177.250.15]:25: Connection timed out)



I have this error with some domains. please with support
 

tom

Proxmox Staff Member
Staff member
Aug 29, 2006
14,057
493
103
I have this error with some domains. please with support
the connection timed out, the host [181.177.250.15]:25 does not answer.

I just tried to connect from here, no answer on port 25.

Code:
telnet minsamail.minsa.gob.pe 25
Trying 181.177.250.15...
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!