Follow-up to #295/#318. The new targeted UID EXPUNGE (IMAPFolder.expunge(Message[])) throws MessagingException("UID EXPUNGE not supported") on a server WITHOUT the UIDPLUS capability, rather than falling back to an untargeted expunge() — which is the correct SAFE outcome (fail-loud, no data loss), but means delete/expunge stops working entirely on a non-UIDPLUS IMAP server. Gmail/Outlook and most modern servers advertise UIDPLUS so the common case is fine; this covers rare self-hosted/legacy servers. Options: surface a clear user-facing error, OR fall back to an untargeted expunge only when it's provably safe (no other \Deleted-flagged messages in the folder). Backlog — edge case, current behavior is data-loss-safe.
Follow-up to #295/#318. The new targeted `UID EXPUNGE` (`IMAPFolder.expunge(Message[])`) throws `MessagingException("UID EXPUNGE not supported")` on a server WITHOUT the UIDPLUS capability, rather than falling back to an untargeted `expunge()` — which is the correct SAFE outcome (fail-loud, no data loss), but means **delete/expunge stops working entirely on a non-UIDPLUS IMAP server**. Gmail/Outlook and most modern servers advertise UIDPLUS so the common case is fine; this covers rare self-hosted/legacy servers. Options: surface a clear user-facing error, OR fall back to an untargeted expunge only when it's provably safe (no other `\Deleted`-flagged messages in the folder). Backlog — edge case, current behavior is data-loss-safe.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to #295/#318. The new targeted
UID EXPUNGE(IMAPFolder.expunge(Message[])) throwsMessagingException("UID EXPUNGE not supported")on a server WITHOUT the UIDPLUS capability, rather than falling back to an untargetedexpunge()— which is the correct SAFE outcome (fail-loud, no data loss), but means delete/expunge stops working entirely on a non-UIDPLUS IMAP server. Gmail/Outlook and most modern servers advertise UIDPLUS so the common case is fine; this covers rare self-hosted/legacy servers. Options: surface a clear user-facing error, OR fall back to an untargeted expunge only when it's provably safe (no other\Deleted-flagged messages in the folder). Backlog — edge case, current behavior is data-loss-safe.