Back to Community Threads
2
Bounce conditions
Idea shared by Webio - 6/6/2022 at 9:22 AM
Under Consideration
Hello,

I would like to propose a functionality which I could name "Bounce conditions" for Spool messages or something similar which would divide bounces caused by remote message and dns bounces. I'm using outgoing gateways and emails which are getting remote error like no such user or mailbox is full are still being tried to be delivered according to Spool settings (General section). There is already a param called DNS Errors Before Bounce. It would be good to have separate param like "Remote error bounce". This would allow to bounce messages to mailboxes which does not exist or are full right after first error instead of waiting whole time for Retry Intervals.

Thanks

3 Replies

Reply to Thread
0
Zach Sylvester Replied
6/6/2022 at 4:18 PM
Employee Post
Hello, 

Thanks for posting your idea in the community. I have gone ahead and submitted a feature request to management for this.  If anyone else wants this to be added please be sure to up-vote this post. 

Thank you, 

Zach Sylvester

System/Network Administrator
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
IMHO this is quite specific case for users which are using outgoing gateways. Currently I have configured Spool delivery intervals to:

5, 15, 30, 60, 90, 120, 240, 480, 960, 1440, 2880

and when remote server is returning error like no such user here this outgoing gateway instead of bouncing this message to main SmarterMail instance it tries each interval try to deliver this message. Probably if no gateway is being used this message would be bounced right away.

I presume that "DNS Errors Before Bounce" setting is not covering this scenario?
0
Zach Sylvester Replied
6/7/2022 at 9:05 AM
Employee Post
Hello, 

Thanks for the question. That is correct DNS errors are not covered here. Let me explain how that works. 

Say you send an email and the primary server is down that could be considered a DNS error since it didn't respond so say it's currently set to 3. 

It would go 5, 15, 30 Bounce 

If the server is currently overloaded and responds but says that the server is busy it will follow that entire interval sequence that you have. 

I recommend setting the DNS errors before bouncing to the same as the number of your spool intervals to ensure delivery. The only issue with this is if the client mistypes an email and it goes nowhere they will need to wait until the spool intervals finish to get a bounce message back from the server. 

I also recommend that you turn on SMTP user verification on your incoming Gateway server as it can cause more issues than it's worth like lost email on the gateway when the server goes down plus verification is already done at the SMTP level when email hits the main server. 

Please let me know if this answers your question. 

Kind Regards, 

Zach Sylvester

System/Network Administrator
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Set up Autodiscover for SmarterMailSmarterMail > Installation and Configuration
Configure SmarterMail as a Backup MX ServerSmarterMail > Installation and Configuration
Common Email Delivery ErrorsSmarterMail > Troubleshooting
Copy Mail Sent To or From a MailboxSmarterMail > Domain/User Configuration and Management
Explanation of Exchange ActiveSync Push FunctionalitySmarterMail > Desktop and Mobile Synchronization