| Author |
|
soccer2d
Newbie
Joined: 02 May 2007
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: 05 August 2009 at 5:44am | IP Logged
|
|
|
I am having a problem with the message queue I am receiving the following message in the log
08:39:59 of thread #3328. Connecting to server...
08:39:59 of thread #3328. Connected to server
08:39:59 of thread #3328. Sending message from file 5930.eml
08:39:59 of thread #3328. Reading message file
08:39:59 of thread #3328. Sending MAIL FROM command
08:39:59 of thread #3328. Sending RCPT TO command
08:39:59 of thread #3328. No dot at line start found, skipping parsing
08:39:59 of thread #3328. Dotting the message end
08:39:59 of thread #3328. Sending DATA command
08:40:01 of thread #3328. ERROR - No response: connection is lost
08:40:01 of thread #3328. ERROR - The message has not been sent due to connection failure
I purposely made this email to not have a TO address so it would fail. The problem is it stays in the queue and doesn't rename it, so every email after it won't send until it does. What can I do to fix this, I even tried having mailbee delete emails that have failed and that didn't work.
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6038
|
| Posted: 05 August 2009 at 6:11am | IP Logged
|
|
|
According to the log file, SMTP server terminates connection unexpectedly. If it returned an error, MMQ would be able to process it and mark the message as undeliverable. But since the connection is terminated, MMQ attempts to resend this message once again. Thus, the issue is caused by incorrect SMTP server behavior which cannot be worked around by MMQ.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
soccer2d
Newbie
Joined: 02 May 2007
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: 05 August 2009 at 9:45am | IP Logged
|
|
|
So in this case the email address recepient was invalid thats why it was terminated unexpectedly. But regardless no matter how or why the email didn't get sent it should mark the email as bad, or at least put it in the bottom of the queue and not stack up all the other messages. MMQ knows that it was disconnected from the SMTP server, or else it wouldn't be in the log, so how can MMQ not work around this?
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6038
|
| Posted: 06 August 2009 at 5:07am | IP Logged
|
|
|
How do you suggest MMQ to process an error if there were NO error? Server just died unexpectedly during sending message, and from MMQ point of view, such situation requires another attempt of sending the message.
It's SMTP server responsibility area to check message structure validity, which was not performed in such case. If it's not possible to reconfigure SMTP server you're using, we suggest to check message structure from within the application which submits the message to MMQ pickup folder, before the submission.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: Emails getting stuck in queue
Privacy policy |
Refund policy