Error in downloading mail on IMAP after ios 18 upgrade

I am unable to download my mail using the native mail app after upgrading to IOS 18. I am getting the following error; “Network Error (POSIX 96)”

The mail configuration is on imap with SSL.

iPad Pro, iPadOS 18

Posted on Sep 16, 2024 10:24 PM

Reply
Question marked as Top-ranking reply

Posted on Dec 30, 2024 10:21 AM

@ferrerod:

Here's the main part of the response I got from Fastmail who diagnosed and solved the problem on my account. It seems there was a bug in their mail engine that was benign until the iOS18 update, then no more. I hope this helps.


We had a bug which put random data into the HIGHESTMODSEQ value for some users. Their account was affected by this. We didn't think it was an issue because there was still heaps of number-space left, but the HIGHESTMODSEQ values were higher than a signed int64 can hold. This was fine because we use an unsigned int64_t internally, but the spec was updated a few years ago to make it a signed value, so we were strictly wrong.
 
Apple's parser couldn't handle these oversize numbers, and failed.
--
 
This has now been fixed by resetting the HIGHESTMODSEQ value for these users which also means this will never happen for them again.



ferrerod wrote:

Did fastmail tell you what technically they did? No one else has a workable solution. Some of us support our own mail serves - though perhaps rare.... would be great if you could get them to tell you exactly what they did for IMAP solution.


287 replies

Nov 22, 2024 5:44 PM in response to George Johnson

I have a dovecot/postfix server as well and am using lets encrypt for ssl, and am experiencing this issue too. I do not think it's an issue with self signed certificates.


No VPN here either.


Curious, has anybody brought this up on any Dovecot mailing lists yet? Or somewhere else? I am looking at their recent archives and see nothing. I do see this mentioned on Mac Rumors forums.


I have dovecot 2.3.19.1 (9b53102964) on a stock Debian 12 system at the moment. Postfix is working fine.

Nov 23, 2024 8:49 AM in response to plinss

plinss wrote:

https://doc.dovecot.org/2.3/configuration_manual/namespace/

In my case (Debian), it's in /etc/dovecot/conf.d/10-mail.conf, look for 'namespace inbox'

Thanks again. This morning I looked at my server configuration. (I installed Postfix/Dovecot using the Cutedge Systems GUI called MailServe. So Dovecot is installed at /usr/local/cutedge/dovecot.) The only configuration file appears to be . . . dovecot/etc/dovecot.conf. But that file doesn't contain a namespace setting, so I assume that Dovecot is falling back on whatever the default is.

Nov 23, 2024 9:58 AM in response to plinss

Thanks for the information. I'm going to dig into it a bit more later on but for now, here's my namespace section. I've been using the same config for years and forgot how/why it was initially set up this way. It's always worked great in macOS Mail, Thunderbird, and Roundcube webmail.


The entire namespace inbox section in 10-mail.conf is actually commented out on my install.


# NOTE: Assumes "namespace inbox" has been defined in 10-mail.conf.
namespace inbox {
  # These mailboxes are widely used and could perhaps be created automatically:
  mailbox Drafts {
    auto = subscribe
    special_use = \Drafts
  }
  mailbox Junk {
    auto = subscribe
    special_use = \Junk
  }
  mailbox Trash {
    auto = subscribe
    special_use = \Trash
  }

  # For \Sent mailboxes there are two widely used names. We'll mark both of
  # them as \Sent. User typically deletes one of them if duplicates are created.
  mailbox Sent {
    auto = subscribe
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }


Nov 23, 2024 2:49 PM in response to plinss

Alas:


Changing it from commented out to 'separator = "\\"' broke the server:

Nov 23 17:23:04 imap: Fatal: master: service(imap): child 91197 killed with signal 11 (core dumps disabled)


Changing it to 'separator = .' didn't break the server, but caused a new and questionable error message in iOS only:

Server code "CANNOT", server message "Invalid mailbox name: Name must not have '/' characters. 


Finally, Changing it to 'separator = \\' (no quotes) doesn't hurt (other mail clients work), but doesn't help iOS 18.x.

Nov 26, 2024 2:54 PM in response to mangalapandi

mangalapandi wrote:
May be i can help you to fix if you share the truncated logs while accessing Mail app to your server.

Well, I tuned on the several verbose debugging settings on dovecot, but it still doesn't seem terribly informative (personal info is obfuscated):


Nov 26 17:21:38 imap(pid 57854 user xxx.xxx): Info: ID sent: name=com.apple.email.maild, version=3826.200.121.2.3, os=iOS, os-version=18.1.1 (22B91), vendor=Apple Inc
Nov 26 17:22:11 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<KN3VR9gnEsAyZZIi>): mail SACL is enabled
Nov 26 17:22:11 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<KN3VR9gnEsAyZZIi>): user: xxx.xxx is member of mail SACL
Nov 26 17:22:12 imap-login: Info: Login: user=<xxx.xxx>, method=PLAIN, rip=##.##.##.##, lip=###.###.###.##, mpid=57854, TLS
Nov 26 17:22:12 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<L+zaR9gnFMAyZZIi>): mail SACL is enabled
Nov 26 17:22:12 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<L+zaR9gnFMAyZZIi>): user: xxx.xxx is member of mail SACL
Nov 26 17:22:12 imap-login: Info: Login: user=<xxx.xxx>, method=PLAIN, rip=##.##.##.##, lip=###.###.###.##, mpid=57854, TLS
Nov 26 17:22:12 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<bvHaR9gnE8AyZZIi>): mail SACL is enabled
Nov 26 17:22:12 auth: Info: od[sacl check](xxx.xxx,##.##.##.##,<bvHaR9gnE8AyZZIi>): user: xxx.xxx is member of mail SACL
Nov 26 17:22:12 imap-login: Info: Login: user=<xxx.xxx>, method=PLAIN, rip=##.##.##.##, lip=###.###.###.##, mpid=57854, TLS
Nov 26 17:22:14 imap(pid 57854 user xxx.xxx): Info: Connection closed (UID FETCH finished 0.684 secs ago) in=474 out=417293
Nov 26 17:22:14 imap(pid 57854 user xxx.xxx): Info: Connection closed (UID SEARCH finished 0.765 secs ago) in=2379 out=614477
Nov 26 17:22:14 imap(pid 57854 user xxx.xxx): Info: Connection closed (IDLE running for 0.001 + waiting input for 1.194 secs, 0.001 in locks, 2 B in + 10 B out, state=wait-input) in=85 out=1332


All I can say is that the app continues to say "checking for mail" long after the server says Connection closed, and other connections don't have Connection closed messages at all.

Dec 2, 2024 10:46 AM in response to Hari1975

any update from apple support? i know there are a few mixed issues in here, but I also see the same issue with an iOS 18 client and our dovecot server. Our separator is default (period) so not the double-backslash. I had submitted a Feedback Assistant ticket with logs etc November 6th and still have not gotten any resolution or natable update from Apple other than providing further information. Perhaps I could reference a similar Apple ticket from those of you who have submitted them. My ticket is FB15701211 fyi.

Dec 12, 2024 9:13 PM in response to plinss

running a dovecot imap server... I can see the folder structure for mailbox subfolders is using "." as the separator. In the conf.d/10-mail.conf I see


namespace inbox {


  # Namespace type: private, shared or public


  #type = private




  # Hierarchy separator to use. You should use the same separator for all


  # namespaces or some clients get confused. '/' is usually a good one.


  # The default however depends on the underlying mail storage format.


  #separator =




  # Prefix required to access this namespace. This needs to be different for


  # all namespaces. For example "Public/".


  #prefix =




  # Physical location of the mailbox. This is in same format as


  # mail_location, which is also the default for it.


  #location =




  # There can be only one INBOX, and this setting defines which namespace


  # has it.


  inbox = yes




  # If namespace is hidden, it's not advertised to clients via NAMESPACE


  # extension. You'll most likely also want to set list=no. This is mostly


  # useful when converting from another server with different namespaces which


  # you want to deprecate but still keep working. For example you can create


  # hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/".


  #hidden = no




  # Show the mailboxes under this namespace with LIST command. This makes the


  # namespace visible for clients that don't support NAMESPACE extension.


  # "children" value lists child mailboxes, but hides the namespace prefix.


  #list = yes




  # Namespace handles its own subscriptions. If set to "no", the parent


  # namespace handles them (empty prefix should always have this as "yes")


  #subscriptions = yes


}




# shared namespace configuration


namespace acl-mailboxes {


  type = shared


  separator = .


  prefix = shared.%%u.


  #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u


  #location = maildir:/Library/Server/Mail/Data/mail/%%u:INDEX=/Library/Server/Mail/Data/mail/%%u/shared


  location = maildir:/Library/Server/Mail/Data/mail/users/%%u:INDEX=/Library/Server/Mail/Data/mail/shared/%%u


  subscriptions = no


  list = children


}


This location does align with file system

/Library/Server/Mail/Data/mail/users/%%u

Dec 17, 2024 12:19 PM in response to Apple_strikes_again

still get POSIX 96 on occasion..., no vpn ever used. Some people say POSIX 96 error goes away with a reboot. Who cares if the error goes away but the email doesn't sync or land in the Inbox...?


iOS 18.2 installed overnight and it is already showing serious bugs ....but no Mail IMAP fix. I see the number of Unread Messages seems to be more accurate but when I visit that Inbox for IMAP, the messages are not there. Going to macOS Mail on macOS 15.1.1, I find the messages awaiting...it all went to crap in iOS 18...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Error in downloading mail on IMAP after ios 18 upgrade

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.