New user here. I seem to be getting the “password required” prompt coming up once or twice every day, with the message “Server says " server is shutting down, please try again”". Once this happens, I can come hit “OK”, and things proceed properly, but in the meantime, the app is stuck there, just waiting for my input and not doing other stuff it’s supposed to be doing.
Is there any setting that will allow eM Client to just accept that it can’t retrieve mail for the time being, and go on with its life without prompting me, so that at some point when the server comes back up, everything is fine?
I guess the alternative is to set up an AHK script looking for that message and dismissing it automatically.
I am not a new user but this behaviour has become a much more serious nuisance in the last 6 months. It occurs on both Windows and MacOS versions of eM Client. I rely on an email service (Migadu) that manages multiple email domains for us, each with several mailboxes. Often though not always Migadu seems to send a respond saying that it is busy and will handle the request shortly but eM client then generates the misleading message reported by the OP. I don’t recall the problem occurring as frequently or at all up to earlier this year but it has become much more frequent recently. Importantly, I have not encountered the same problem with several other email clients including Thunderbird, Outlook, Apple Mail and Mailspring. As far as my experience goes, it is only eM client that behaves this badly.
Interesting - I also use Migadu. But as you say, other apps (I came here from Thunderbird/Betterbird, which had other fatal problems forcing me to move) don’t have this problem with them.
Provided your mail server is not having issues then you might possibly have incorrect mail server settings.
Go to “Menu / Accounts” and update what your Incoming and Outgoing mail server settings are and we can then see if there is any obvious error messages ?
I’ve verified that the settings are correct. But the good news is that the problem hasn’t recurred in several days.
@ghughes888 above thinks that the mail server IS having problems, but that this is a legal state for the server to be in; eM mishandles the situation by flagging it as an error, when the proper response would be to just let it be, trying again later. And that’s exactly what I’d like to see eM doing, because it doesn’t bring everything else to a halt with a modal dialog waiting (forever) for permission to proceed.
As a much longer term user of eM the explanation of incorrect mail server settings would require some change in those settings immediately prior to the initial occurrences of the error messages reported. I am absolutely sure that I did not make any such changes. Further, since the error messages were occurring on multiple machines under both Windows and MacOS, I would have had to have changed the settings on each machine.
I can confirm that the frequency of errors is much lower now - I suspect this is associated with the installation of the most recent release of eM. I am not sure that they have completely ceased as I have had the error message on a MacOS machine within the last 2 days but I think that may have been before I updated eM.
I should also note that very occasionally I get a similar message with the Mailspring client. I suspect that there is some interaction between how Migadu responds to repeated mail requests from the same IP address and how eM and Mailspring process Migadu’s response. I can also confirm that I have never encountered the problem with Thunderbird/Betterbird.
I’ve verified that the settings are correct. But the good news is that the problem hasn’t recurred in several days.
If it suddenly started working and you haven’t changed anything on your computer and have the correct mail server settings as you say, then “that sounds like a mail server problem to me” where your remote mailbox is not always available and so throws up an invalid password.
eM mishandles the situation by flagging it as an error, when the proper response would be to just let it be, trying again later.
Then if you believe eM Client is mishandling it as an error, lodge a support ticket via the VIP Support page who will investigate it and advise you.
Sometimes certain servers using eg: older authentication methods “might need specific extra settings to make them work correctly” depending on what your server uses. So that can also be a reason why you might be getting issues. But support will advise if you need anything like that.