1
Delay emails not always being sent
Problem reported by John Quest - 9/12/2024 at 9:02 AM
Resolved
I have discovered a bug in the way Smartermail deals with delay notifications. 

There is some confusion within Smartermail whether this needs to be treated as a bug or as a idea/feature request.

What is happening (and is happening a lot more in today's environment with so many parked domains) is that when an outgoing email is attempted to be sent, a MX lookup is done and if none is found then delivery is attempted to an A record. IF that A record connection TIMEOUT then the delay notification is NEVER sent, per the configured number of tries. 

This is considered a bug in the way Smartermail handles this. A delivery attempt is a delivery attempt. A failed delivery attempt must be counted as a failed delivery attempt regardless of why.

7 Replies

Reply to Thread
0
Zach Sylvester Replied
Employee Post
Hey John, 

Thanks for reporting this issue. I just created a dev task to get this fixed. 

Kind Regards, 

Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
0
John Quest Replied
See ticket 263-2E5F56C2-001E
0
Zach Sylvester Replied
Employee Post
Hey John, 

We just applied a fix for this bug internally. It will most likely be in the next release. 

Thanks, 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
0
Zach Sylvester Replied
Employee Post Marked As Resolution
Hey Guys, 

This issue was fixed in the newest release. I will mark this as resolved. 
Have a great rest of your week. 

Kind Regards, 
Zach Sylvester Software Developer SmarterTools Inc. www.smartertools.com
0
John Quest Replied
It will probably be next week before I can apply the latest release.
0
John Quest Replied
So far, running 9042, it does not appear to be resolved. I will respond to the support ticket.
0
John Quest Replied
UPDATE: This was indeed confirmed as a different bug when it involves the server being configured as a gateway for another server, such as Exchange. 

Reply to Thread