How to disable RFC2087 on an IMAP account QUOTA Feature

Great... Tried rebuilding the database and MailMate exits. It must be having an issue with a mailbox? Core file attached.

You can disable it like this (for all accounts though):

defaults write com.freron.MailMate MmIMAPQuotaDisabled -bool YES

I'm also looking into why the IMAP server fails. What is the hostname in this case?

Sorry, didn't see your rebuild-attempt. You shouldn't have done that... :-| It might be crashing because you have also used the “Custom Location” feature in the General preferences pane, but that's just a guess (there's a known issue with that combination I haven't fixed yet).

I'm not sure how you can most easily get up and running since I'm not sure exactly what state MailMate is in now. It might be easiest to force MailMate to re-fetch all emails from the servers. This is done by removing the following folders/files:

~/Library/Application Support/MailMate/Database.noindex
~/Library/Application Support/MailMate/Messages.noindex
~/Library/Application Support/MailMate/Messages
~/Library/Application Support/MailMate/Attachments

Then launch MailMate. You still need the defaults command in my previous answer.

hostname = mail.messenich.com

Attached is the dialog with the server leading up to the error. The attempt to rebuild the database failed. Making progress after changing MmIMAPQuotaDisabled -bool YES (thanks for that)

It's refetching mail from the server. Just fwiw, the General Preference pane Messages Folder is default with Indexed for Finder/Spotlight checked.

I just realized that your accounts does have an INBOX which means the fix won't work. That makes it seem like a server issue, but I'll look into a workaround.

Ok, second attempt to fix this. In a few minutes you can hold down ⌥ when clicking “Check Now” in the Software Update preferences pane. You should get r5464+.

Sorry about the inconvenience.

Thanks Benny for the careful and timely attention to the issue. I deleted MmIMAPQuotaDisabled and loaded r5464. The fix is working against the problematic server.

Thanks for letting me know.