Email Attachments as File Transfer

Email is the file transfer system nobody chose and everybody uses. It multiplies copies across mailboxes, offers no revocation and no audit trail, and bounces anything large — yet it remains the default because it is right there, and because the alternative was never made as easy.

This series takes attachments seriously as infrastructure: why the medium fits transfer so poorly, where size limits actually come from (and why the file grows in transit), the journey through scanners and rewriters that delays or alters delivery, security policy that respects users, change management for weaning teams onto better paths — and the honest case for when a small attachment is perfectly fine.

Articles in This Series

• Why Email Is a Terrible File Transfer System That Everyone Uses Anyway
  Copies everywhere, no revocation, no audit — written with empathy.
• Attachment Size Limits: Where They Come From and Why They Vary
  Client, server, and gateway limits stacked — plus encoding overhead.
• The Journey of an Attachment: Servers, Scanners, and Rewrites
  Why attachments arrive late, altered, or not at all.
• Weaning Users Off Attachments: Alternatives That Actually Stick
  Making the secure path the easy path, pilots, and the holdouts.
• Attachment Security: Malware, Spoofed Files, and Safe-Handling Policy
  Risky types and disguises, user coaching, and the incident playbook.
• When Attachments Are Fine: A Pragmatic Small-File Policy
  The honest counterpoint, with a one-page policy template.

Explore More Topics

This series is part of the Sysax file transfer topic library, which covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build: Sysax Multi Server, a secure FTP, FTPS, SFTP, and HTTPS server for Windows, and Sysax FTP Automation, which schedules and scripts secure transfers so the routine ones run themselves.