2
Question about Backup MX user verification
Question asked by Linda Pagillo - March 21, 2016 at 7:38 AM
Unanswered
Hello everyone. I noticed something that happened over the weekend when I was migrating a Smartermail installation from one server to another. Prior to the migration, I set up one of my other Smartermail servers as a backup MX for my primary server that I was migrating. Since my primary server is a Smartermail server, I enabled Smartermail Gateway Mode on the backup MX. I set it to use Web Service as the user verification type.I noticed that when I took my primary server down and tested sending to it, I received bounces stating 550 - no such user here. I believe this happened because since my primary server was down, the user verification couldn't happen, therefore, the messages bounced. Am I correct in this assumption? If yes, can someone tell me a way around this besides using no verification? Also, if I'm correct in my assumption, what is the point/value of Web Service verification if it doesn't work if the primary server is down? Thanks!
Linda Pagillo
Mail's Best Friend
Email: linda.pagillo@mailsbestfriend.com
Web: www.mailsbestfriend.com

7 Replies

Reply to Thread
0
Matt Petty Replied
March 24, 2016 at 8:25 AM
Employee Post
User verification via a web service would require the primary to be up, since that's how the user verification is done. Gateways are meant to "assist" the primary mail server. Using user verification this way would require the gateway to cache or pull all these values from the primary while it is still up in order for this to work, we currently do not do this.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Merle Wait Replied
March 24, 2016 at 8:49 AM
Thank you for your response.... 
So.. if I know that for whatever reason.. the primary becomes unavailable... either inbound gateway has to be switched to a backup service mode.   Correct?  But here is no auto-detection from the gateway to primary  - or notification that the gateway can not reach the primary.... :(
0
Matt Petty Replied
March 24, 2016 at 9:07 AM
Employee Post
Correct. However, generally backup mx servers are kept as backup mx servers, as far as I know people don't really hot swap between Backup and Gateway modes.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Linda Pagillo Replied
March 24, 2016 at 9:57 AM
Thanks for your response Matt. I have another question... it's my understanding that backup MX servers can be used as a kind of store and forward service in the event that the primary server is unavailable. I currently use Smartermail backup MX servers for this purpose. However, are you saying that if I'm going to use a Smartermail server as a backup MX, I need to choose no verification in order for it to work?
Linda Pagillo
Mail's Best Friend
Email: linda.pagillo@mailsbestfriend.com
Web: www.mailsbestfriend.com
1
Matt Petty Replied
March 24, 2016 at 12:07 PM
Employee Post
I've talked to Bryon about this and we will be classifying this as a bug. Backup MX without the ability to verify users without the Primary really hampers its ability to function as a backup. 

Currently the backup mx can only function as a true backup (without the primary available) if the user verification is off.
Matt Petty
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Webio Replied
March 24, 2016 at 12:30 PM
Hello,
 
what version of SM was one which you  where migrating? I was experiencing similar issues with some older versions. I was sending few support tickets about no such user here issue and from some time now I'm not experiencing this anymore (emails are being delivered when main server is back online and no such user here is not returning during primary server startup process). On my end I'm using Domain Forward -> All Domains with user verification using web service. I can't use Backup MX because my main server is not listed as a MX server.
 
Regards
0
Merle Wait Replied
March 24, 2016 at 1:56 PM
hi Webio, I am a little confused by the comment:  "I can't use Backup MX because my main server is not listed as a MX server."....
Since I never used SM in a true backup capacity, and only gateway mode(which I now understand.. is not so bright of an idea either... )   I wasn't aware the main server had to be listed in the DNS as MX record.  I was just using the I/P address of the main server....    AND more to the point as well.... the back-up AND current gateway servers take the emails and deliver them via internal I/P address 
 
Example:  
DNS MX: 122.122.122.122 --->gateway --> 192.168.52.52 --> MainServer
(true the main server has a public address too, but we choose to route the email internally to it).   All servers are 14.x
 
 
Not arguing... just trying to learn ... {which apparently I have a long way to go :) }

Reply to Thread