All email account on one domain stopped working in mail clients. Webmail works
Hi all,
suddenly, this morning all email accounts on one domain stopped working on email clients.
These are emails that have been working fine for years now on the same machines and same email clients.
The webmail works fine, only email clients Pc's, macbooks, phones android, phones apple they all start getting error: We couldn't find the incoming IMAP server.
This is on the server where 100 more domains work without problem.
Only this one domain gives problems.
Tried to restart the server but no changes.
What could have gone wrong?
Ah yes, it happens on all tested IP's and they are not blocked in either CSf of cpHulk.
All passwords are 100% working and webmail is working.
-
sounds like whatever hostname you have defined as the IMAP server in your email client configurations cannot be resolved. If I were you, I would be checking DNS to make sure that the mailserver hostname that you use actually resolves globally. Maybe your domain is expired or somebody changed some DNS entries for your domain.
0 -
Thanks, but how come the webmail works fine?
0 -
We'll need some more details on this issue before we can provide much advice.
I do like mtindor's guess of the hostname having an issue. Inside the mailserver settings for one of the users, check the connection settings and see if the hostname they are using to reach the system is still valid with no DNS issues.
If that is working properly, you could check /var/log/maillog while trying to connect from an account to see if that leaves any interesting or helpful logs.
That's where I'd start - let us know what you find!
0 -
I checked the nameservers for the domain and it has the same hostnames as the other domains on the server (WHM) that don't give problems. Also checking at leafdns.com gives no errors, warnings or anything suspicious. No errors in /var/log/maillog on connecting the emails associated with that domain either.
0 -
We might need to see a ticket on this issue if there are no obvious error messages.
0 -
The same client has 2 more domains on the same server and are installed on the same computers and phones, and these work fine. All three domains have the same nameservers.
0 -
How can I open the ticket without going through my license supplier? Your system asks me to contact my server guys and I have a self-managed server.
0 -
A ticket would need to go through where you purchased your license, yes.
Did you check their mail client settings and confirm they had a valid imap server in place? And that you're able to reach it?
0 -
I submitted the ticket to my server supplier 14hrs ago but no answer. Ok I will wait for them.
How do I check if there is valid imap server in place?
Isn't this one imap for the whole server (WHM)?
As other domains / accounts work fine.0 -
You would have to check the actual settings inside one of the user's mail clients to see what server they are using to connect to. It could be anything, so you'll have to confirm what it is.
Once you have that server name, you'll simply need to try and connect using their details. You could do that through a mail client yourself, or you could try a telnet test to the port using their server name to see if it's open for connections.
0 -
Ok, thanks.
How do I use telnet test to check the server names and ports if they are working from their machines?0 -
I figured out about the telnet command.
It cannot connect to that particular domain. Any other domain does not reject connection like it does not exist. The SSL for the domain is active and running. The zones for the domain seem fine and when I send the test email from webmail to mail-tester.com it comes back as everything is 100%0 -
Ok, I've made progress by accident.
I did: telnet mail.domain.com 465 - and that failed
Then I tried telnet domain.com 465 - and that went through.
So I tried to add the email to the client with sever name just domain.com instead of mail.domain.com and that worked.
What could have caused this and how do I revert this server name back for this domain to mail.domain.com?0 -
We have details on using telnet here:
0 -
Can you please suggest something about my previous post?
0 -
You'll want to check the DNS for the mail subdomain. It would seem that something has caused that to break - a basic ping or dig check against that subdomain would show if there is a DNS problem.
You could either fix the subdomain and get that working or have them update the mail client to just use domain.com.
0 -
Please see if this discussion solves your issue? Particularly, see the workaround mentioned by bernard.borg here.
0
Please sign in to leave a comment.
Comments
17 comments