mail delivery issues since build 7153
Problem reported by Christian Schmit - August 14 at 2:16 AM
Submitted
Since build 7153 we have noticed increased delivery failures for local and remote recipients. Another factor indicating that something seems to have changed from build 7125 to build 7153 is that in the Smartermail statistics we see a huge increase in "SMTP Terminated connections" under "SMTP Out Sessions". We reverted back to build 7125 which solves the delivery issue for us.

Is anyone else running build 7153 seeing an increase in "SMTP Terminated connections" under "SMTP Out Sessions" in the Smartermail statistics?

We also saw much more "mailbox is locked" entries in delivery.log with build 7153. Maybe both issues are related. We have tickets are open with support for this.

Christian

14 Replies

Reply to Thread
0
David Jamell Replied
0
Thomas Lange Replied
Looks like are we have similar issues with our SmarterMail system:
We are receiving the System-Messages with Delivery-Notification for all outgoing emails, but only for the automatically by our SmarterMail/Events automatically added "journal@"-recipient/account used for our message-archiving software.

Our Events "Journal Incoming" and "Journal Outgoing" - both just do "Add recipient" journal@ourdomain.de
and under "Spool" and "Waiting for Delivery" are many, many hundreds/thousounds of emails.... most of them dealing with delivering to our local journal-useraccount (looks like only this "last/added recipient" ist failing, originally recipients are already ok/success!
Could even be that some kind of messages having "looping issues" because often many, many, many textlines with "Failed" :-(

I can even see "mailbox is locked" messages in the delivery log for the journal-account, re-indexing was no solution, still seeing this issues/SystemMessages with delivery failure
[2019.08.14] 17:20:46.631 [40279] Add message to mailbox call failed.  Reason: Access to the grp file is locked, monitor enter failed.
[2019.08.14] 17:20:46.631 [40279] Delivery attempt to journal@xxxxxxxxxx.de to folder 'Inbox' failed.  Mailbox is locked.

I tried with SystemMessages and "empty from address", and even with entering "postmaster as the from-address", this did not make any difference concerning the messages/failure-emails.

And our users do think, that there original/destination was not working, they do not notice that in our case it is just our "journal"-recipient failing!

tested with v17 / build 7153 and even with the MAPI-beta 7159
looks like the bug/issue is not solved/fixed yet.
2
Kyle Kerst Replied
Employee Post
Thomas, if you're still having looping issues please deploy the custom build below which includes fixes for this as well as some automated forwarding delay problems: 

Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Bruce Replied
I am getting 1,000 of emails looping on multiple SmarterMail servers with the subject line;

 Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed:Failed: Failed: Failed: Failed: Failed: Failed:Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed: Failed:

For each loop this gets longer.

Will this custom build fix this?
1
Rod Lasky Replied
Employee Post
Hi Bruce.  Yes, build 7164 will fix this looping.
Rod Lasky
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Bruce Replied
Thanks, Rod, for the quick reply.
2
Thomas Lange Replied
Thanks Kyle for the link to this custom build.
(btw: I suppose the MAPI-beta needs an updated/fixed build, too)

Bruce: I just installed custom build 7164 - looks good now!
But keep in mind in case your "Spool"-queue is already filled with thousounds of messages (we had 3.000 upto 8.000 Waiting for delivery!) you need to stop the SmarterMail service, then RENAME the Spool-Directory, and restart the SmarterMail-service. SmarterMail will then re-create a new spool-directory, including it´s  subdirectories.

Keep in mind you could loose emails: what was in the old-spool will not being send anymore! , thats why I suggest a rename of this folder and not a delete, to have the chance to manually check content/files.

0
Bruce Replied
I was able to clean the spool queues, but I have just been woken at 2am by a throttle notification and checked the spool on one of the servers and it has occurred again, 1,000's of emails with 'Failed: Failed:' subjects.

It looks like 7164  has not fixed the problem and the loop is still occurring.
0
Bruce Replied
It looks to be when you get a Failed Delivery notification from 'System Administrator' to a mailbox that is full that because the Failed Notification can not be delivered it then gets stuck in a loop.
0
Stefan Mössner Replied
Hello all,

I had the same issue with SmarterMail, build 7153. The new custom build 7164 and deleting the spool files helped me to get back a performant running SmarterMail.

Thank You.
0
Bruce Replied
I have not seen any more since 2am this morning, so I am hoping it was just a hangover from the previous version.
0
Stefan Mössner Replied
Hello all,

unfortunatelly it only worked for nearly one day. Again there were some mails with "Failed:". I'm using some addresses of my internal mail domain which doesn't exist as mailboxes for notifications from firewalls, IP cameras etc. I had to delete these mails for stopping SmarterMail to try to send them again and again. In the past releases of SmarterMail there wasn't such an issue. Why isn't SmarterMail stopping to send these mails after a few retries?

Kind Regards.
0
Bruce Replied
I am also still getting this but only now on one server, which has 12,000 mailboxs, but this issue only seems to affect one mailbox that sends email notifications but the mailbox is full so failed emails cannot be returned, so you end up with an email loop with the subject line;

Failed: Failed: Failed: Failed: Failed: Failed: Failed: 
0
Bruce Replied
OK, just found another mailbox that this is also happening too which is also rejecting email as the mailbox is full.

As a temporary fix I am increasing the size of the affected mailboxes so that they can receive the 'Failed' email and stop the loop.

Reply to Thread