2
Authentication failed on just 1 domain
Problem reported by Graham Smith - 11/11/2015 at 9:51 PM
Submitted
I have a about 12 domains running on a 8.4 Server.  All working fine for last 2+ years.

Out of the blue, on 1 domain, we are getting Authentication failed on POP and SMTP using Outlook etc - just this 1 domain
 
Have triple/quadruple checked credentials. Can log in via Webmail, no problem.
 
Have tried recreating the domain, problem remains

Out of ideas - any input is welcomed
 
Thanks
Graham
 

8 Replies

Reply to Thread
0
Bruce Barnes Replied
Double check the IP address assigned to the domain under DOMAIN ===> EDIT
Bruce Barnes ChicagoNetTech Inc brucecnt@comcast.net Phonr: (773) 491-9019 Phone: (224) 444-0169 E-Mail and DNS Security Specialist Network Security Specialist Customer Service Portal: https://portal.chicagonettech.com Website: https://www.ChicagoNetTech.com Security Blog: http://networkbastion.blogspot.com/ Web and E-Mail Hosting, E-Mail Security and Consulting
0
Graham Smith Replied
Hi Bruce
 
Thanks for your input.
 
Have checked that setting and it has a correct IP address assigned - doesn't seem to have a bearing, issue persists

 
0
Richard Frank Replied
if webmail login works, than outlook must be the culprit?
1
Bruce Barnes Replied

Could also be that port 25 is blocked for SMTP clients, by the user's ISP -- not at all uncommon these days

Make certain you have port 587 mapped and avaliable,  and have them try their SMTP connection for the client on port 587.
See:

https://portal.chicagonettech.com/kb/a104/blocking-of-alternate-smtp-port-587-by-isps-now-prohibited.aspx

for more information.

Bruce Barnes ChicagoNetTech Inc brucecnt@comcast.net Phonr: (773) 491-9019 Phone: (224) 444-0169 E-Mail and DNS Security Specialist Network Security Specialist Customer Service Portal: https://portal.chicagonettech.com Website: https://www.ChicagoNetTech.com Security Blog: http://networkbastion.blogspot.com/ Web and E-Mail Hosting, E-Mail Security and Consulting
0
Graham Smith Replied
Hi All
 
Thanks for the ideas - SM is on our own dedicated Server.
 
We have tested this issue in Outlook from a number of different PCs/locations with the same result
 
Seems this specific domain is being routed via a 3rd party dynamic DNS.  Aparently their Server was updated recently and we suspect this is causing the issue
 
We are waiting to hear from their support people but i'm "quietly confident" this is the problem
 
Thanks again
 
1
Bruce Barnes Replied
All SmarterMail installs must be on STATIC IP addresses.
Bruce Barnes ChicagoNetTech Inc brucecnt@comcast.net Phonr: (773) 491-9019 Phone: (224) 444-0169 E-Mail and DNS Security Specialist Network Security Specialist Customer Service Portal: https://portal.chicagonettech.com Website: https://www.ChicagoNetTech.com Security Blog: http://networkbastion.blogspot.com/ Web and E-Mail Hosting, E-Mail Security and Consulting
0
Paul Blank Replied
From what Graham said, it seems as if the server does have a static IP, but the DNS routing is some form of dynamic arrangement. 
 
I have this (successful) situation with Symantec Email Security.cloud filtering. They process incoming and outgoing emails and relay them to/from Smartermail and other email servers that I maintain.  "cluster5.us.messagelabs.com", for example, is in the MX record. They give this, or variations on this, to different accounts. The secondary MX entry would be, for example, "cluster5a.us.messagelabs.com".
 
Outgoing emails are sent from this cloud service using one of many outbound IP addresses - yes they do change all the time - and this routing works just fine.
 
I've been using this service for several years (back then it was called Messagelabs). Interested to know the final resolution of Graham's issue.
 
 
 
2
Graham Smith Replied
Thanks for all the input and comments
 
Our server does have a fixed IP.  The present DNS routing via a 3rd party is purely for flexibilty reasons, no mail security reasons or such like.
 
We are in the process of changing the domain settings to bypass the present DNS routing and route directly to our name servers/server
 
We are confident this will resolve the issue
 

Reply to Thread