Why Is Sending an Email So Expensive? Breaking Down the Hidden Costs Behind Email
Email transmission is nearly free; the real cost is getting the recipient to trust and accept the message.
Starting from a Hacker News discussion on why sending email is so expensive, the article breaks down the real cost structure. SMTP's open design makes transmission nearly free, but the spam flood forced the ecosystem to add SPF, DKIM, and DMARC, requiring senders to maintain DNS records, manage keys, and monitor results. IP reputation takes long-term compliant sending to build, and new IP warm-up is itself a hidden investment. Commercial email pricing reflects deliverability optimization and compliance support rather than bandwidth; transactional and marketing email differ in cost because they require different trust levels. Sending at scale amplifies complaint risk and compliance burdens, making marginal costs rise rather than fall. The conclusion: what's free is the interface; what's expensive is trust maintenance.
Introduction: The Price Paradox of an Email
To most people, sending an email is almost zero cost—click send, and it arrives on the other side of the world in seconds. But a recent discussion thread on Hacker News raised a counterintuitive question: why is sending an email so expensive? Although the post had only 9 upvotes and 3 comments, it touched on a long-neglected corner of internet infrastructure.
On the surface, the question sounds like a dry joke, but it points to the full cost chain of the email system—from protocol design and anti-spam mechanisms to commercial email delivery services. Only by understanding these costs can we understand why, behind "free" email, there is an expensive invisible bill.
The Email Protocol Itself Is Not Expensive—What's Expensive Is "Delivering Credibly"
The design philosophy of the SMTP protocol is openness and mutual trust: any server can attempt to deliver email to another server. This decentralized design made email almost barrier-free in the early days, but it was precisely this openness that planted the seeds for the later flood of spam.
After spam became one of the internet's main sources of pollution, the entire ecosystem was forced to add layer upon layer of "trust verification" mechanisms. Senders need to prove they are not spammers, and recipients need to judge whether an email deserves to land in the inbox. The operating costs of this mechanism are ultimately distributed to everyone who sends email in good faith. In other words, email itself is not expensive—"getting the other side to trust you" is.
Infrastructure Costs Brought by Anti-Spam Mechanisms
To combat spam, the email ecosystem introduced sender authentication technologies such as SPF, DKIM, and DMARC. These technologies are themselves standardized and free, but for them to actually take effect, senders need to maintain DNS records, manage keys, configure policies, and continuously monitor authentication results.
For individual users, these configurations are hidden behind email service providers; but for self-hosted mail servers or enterprises that send email in bulk, each item is a real operational investment. IP reputation management is an even longer-term project: a new IP needs to go through a "warm-up" process and gradually build sending reputation, otherwise a large number of emails will land in the spam folder. Reputation cannot be bought; it is cultivated through time and compliant sending behavior, which is itself an expensive hidden cost.
The division of labor among SPF, DKIM, and DMARC: The three are often mentioned together, but they operate at different levels. SPF (Sender Policy Framework) declares in DNS which IPs are authorized to send email on behalf of a domain, allowing recipients to verify whether the sending server's address is legitimate; DKIM (DomainKeys Identified Mail) uses the domain's private key to sign the email headers or body, and the recipient verifies the signature using the public key in DNS to ensure the content has not been tampered with in transit; DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on both, specifying how recipients should handle emails when SPF or DKIM verification fails (allow, quarantine, or reject), and requires senders to provide a reporting address to receive aggregate reports.
Understanding this division helps clarify: SPF governs "who is sending," DKIM governs "whether the content has been altered," and DMARC governs "what to do after a failure." All three are indispensable, and the process of tightening DMARC policy from p=none to p=reject usually requires months of observing reports—which is precisely one source of operational costs.
IP warm-up and the reputation system: Email service providers and anti-spam organizations (such as Spamhaus) maintain a reputation score for each sending IP, based on factors including complaint rate, spam trap hit rate, and sudden changes in sending volume. New IPs have no historical data; if they send in large volumes directly, they are highly likely to be flagged as suspicious and rate-limited or blocked.
Therefore, "IP warm-up" has become standard practice: starting with a few dozen emails per day, gradually increasing sending volume week by week while monitoring bounce and complaint rates. It usually takes 2 to 6 weeks to establish stable reputation. During this period, sending efficiency is low and manual monitoring is intensive, and once a complaint spike occurs, reputation can quickly drop to zero. Although shared IP pools allow you to borrow others' reputation, they also mean bearing joint risk for the behavior of other senders in the same pool—which explains why commercial services enforce strict admission management for IP pools.
The Pricing Logic of Commercial Email Services
When enterprises are unwilling to maintain this complex system themselves, they turn to commercial email delivery services. These services charge not just a "transmission fee," but cover a range of work including IP pool maintenance, reputation management, bounce handling, compliance auditing, and deliverability optimization.
From this perspective, the pricing of commercial email services actually reflects the difficulty of "ensuring email lands in the inbox." The inbox is a scarce resource, and mailbox providers apply strict screening standards to emails entering the inbox—and the cost of meeting those standards is ultimately borne by senders. This is also why, for the same act of "sending an email," the unit cost differs enormously between marketing emails, transactional emails, and ordinary personal emails—they require completely different levels of trust.
The cost difference between transactional and marketing email: Transactional emails (password resets, order confirmations, billing notifications) are triggered by user actions, with clear recipient expectations and extremely low complaint rates, so their unit cost is lower; marketing emails are proactive pushes that recipients may not expect, with naturally higher complaint and unsubscribe rates, requiring more refined segmentation, frequency control, and unsubscribe compliance support.
This difference is directly reflected in pricing: most commercial email services charge transactional email by volume, while marketing email requires stricter list quality review and may even be billed by "valid deliveries" rather than "sends." In other words, the price reflects not bandwidth, but the risk premium that sender behavior imposes on the inbox ecosystem.
Marginal Costs and Compliance Burdens of Sending at Scale
For organizations with high sending volumes, costs also manifest in the marginal investment brought by scale. The larger the sending volume, the higher the probability of complaints and being flagged as spam, and the harder it is to maintain reputation. On the compliance side, regulatory requirements for commercial email in various countries continue to become more detailed, and unsubscribe mechanisms, sender identity disclosure, and data retention all require systematic support.
The Hacker News discussion, though brief, raised a thought-provoking angle: when we take email for granted as a free tool, we often overlook the social coordination costs required to keep this system running. The "expensiveness" of the email system is, to a large extent, the price paid to maintain its credibility.
Compliance requirements in major jurisdictions: The U.S. CAN-SPAM Act requires commercial emails to provide a clear unsubscribe link, process requests within 10 business days, and include a physical address; the EU GDPR and ePrivacy Directive require marketing emails to obtain prior consent (opt-in) and safeguard data subjects' rights of access and erasure; China's Measures for the Administration of Internet Email Services require commercial emails to be marked with "advertisement" or "AD" labels and include a rejection method.
Compliance is not a one-time configuration: unsubscribe requests need to be synchronized in real time to all sending systems, consent records need to be auditable and retained, and cross-border sending also involves handling data export issues. The larger the sending volume, the higher the automation and audit costs of these processes, and penalties for violations are often calculated based on email volume or revenue proportion, amplifying the risk exposure of sending at scale.
Conclusion: What's Free Is the Interface; What's Expensive Is Trust
Back to the original question—why is sending an email so expensive? The answer is not about how much electricity it takes to transmit a data packet, but about the entire infrastructure and coordination mechanisms required for that email to be trusted, received, and read. Email is one of the few protocols on the internet that remains universal across decades; its appearance of low cost is built on high-cost trust maintenance.
Understanding this offers lessons for building any product today that depends on message delivery: delivery is never a technical problem—it is a trust problem.
One-line Summary
Email transmission is nearly free; what's truly expensive is getting the other side to trust you and accept the message.
Paragraph Summary
Starting from a Hacker News discussion about "why sending an email is so expensive," the article breaks down the real composition of email costs. The open design of the SMTP protocol makes transmission itself nearly zero cost, but the flood of spam forced the ecosystem to layer on authentication mechanisms such as SPF, DKIM, and DMARC, requiring senders to maintain DNS records, manage keys, and monitor authentication results. IP reputation must be gradually built through long-term compliant sending, and warming up a new IP is itself a hidden investment. The pricing of commercial email services therefore reflects deliverability optimization and compliance support rather than bandwidth fees; the cost difference between transactional and marketing email also stems from different required trust levels. Sending at scale further amplifies complaint risk and compliance burdens, making marginal costs rise rather than fall. The conclusion: what's free is the interface; what's expensive is trust maintenance.
Related articles
LLM Application Development: A High-Paying Career Guide for Ordinary People
LLM application development offers fresh graduates up to 35K/month, with SP offers reaching 600K. This article explains the core skills, how to break in, and how ordinary people can seize AI opportunities through learning by doing.
Say Goodbye to AI Influencer Faces: A Complete Guide to Creating Visual Assets for AI Comic Dramas from Scratch
Bilibili creator shares a full workflow for zero-basics AI comic drama visual assets: use Doubao Work skills with script-first, visual references, and real-person texture to escape AI influencer faces, then lock character and scene consistency with asset sheet layouts, weapon detail images, scene nine-grids, and cinematic color palettes.
The AI Production Pipeline Behind Great Videos: From Research to Agent Validation
AI video production isn't just a model race. This article breaks down a transferable four-step pipeline: researching professional workflows, organizing a skill checklist, configuring agents, and experimental validation—and explains how general-purpose LLMs like DeepSeek can replace paid tools to run the entire process.