My accounts in Mail app stopped to sync post update

Same problem here with Cyrus 2.4.17.

98 / 5 000

We would expect a reassuring answer from Apple that they are dealing with our Mail problems at all !!!!!!

My hosting provider (Webland.ch) confirmed there is an issue syncing mails on iOS18 and Apple "found the cause and the problem should be fixed in the next iOS18.1 update".

I’m having the exact issue with Namecheap / Provateemail.com email that used to work with Mail iOS app. Please Apple. I didn’t buy new iPhone just to have issues like this.

I have the same problem, I have to use Mail only on the iPad and MacBook 😠

I updated to version 18.0.1 but the mail problem was not solved !!!!!!!!

AI can not - they need Old-School developer, as now there only managers and designers exist, which can not do anything good with code, but only draw pictures and prices.

Hi,

I had a similar issue with my email disappearing from multiple accounts, and after troubleshooting, I discovered that the problem was related to my self-hosted IMAP mail service on Synology. After updating the SSL certificate, the issue was resolved, and all my emails reappeared. If you're using a self-hosted solution, I recommend checking your SSL certificate as well.

Hope this helps!

We can’t report it because it doesn’t even give an option to choose Mail as the app that’s not working unless we are selecting it from a MacBook and it doesn’t give us the option to choose the iOS 18 as a software that we are having problems with for the bug report

I had the same issue with the mail.app and using register.com. All worked fine before I changed to IOS18. After I did, I was unable to send emails and received an INVALID ADDRESS response. I stopped in at the Apple Store and they couldn't help me neither did two calls to Apple, and one to REGISTER.COM. However, this morning, I spoke with Applecare support named Michelle and she suggested I add my user name and password to the outgoing mail server where it says optional. I did and VOILA! I'm back in business. May not work for everyone, but it did for me.

isp-Gil wrote:

...

If I assign “imap.mydomain.com” as the incoming mail server and “smtp.mydomain.com” as the outgoing mail server, the Mail application will not allow SSL to work on port 993 and will only accept the unsecured connection on port 143.

This anomaly also occurs when using the hosting system (first type), using different names for inbound and outbound servers.

This problem does not occur on IOS 17 !!!

...

This is interesting to me... I have a few email accounts that use IMAP. None of them are working on ios 18 or ipados 18... all of them worked in previous versions, and all the accounts work fine on macOS mail app.

one account has the email address like anyone@anyemail.com, but the mail server is bigrack.example.com

in other words, the email account domain is different than the domain of the email server. Is that where you see the problem happening for you? or do you mean that the send and receive names are different?

agentogden wrote:

its definitely IMAPS.

account settings > advanced

turn off use SSL, change port to 143.

Sadly that option won’t work for many as tons of servers are set to refuse non secure connections. That’s the issue I have. One server will just say “connection refused”, the other mail server will actually block a second connection attempt that’s not ssl or TLS.

so, I’m glad to read that you can make it work for you but consider it lucky that your server will allow you to go with insecure connections.

@2611-40: SSL has nothing to do with browsing the internet; it’s only related to email encryption as it ensures your email is secure and protected from prying eyes so disabling it will not make your browsing less secure;

[Edited by Moderator]

SSL has nothing to do with browsing the internet; it’s only related to email encryption as it ensures your email is secure and safe from prying eyes so disabling it will not make your browsing less secure

Could you please check if there is some difference in communication between a working server and one that's failing? I think it is something simple that has changed over the years in IMAP communication, maybe a CR-LF vs. LF only behavior in protocol communication or email listing or something... just guessing...