4 Commits

Include renames

Author	SHA1	Message	Date
jcoffey-dev	3cae9464f0	import: bound the memory an IMAP or EWS import holds ... Two things let a large mailbox fill memory. IMAP workers handed every fetched message to the archive writer through an unbounded queue, so fast workers could hold whole folders' worth of bodies while the single writer caught up. And fetch batches were sized by count only: 20 items per EWS GetItem, 8 connections at a time, is a few megabytes of ordinary mail and several gigabytes of large attachments. - The IMAP event queue is bounded at two events per worker, so a worker waits for the writer instead of running ahead of it. - Fetch batches are bounded by bytes as well as by count, with a shared helper, `sync::batch::by_count_and_bytes`: 32 MiB by default, and a single larger message goes alone. - IMAP learns each new message's RFC822.SIZE on the control connection, in 1000-UID metadata fetches, before the body fetch. A server that won't say leaves the chunks sized by count. `--fetch-batch-mib` sets the cap. - EWS asks FindItem for `item:Size` and packs GetItem batches by it, fetched `--ews-connections` batches at a time. `--ews-getitem-batch-mib` sets the cap. Items from an incremental SyncFolderItems run carry no size and stay batched by count. - docs/usage.md describes both options.	2026-09-30 12:32:29 -07:00
Maurus Decimus	f263f57c09	EWS fixes - part 3	2026-06-10 22:19:28 +02:00
Maurus Decimus	adbd0276a6	EWS fixes	2026-06-10 20:26:41 +02:00
Maurus Decimus	576073f8c9	Initial commit	2026-05-29 18:02:15 +02:00