What happens under the hood with bulk delete?

When you delete (or archive) messages quickly in a row, they do not go to the server one at a time. Senly batches all deletions within 220ms into one bulk-move request to `/api/email/threads/bulk-move`.

Benefits:

  • No rate-limit hit with your provider (Gmail / IMAP).
  • Connection reuse — IMAP does not have to reconnect 30 times.
  • Retry layer for Gmail "Command failed" throttling: on transient errors the server tries 3 times with backoff (300ms → 900ms → 2.7s + jitter) before reporting failure.
  • "Thread not found" counts as success — if the message was already gone, that does not trigger an error, because the end result (message out of inbox) is achieved.

Max 200 threads per batch. Beyond that, Senly splits automatically.

Question not answered?

Our team helps you personally.