Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

iCloud IMAP Error

#2782

I started receiving pop-ups from MailMate this morning:

MailMate encountered the following error: “Server response: “C3 BAD Partition pending requests queue is full: partitionMaxPending=128 (took 2309 ms)”.”.
Mailbox: “Junk”.

I tried Retry and it went away for a bit, then came back multiple times. I closed and reopened MM and am seeing them still. I've not yet rebooted my laptop.

Version 1.13.2 (5673)

Thanks, Benny.

Des

Reported by Des Dougan · March 19th, 2021 @ 04:05 PM

State: cantreproduce
Milestone: none
Assigned to: benny benny

Activity

  1. Des Dougan
    Des Dougan

    As I was posting this, I noticed on the create ticket window:

    "Upload Quota Reached. Please notify the account owner."

    March 19th, 2021 @ 04:06 PM

  2. benny
    benny
    • State changed from new to cantreproduce

    Rebooting won't help. This appears to be a server issue. For now, you can try taking the Junk mailbox of the account offline, e.g., for 24 hours. Then take it online to see if the issue has gone away.

    (I have no idea what the iCloud IMAP error message means and I've never seen it before. It seems to be rare since googling for it didn't reveal anything.)

    March 19th, 2021 @ 08:16 PM

  3. Des Dougan
    Des Dougan

    After I told it not to retry, the message has not reappeared.

    Thanks for getting back to me, Benny.

    March 22nd, 2021 @ 05:23 PM

  4. benny
    benny

    Make sure the Junk mailbox in the account is back online. Find it under Sources in the mailbox list.

    March 22nd, 2021 @ 07:00 PM

  5. Mark Chapman
    Mark Chapman

    In case it is helpful I have started to get a similar message today:

    MailMate encountered the following error: “Server response: “D3 BAD Partition pending requests queue is full: partitionMaxPending=128 (took 3228 ms)”.”.
    Mailbox: “Junk”.

    Retry just brings it back moments later. Oddly, I got a similar error for another mailbox earlier and Retry made it go away.

    Server response: “D3 BAD Partition pending requests queue is full: partitionMaxPending=128 (took 711 ms)”.”.

    Mark

    March 29th, 2021 @ 05:20 PM

  6. Jon
    Jon

    Got the same error as Mark today.
    In my case MailMate seemed to have been locked up and one of buttons on the dialog were clickable (grayed out).
    Even stranger after I force quit MailMate, the dialog is still on my scree.
    When I opened MailMate back up it was not responding for about 2 minutes, then it came back up...

    March 29th, 2021 @ 05:25 PM

  7. benny
    benny

    This still seems to me to be a server issue, but I've had several reports about it recently. @Jon: Maybe MailMate isn't handling this error as gracefully as it should. Could you generate logs for me like this if possible:

    • Open the “Activity Viewer” in MailMate (Window menu). This enables logging.
    • Observe a few rounds of this error.
    • Use “Help > Send Server Logs”.

    Then I'll see if MailMate could be part of the problem.

    March 29th, 2021 @ 08:04 PM

  8. Amy
    Amy
    • State changed from cantreproduce to new

    Is this an ongoing problem for others? I just got the same message: "D3 BAD Partition pending requests queue is full: partitionMaxPending=128 (took 4 ms). Mailbox: INBOX" Any suggestions?

    December 14th, 2022 @ 09:35 PM

  9. Steffen
    Steffen

    I just now got the same error message (for all mailboxes on my iCloud account: Inbox, Junk, Deleted Messages, ...).

    December 14th, 2022 @ 10:38 PM

  10. benny
    benny
    • State changed from new to cantreproduce

    My primary advice is still the same. Take the account offline and retry later.

    Maybe also check your IMAP account settings. Make sure you are using imap.mail.me.com/smtp.mail.me.com. If settings were imported from Apple Mail in the past then they might be different. This could be a problem if it forces MailMate to connect to specific iCloud server instances and those instances have the issue you are experiencing. (I don't really know how iCloud works server-side. This is just a wild guess.)

    December 15th, 2022 @ 07:09 AM

  11. Steffen
    Steffen

    In my settings there were more specific addresses indeed. I changed it to the more general form as you suggested. The error message hasn't popped up since.

    December 15th, 2022 @ 09:25 AM

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.