In Australia many ISP’s have offloaded the running of email to a company running ATmail.
A few months back eMclient stopped working. Eventually using security over a specified port worked butt still has the odd authentication issue.
ATmail support say their local people can assist butt they can’t so I’ve come to the bigger community.
Outlook over IMAP is still OK.
thanx
db:)
Need more info.
Does your server use an OAuth passwordless token to connect or and app password?
Or does it use a manual legacy IMAP username and password ?
Also what is your current IMAP Server address, Server Port and Security policy ?
Lastly what version of eM Client do you have ?
and do you have Windows or Mac & OS version?
Using primary password as app password have a known issue.
Manual legacy IMAP
We tried different server addresses, aliases … SSL ports
Win 11
I did suggest they setup their own version to test
thanx
db:)
Using primary password as app password have a known issue.
You carnt use the primary email password as an app Password.
If ATmail requires an App Password, you have to “generate an app password” via the ATmail account area if they support that.
Manual legacy IMAP
We tried different server addresses, aliases … SSL ports
Win 11
If ATmail don’t use app passwords and the automatic account wizard setup doesn’t work with OAuth passwordless token setup and you are manually setting up the account as IMAP with a legacy username and password in eM Client via “Add Account / Mail / Other” then these are the V6-10.2 or V10.3 or higher IMAP secure Server Ports & Security Policies you can use.
Googling ATmail the IMAP server addresses appears to be imap.themessagingco.com.au
eM Client V10.3 or higher
(IMAP)
Port 993 "Use TLS on Special Port”
Or
Port 143 "Use STARTTLS if available”
(SMTP)
Port 465 "Use TLS on Special Port”
Or
Port 587 "Use STARTTLS (Always)”
—
eM Client V6 to V10.2
(IMAP)
Port 993 Use SSL/TLS on special port (legacy)
Or
Port 143 Use SSL/TLS if available
(SMTP)
Port 465 = Use SSL/TLS on special port (legacy)
Or
Port 587 Force usage of SSL/TLS
Level 2 support explained the web password should always work. App passwords were optional butt I have had issues where they cease to function. I need to erase them all and regenerate them. So for debugging purposes I stuck with the web password. I’ve tried your setting combinations including different names for the servers with level 2 support. Will have a another go … thanx