iCloud doesn't automagically refresh, gives IMAP error code when manually refreshing.
-
benny
Based on the error the server appears to tell MailMate that a command was too long. I'm not sure how that would happen, but you can provide more details like this:
- Open the Activity Viewer in MailMate
(⌥⌘0).
- Trigger the error message.
- Use “Help ▸ Send Server Logs” in MailMate.
Thanks in advance.
- Open the Activity Viewer in MailMate
(⌥⌘0).
-
Roland Dobbins
Logs sent.
-
benny
- State changed from new to accepted
This is what happens:
05:23:55 Storing flags 05:23:55 C: H8 UID STORE 82059:82061,82065:82066,82068,82072,82075,82077,82079:82080,82084,82089: ... 05:23:55 <19762 bytes> 05:23:55 C: ... 4918:94947,94949:94950,94952,94954:94963,94965:94970,94972:94990 +FLAGS.SILENT (\Seen) 05:23:56 S: H8 BAD Command line too large 05:23:56 Error: Server response: “H8 BAD Command line too large”.The server does not like a command with 19762 bytes. I think this happened when you had a mailbox with a few distributed messages already marked as seen and then you marked all the other messages as seen. Nothing wrong with that, but it triggered the problem above.
MailMate could work around this by assuming that “BAD” means “too large”, but it's not straightforward. I'll track progress on that in this ticket.
I think you can solve your problem for now by marking all the messages as unread. Then wait for the change to synchronize with the server. Then mark them all as read. This should prevent the generation of a very long command.
-
benny
- State changed from accepted to fixreleased
Just for the record, this type of problem was fixed some time ago by enforcing a limit on the length of a command with UIDs generated by MailMate.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.