From: | Tommy |
---|---|
Date: | 1/12/23 4:56 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
As far as i know,the smtp queue flusing is every minites,sometimes it is dead lock never works,check SmtpQueue.log it never any new log,after server restart,it works again. Any fast method to force the smtp queue flusing? |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 1/12/23 9:22 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
What value are you using for Retry Interval under Server Configuration/Advanced tab? Even though the queue is flushed every minute, emails are not sent again until the Retry Interval occurs.
|
|
Top |
From: | Tommy |
---|---|
Date: | 1/12/23 7:45 PM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
When you search Flusing SMTP queue at SmtpQueue.log,you can see it run task every minutes.When it is dead,you can not see any more Flusing SMTP queue at the log,and many emails stay at outbound queue. |
|
Top |
From: | Tommy |
---|---|
Date: | 1/13/23 6:26 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
I found some unusual at queue iteration.
2023-01-13 15:18:22,137 - Outbound queue iteration completed in 5301 ms. |
|
Top |
From: | Tommy |
---|---|
Date: | 4/17/23 1:31 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
I found the issue,for the retry queue,the email is sent one by one,if the one is still sending,it will not open another thread and send other one. This will be problem if one of big email sending to downstream server,and many small emails keep stay in the queue. Best suggestion: For the retry queue,if one of the email is not sent finished within 1 minutes,open another new thread to deliver other emails,this can avoid email queue issue. |
|
Top |
From: | Tommy |
---|---|
Date: | 4/24/23 9:35 PM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Any solutions for that? |
|
Top |
From: | Synametrics Support |
---|---|
Date: | 4/26/23 9:07 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Your assessment is correct: once emails go into the queue, a single thread processes all of them. Changing this logic is not trivial. I have submitted a request to our to-do list and our dev team will evaluate and assign a priority to the task. Note that most emails will never go into the queue if they are delivered on the first attempt. |
|
Top |
From: | Tommy |
---|---|
Date: | 4/26/23 10:30 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Xeams can run for muti-domains,if one of the email has issue,it will have many others waiting behind it. I think 3 threads for queue is best choice. |
|
Top |
From: | Tommy |
---|---|
Date: | 4/26/23 7:52 PM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
For example,xeams is running as front,if the downstream server has some problems for a long time,there are hundreds of emails stay at the retry queue,once the downstream server back online,if send one by one,it is too slow and takes too long time. Best suggestion: There is changeable options at the control pannel,by default,the retry thread is set to 1 or 2,for urgent case,administrator can change to be 5-10 and restart xeams to make it works. |
|
Top |
From: | Tommy |
---|---|
Date: | 5/13/23 2:24 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Any update on this function? |
|
Top |
From: | Tommy |
---|---|
Date: | 5/13/23 2:25 AM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Any update on this function? |
|
Top |
From: | Tommy |
---|---|
Date: | 5/30/23 11:01 PM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
For example,the xeams is running at the could server,backend service offline due to outage for several hours or a day. In that case,there maybe too many emails stay at the queue,after the backend server back online,if send one by one,it is really too slow and takes too long time. If backend server is exchange,it is easily to have below issue: 451 4.7.0 Temporary server error. Please try again later. PRX4 If you do not check the log,maybe not know the exchange issue,as telnet exchange 25 port is normal status.This case also cause too many queue. So extend the retry queue threads is urgently needed function. |
|
Top |
From: | Synametrics Suppport |
---|---|
Date: | 5/31/23 3:14 PM |
Topic: | SMTP queue dead lock |
Type: | General Discussions |
Post a follow up |
Tommy, We already have this feature in our to-do list. However, it is a major change and therefore, will take some time.
|
|
Top |