Question about Tracking Center status

Discussion in 'Mail Gateway: Installation and configuration' started by Athar42, Feb 28, 2019.

  1. Athar42

    Athar42 New Member
    Proxmox Subscriber

    Joined:
    Feb 27, 2019
    Messages:
    2
    Likes Received:
    0
    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:
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,484
    Likes Received:
    314
    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?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Athar42

    Athar42 New Member
    Proxmox Subscriber

    Joined:
    Feb 27, 2019
    Messages:
    2
    Likes Received:
    0
    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
     
  4. EUSAN

    EUSAN New Member

    Joined:
    Jul 18, 2019
    Messages:
    7
    Likes Received:
    0
    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
     
  5. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,635
    Likes Received:
    419
    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...
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice