We manage three different types of email servers.  Both of the others allow us to "Bounce" messages that can't be delivered but are being retried over and over again.  SmarterMail is the only one that doesn't allow this action.

 

For example, right now I have quite a few messages addressed to gmail.com accounts that are over quota.  The specific SMTP Response Code given by gmail.com is "452 4.2.2 The email account that you tried to reach is over quota."  Yes I'm aware that since it's a 4xx response code we should retry the message per the RFC, but when we see a pattern of the same addresses sitting in the Spool until the retry period expires grows old and frustrating.

 

If you would PLEASE add a Bounce action to the Spool that would Bounce the message back to the sender with the last SMTP Response Code it would help us out a lot... and help keep the Spool cleaned up.

 

Another prime example is when people accidentally send to @charter.com instead of @charter.net the messages sit in the Spool.  

 

Thanks much,

-Joe