Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 6058 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

incoming email stuck in queue

StefanoColombo

we're having an issue with email protection ( MTA ) .

starting from yesterday we had hundreds incoming email stuck in queue .

At the beginning we found the issue was related to the internal server that were low on disk space and didn't accept connection , so we solved that issue and all the queued email were forwarded during the night

 

Today we're having the same issue , however the internal server are fine so the issue seems more to be related to the firewall .

How can I check the reason causing the queue increase ?

thanks



This thread was automatically locked due to age.
Parents
  • 0 in reply to LuCar Toni

    I had a look at the smtp_main.log but could not find yet a reason for queue not being emptied apart from this

    error=unable to get local issuer certificate cert=/CN=....

    But the certificate mentioned is the selfsigned exchange certificate which did not change

     

  • 0 in reply to StefanoColombo

    You should see some REF_ID beside the Email.

    Perform a "Grep" on the logs.

    grep REF_ID smtp_main.log | less 

  • 0 in reply to LuCar Toni

    here is one

    21320 locking /sdisk/spool/output//db/retry.lockfile
    21320 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    21320 Considering: name.surname@domain.it
    21320 unique = name.surname@domain.it
    21320 name.surname@domain.it: queued for routing
    21320 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    21320 routing name.surname@domain.it
    21320 --------> router_for_notifications router <--------
    21320 local_part=name.surname domain=domain.it
    21320 checking "condition" "${if and{{bool_lax{1}}{bool_lax{${if eq{$acl_c1}{1}{1}{0}}}}}}"...
    21320 router_for_notifications router skipped: condition failure
    21320 --------> static_route_hostlist_for_email router <--------
    21320 local_part=name.surname domain=domain.it
    21320 checking "condition" "${if match_address{$local_part@$domain}{+hostlist_route_emails}{1}{0}}"...
    21320 calling static_route_hostlist_for_email router
    21320 static_route_hostlist_for_email router called for name.surname@domain.it
    21320   domain = domain.it
    21320 static_route_hostlist_for_email router declined for name.surname@domain.it
    21320 --------> static_route_hostlist router <--------
    21320 local_part=name.surname domain=domain.it
    21320 checking domains
    21320 calling static_route_hostlist router
    21320 static_route_hostlist router called for name.surname@domain.it
    21320   domain = domain.it
    21320 original list of hosts = "<;10.0.20.120;10.0.20.121;" options =
    21320 expanded list of hosts = "<;10.0.20.120;10.0.20.121;" options =
    21320 set transport static_smtp
    21320 finding IP address for 10.0.20.120
    21320 calling host_find_byname
    21320 finding IP address for 10.0.20.121
    21320 calling host_find_byname
    21320 queued for static_smtp transport: local_part = name.surname
    21320 domain = domain.it
    21320   errors_to=NULL
    21320   domain_data=NULL localpart_data=NULL
    21320 routed by static_route_hostlist router
    21320   envelope to: name.surname@domain.it
    21320   transport: static_smtp
    21320   host 10.0.20.120 [10.0.20.120]
    21320   host 10.0.20.121 [10.0.20.121]
    21320 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    21320 After routing:
    21320   Local deliveries:
    21320   Remote deliveries:
    21320     name.surname@domain.it
    21320   Failed addresses:
    21320   Deferred addresses:
    21320 LOG: MAIN
    21320   => name.surname@domain.it F=<lsconf@sender.it> P=<lsconf@sender.it> R=static_route_hostlist T=static_smtp S=214826 H=10.0.20.120 [10.0.20.120]:25 I=[10.0.20.251]:33032 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no DN="/CN=TRE-EXCH01" C="250 2.6.0 <100014240.271258.1560836001010@mail1.sender.it> [InternalId=21607980466250, Hostname=TRE-EXCH02.TRERE.IT] 216177 bytes in 0.134, 1575.191 KB/sec Queued mail for delivery" QT=10s DT=0.152s
    2019-06-18 07:33:34.767 [21320] 1CT05Q-Ddc3tK-wR => name.surname@domain.it F=<lsconf@sender.it> P=<lsconf@sender.it> R=static_route_hostlist T=static_smtp S=214826 H=10.0.20.120 [10.0.20.120]:25 I=[10.0.20.251]:33032 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no DN="/CN=TRE-EXCH01" C="250 2.6.0 <100014240.271258.1560836001010@mail1.sender.it> [InternalId=21607980466250, Hostname=TRE-EXCH02.TRERE.IT] 216177 bytes in 0.134, 1575.191 KB/sec Queued mail for delivery" QT=10s DT=0.152s
    21320 LOG: MAIN
    21320   Completed QT=10s
    2019-06-18 07:33:34.769 [21320] 1CT05Q-Ddc3tK-wR Completed QT=10s
    21320 locking /sdisk/spool/output//db/retry.lockfile

  • 0 in reply to StefanoColombo

    Looks like, this email got delivered? 

    21320   => name.surname@domain.it F=<lsconf@sender.it> P=<lsconf@sender.it> R=static_route_hostlist T=static_smtp S=214826 H=10.0.20.120 [10.0.20.120]:25 I=[10.0.20.251]:33032 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no DN="/CN=TRE-EXCH01" C="250 2.6.0 <100014240.271258.1560836001010@mail1.sender.it> [InternalId=21607980466250, Hostname=TRE-EXCH02.TRERE.IT] 216177 bytes in 0.134, 1575.191 KB/sec Queued mail for delivery" QT=10s DT=0.152s
    2019-06-18 07:33:34.767 [21320] 1CT05Q-Ddc3tK-wR => name.surname@domain.it F=<lsconf@sender.it> P=<lsconf@sender.it> R=static_route_hostlist T=static_smtp S=214826 H=10.0.20.120 [10.0.20.120]:25 I=[10.0.20.251]:33032 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no DN="/CN=TRE-EXCH01" C="250 2.6.0 <100014240.271258.1560836001010@mail1.sender.it> [InternalId=21607980466250, Hostname=TRE-EXCH02.TRERE.IT] 216177 bytes in 0.134, 1575.191 KB/sec Queued mail for delivery" QT=10s DT=0.152s

     

    250 https://www.greenend.org.uk/rjk/tech/smtpreplies.html 

  • 0 in reply to LuCar Toni

    Actually the emails were not delivered and stuck in the queue.

    We opened a ticket and with the support we deleted some references on the DB for emails that seemed to block all the others , restarted the smtpd .

    Then all the emails in queue were successfully delivered , however after a while others started to queue again so we switched to the other XG node of the HA and this had no issue .

    We will investigate with the support the first node

     

    thanks for the help

Reply
  • 0 in reply to LuCar Toni

    Actually the emails were not delivered and stuck in the queue.

    We opened a ticket and with the support we deleted some references on the DB for emails that seemed to block all the others , restarted the smtpd .

    Then all the emails in queue were successfully delivered , however after a while others started to queue again so we switched to the other XG node of the HA and this had no issue .

    We will investigate with the support the first node

     

    thanks for the help

Children
No Data