When eM has an error, that is later corrected, the error indicator & message should automatically clear.
When a user needs to manually “ignore” an error - that logically means the error condition and its underlying cause is still present. But as an example, if the error is a failure to sync, and a second sync successfully completes, there is no active error and the client should reflect that.
Keeping the error log available for diagnostic purposes is valuable - but for standard use continuing to display the error is more confusing than helpful.
1 Like
What error are you getting?
Could be any kind. Sync error, failure to send, or other common error that might be caused by a temporary server problem, or a network connectivity, or sometimes a mis-typed address. As soon as the underlying cause is corrected and the problem resolved - eM should clear the error indicator and remove the message. But it doesn’t.
If it’s a eg: Physical Network error or TCP/IP software issue, the error message normally does automatically go away if you either close eM Client and re-open it or click refresh at the top.
Most mail clients will normally need to be “closed and reopened” to acknowledge a fixed network connection unless you are very lucky.
Not that I’ve seen. Yes - closing and re-opening removes the error unless it’s underlying cause is still present. But a transient issue (like a failure to connect that is then corrected) should clear itself.
It’s also a wording issue. Having “Ignore” being the method to clear an error is quite confusing. I can choose to “Ignore” a failure to connect to a given server/account to continue working with other accounts. And “Ignore” indicates a conscious acknowledgement of a known condition and a decision to proceed regardless.
Having a momentary failure to connect to Gmail/Hotmail - that makes sense…but as soon as they re-connect the error should self-clear. Without needing to close/re-open the program.
Pressing “Ignore” for a failure to deliver means…what? Did the message get sent to some receipients but not others? Is the message still in my outbox? Did it get saved to Sent? This is a common example for me so it sticks out.
This issue still hasn’t been resolved. I just had a message that had a send failure. Why - I guess my server had a hickup. Just because. So I get a fail to send error.
That’s reasonable. Better would be an automatic retry…but reporting the error is fine. Now, I go to the Outbox, and refresh…and it sends. All good. But…the error is still showing active.
The failure has been cleared - therefore the status should clear. But it doesn’t. And with the only available option being, “Ignore” - that implies the error is still active and ongoing and I’m choosing to manually “Ignore” it. This is not an intuitive action and is unnecessarily confusing.
1 Like
Yes - closing and re-opening removes the error unless.
This is not normal with eM Client that you have to keep closing and reopening eM Client to get the email to work and constantly getting errors.
If you are using the latest eM Client for whatever version you have, then could be related to an eg: Optional program installed possibly interfering with the mail client. Programs that sometimes cause issues are eg: Optionally installed Firewall / Security program, Optionally installed Antivirus program & VPNs. So if you have anything like that installed, try completely disabling those to test.
Now if you have no optional programs like that installed or if you do but made no difference disabling them, then could be you might have an outdated eM Client program and might need to update. You can see and d/l all the various versions of eM Client from the release history page. If you do update, backup eM Client before updating via “Menu / Backup” incase you need to restore for any reason. Also close eM Client before updating.
Lastly if you already have the latest eM Client for your current version, then update in this thread your current incoming and outgoing mail settings so we can check them incase there is a settings problem.
Respectfully, you didn’t read my last post fully.
I didn’t say I have constant errors. I said I had AN error - which was due to my server. And while we don’t like errors - they can occur.
The error was server side. It fixed itself. So the client should fix itself - and simply re-sending was all that was needed. My point is after the successful re-send the error status should clear. It doesn’t. That’s not good.
I said I had AN error - which was due to my server. And while we don’t like errors - they can occur.
If your mail server has connectivity issues where it’s not always constantly available, then you need to contact your mail server technical support and get that resolved. Then the errors won’t normally appear unless there is a eg: actual Mail server outage or Permanent mail server problem with the mailbox.
eM Client shouldn’t automatically remove error messages “when mail servers have problems or are unavailable”, as mail clients “are designed to report them so you can then get them fixed”.
It would be irresponsible for developers to just hide errors like that automatically. Users need to know if there are problems with mail servers.
It must be a language problem. I can’t explain this otherwise.
It’s proper and appropriate for a client to report when a problem occurs. That’s not in dispute. But the client should indicate when the problem is fixed - and this program doesn’t do that.
That’s simply wrong. No other mail client I’ve ever used behaves this way. Not in Windows, not in Linux, not in Android.
If nothing else, the button in the dialog should say something like “acknowledge” instead of “ignore”. But there should still be an indication that the problem has been corrected.
1 Like
the client should indicate when the problem is fixed - and this program doesn’t do that.
No mail clients don’t normally know when mail server issues are resolved. They normally just stop and wait for user input once error windows appears. So you then have to manually do that.
No other mail client I’ve ever used behaves this way. Not in Windows, not in Linux, not in Android
As you claim this should be different and works in your other mail clients, then put your suggestion on the eM Client Sleek Plan Suggestion share and voting page.
Wow, what a frustrating back on forth for what is an obvious problem