Does attachment 2 mean version two? Batch names, MIME and byte-count evidence

A staged rename distinguishes files; it does not certify versions, deduplication or contents

Each save creates batch-local usedNames. uniqueName detects conflicts case-insensitively and preserves files under numbered names instead of merging/dropping contents. contentType comes from the extension; byteCount estimates source size. None establishes business version, actual format, byte identity or redaction. No archive deduplication/inspection service is added.

Different from item review, encoding and revision retention

Items concern content/stages, encoding concerns serialization, retention relates revisions. Here original-to-staged names and metadata evidence matter. No real file is copied, renamed or disclosed.

Check Verified scope Manual review Not established
Local names usedNames for one batch Batch/item IDs/original reference Whole-inbox/account deduplication
Case lowercased collision checks Original/staged mapping Case variants prove identical content
Suffix Preserve/number conflicting files Name occupancy Version 2/latest approval
Name cleanup Name-character processing Label versus actual material Security scan/content identification
Type hint Extension-derived UTType/MIME Actual format/destination Suffix proves trusted contents
byteCount File/package size estimate; read failures separately Measured size/actual copy Same size means same SHA
Staging budget 200 MiB measured-file accumulation Not every text/page limit Every site accepts 200 MiB
Retention identity Batch/item/id/reference separately Real version/content evidence Name/number/MIME are business identity

Synthetic naming illustration

One batch contains sample.txt followed by SAMPLE.TXT; the latter can become SAMPLE 2.TXT. This is a collision suffix, not business v2, equal contents or automatic merging.

Other batches can reuse names. Type/size are not cryptographic digests. Use authorized originals/actual bytes/content for revision review instead of disguising formats or bypassing handoff/access through renaming.

FAQ

Does suffix 2 mean business v2?

No. Local naming occupancy is not approval/version order.

Are case variants retained without renaming?

Current checks lowercase conflicts and number candidates, without merging contents.

Does this globally remove duplicate contents?

No. Batch-local name uniqueness is not content deduplication.

Does MIME prove real format?

No. Extension inference differs from content/destination evidence.

Does equal byteCount prove equal bytes?

No. Size is neither SHA nor authenticity.

Were files copied/renamed/inspected?

No. Synthetic/source review only, without attachment operations/services.

Reading and source

Per-item checks · Encoding/names · Version material · File bridge stages · Start · Privacy

Naming/sizes/save · Files/later placement