Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iPhone mail ignoring IMAP path prefix after 10.3 upgrade

After upgrading one of my iPad mini's to iOS 10.3, the mail app no longer uses the IMAP path prefixes on any mail account I have. (I have five mail accounts configured, of which two use path prefixes.) My un-upgraded iProducts continue to work normally, so I can't upgrade them until this is resolved.

Has anyone else experienced this after the iOS 10.3 upgrade?

I've tried rebooting the iPad, deleting and re-adding the accounts, even setting the path prefix to /tmp to see if anything was being used. Nothing has worked. I know similar issues were discovered in the past, though I'd never experienced them. Is this a new issue, or the reintroduction of an old issue?

iPad mini Wi-Fi, iOS 10.3, iPad mini 2 Wi-Fi

Posted on Mar 28, 2017 12:50 PM

33 replies

Apr 25, 2017 12:24 AM in response to AndyAndersonJr

Potentially good news!

I upgraded to iOS 10.3.2 public beta 4 last night (in the UK) and it seems, for me at least and my work servers, the IMAP folder problem has now been fixed. It still had the issue in beta 3 but once beta 4 was loaded and I went to the folders they appeared as they should do.

So hopefully if this fix has solved the problem for all IMAP folders in general then hopefully Apple have resolved the issue and it will be incorporated into the final release of 10.3.2.

Matt

mpost89

Level 1

4 points

May 11, 2017 8:26 AM in response to shaulm

Same here, Mail burned through something like 13 GB over cellular, costing me almost a hundred dollars in overage before I noticed it. Glad to see I'm not alone here, I guess, since it means it's more likely to get fixed.

Strulf

Level 1

14 points

May 31, 2017 11:09 AM in response to nobulus

Oh that’s not my problem, I can see them as well. I just can’t get rid of the [Gmail] folder anymore; when I use a prefix in the mail settings of iOS, the connection to Google fails.

This used to work prior to iOS 10.3.

Strulf

Level 1

14 points

May 31, 2017 11:34 AM in response to B Bond

No I can’t update at the moment, still on iOS 10.3.1. I did delete the account already and several other steps but it’s already good to know that it might be fixed in 10.3.2. Just because nobulus said he still had problems on 10.3.2.

Thanks!

May 15, 2017 4:46 AM in response to Matthew Jennings3

Okay so it's now official Apple believes it's addressed this issue as they finally closed the bug ID. Waiting now for the release of 10.3.2 official....