3
Smartermail not handling mailing list addresses locally in split domains
Problem reported by David Sovereen - 11/16/2015 at 3:16 PM
Resolved
Hello,
 
We have a split domain (mercury.net) with some email users on SmarterMail and others in Office 365.  Our MX record points to Office 365.  Smartermail has the domain configured as Domain Location: External (use MX record).  Office 365 has the equivalent setting, knowing to send e-mail to non-local @mercury.net addresses to Smartermail.
 
The problem is that Smartermail is not treating mailing list addresses as local and processing them accordingly.  When a message is sent from an Office 365 user to a mailing list configured in Smartermail, Office 365 sends the message to Smartermail and then Smartermail sends the message back to Office 365 and then Office 365 sends the message back to Smartermail, and then Smartermail sends the message back to Office 365, and that continues until Smartermail eventually responds with:
 
Maximum hop count exceeded. Possible loop.
 
Smartermail needs to treat mailing list addresses as local and process them.
 
Hopefully Smartermail can create a custom build for us to fix this sooner than later.
 
Thanks,
 
Dave

5 Replies

Reply to Thread
0
Employee Replied
Employee Post
Dave, do you have "Deliver locally if user exists" checked?
1
Employee Replied
Employee Post
Dave, I have set up a test in which I was able to duplicate this scenario.  This has been added to our bugs list.
0
David Sovereen Replied
Yes:

Deliver locally if user exists: Enabled

And it does deliver locally to Users, but not to Mailing Lists.

I quickly tested Aliases (so you could fix it at the same time if they were also having the problem) and they are broken too.

Users work, Aliases and Mailing Lists do not.

Thanks,

Dave
0
David Sovereen Replied
As an FYI, however, the problem does NOT to appear to affect Aliases. It only affects Mailing Lists. I was trying to get out of the office and when my messages to an Alias didn't show up quick enough, I assumed it was going to fail like Mailing List messages do. However, it did not. The moment I left the office, the message came through on my phone. I wasn't in a position to update this until now. Sorry. Wrong Assumption. Problem affects Mailing Lists but not Aliases.

Glad you tested/recreated using Mailing Lists so you could validate the problem!

Dave
1
Employee Replied
Employee Post
Dave, this issue has been resolved and will be included in the next minor release.  If you would like an interim custom build, please contact sales@smartertools.com

Reply to Thread