At a glance#

Email is the oldest digital channel a business still uses every day, and the only one that no single company owns. Any organisation can send from its own domain, and any person can hold an address with any provider. It is where people expect receipts, invoices, statements, account notices and newsletters: the messages they may want to keep, search and forward.

  • What it is: messages between addresses (name@domain) carried over open internet standards.
  • Who runs it: nobody in particular. You own your domain; the recipient's mailbox provider (Gmail, Yahoo, Outlook.com, a company's own server) decides what reaches the inbox.
  • Reach: the Radicati Group counted more than 4.4 billion email users in 2024.1
  • Who may start the conversation: the business may write first, but marketing needs permission in most countries (see the rules below).
  • How it is priced: by volume or by number of contacts, paid to the service that sends for you. The receiving side charges nothing.
  • Best for: records, long content, attachments, newsletters, anything a person files.
  • Avoid for: urgent alerts and one-time codes where seconds matter.
  • As of: October 2026.
Transactional emailMarketing email
What triggers itSomething the person did: an order, a password reset, a billA decision by the business: a campaign or a newsletter
PermissionPart of the service the person asked forConsent in most countries, with narrow customer exceptions
UnsubscribeNot covered by Gmail's one-click ruleOne-click unsubscribe expected by the largest mailbox providers
Where to send it fromIts own stream, so a marketing problem cannot delay itA separate stream, ideally a separate subdomain
The two kinds of business email, as the largest mailbox providers treat them.

How it works#

An email leaves your systems through a sending service, usually an email service provider (ESP), or through your own mail server. It is handed from server to server with the Simple Mail Transfer Protocol (SMTP), the standard every mail server speaks, today defined in RFC 5321.4 Most ESPs let your software send through an API and report back what happened through webhooks: delivered, bounced, clicked, unsubscribed or marked as spam.

The receiving mail server, run by the recipient's mailbox provider, then decides whether to accept the message and where to file it. It first checks that the mail really comes from the domain it claims, using three records you publish in your domain's DNS (the internet's address book):

  • SPF (Sender Policy Framework) lists the servers allowed to send mail for your domain.5
  • DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message, which the receiver checks against a public key you publish.6
  • DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers what to do when a message fails those checks, requires the visible From address to match, and sends you reports.78

Passing these checks proves identity, not good behaviour. The receiver then weighs your reputation: how many recipients mark your mail as spam, how many addresses bounce, and how people engage. Gmail, for example, measures the share of messages users report as spam and asks bulk senders to keep it below 0.1% and never reach 0.3%.11

The path of one email

  1. 01Your system

    Decides to send: a receipt, a reset link, a newsletter

    A request to the sending service

  2. 02Sending service

    Signs the message with DKIM and hands it over by SMTP

    The message, from an address on your domain

  3. 03Receiving mail server

    Checks SPF, DKIM and DMARC, then your reputation

    Accepted, rejected or filed as spam

  4. 04Mailbox

    Inbox, a promotions tab or the spam folder

One common measure is weaker than it looks. An "open" is usually recorded when a tiny invisible image in the message loads. Since 2021 Apple's Mail Privacy Protection blocks such pixels from telling senders when mail is opened, and hides the reader's IP address,14 so open rates are now an estimate rather than a count. Clicks, replies and purchases are firmer signals.

A short history#

Ray Tomlinson, an engineer at BBN, sent the first email between computers on the ARPANET in 1971 and chose the @ sign to separate the user from the machine.2 In August 1982 RFC 821 defined SMTP, written by Jon Postel,3 and the protocol was consolidated in RFC 5321 in October 2008.4

Openness brought spam, and the industry answered with ways to prove who sent a message: DKIM was standardised in September 2011,6 the current SPF in April 2014,5 and DMARC in March 2015.7 In January 2017 RFC 8058 gave senders a standard way to offer one-click unsubscribe from the mail app itself.9

Then the mailbox providers turned good practice into rules. In October 2023 Google announced that from February 2024 anyone sending more than 5,000 messages a day to Gmail addresses must authenticate their mail, offer one-click unsubscribe and keep spam complaints low;10 Yahoo's sender rules ask for the same essentials.12 Microsoft announced the same for Outlook.com from May 2025, for domains sending more than 5,000 emails a day.13 Gmail began a progressive enforcement, including rejecting non-compliant mail, in November 2025.11 In May 2026 the IETF published RFC 9989, which replaces RFC 7489 and moves DMARC onto the Standards Track.8

From ARPANET to authenticated inboxes

  1. First network email on ARPANET

    Ray Tomlinson picks the @ sign

  2. RFC 821 defines SMTP

    The protocol mail servers still speak

  3. DKIM, SPF and DMARC standardised

    Proof that mail comes from the domain it claims

  4. RFC 8058 standardises one-click unsubscribe

    Leaving a list from the mail app itself

  5. Apple announces Mail Privacy Protection

    Open tracking becomes unreliable

  6. Gmail's rules for bulk senders begin

    Authentication, one-click unsubscribe, low complaint rates

  7. Outlook.com rules for high-volume senders

    Domains sending over 5,000 emails a day

  8. RFC 9989 updates DMARC

    Now on the Standards Track

Where it is used#

Email is used in every region and by every kind of organisation, and it is the channel most online services ask for at sign-up. The Radicati Group, a technology market research firm, put the number of email users worldwide at 4,481 million in 2024 (about 4.48 billion, more than half the world's population) and forecasts 4,970 million (about 4.97 billion) by the end of 2028. It estimates that business and consumer emails sent and received exceeded 361 billion a day in 2024, and forecasts about 424 billion a day by 2028.1

Email users worldwide (billions)

4.482024

Business and consumer users

4.972028, forecast

The Radicati Group's forecast

The Radicati Group, Email Statistics Report 2024–2028.

What changes between regions is less whether people have an address than how strictly marketing email is regulated:

  • Americas: the United States lets businesses send commercial email without prior consent as long as they honour opt-outs,17 while Canada requires consent first.20
  • Europe: the EU and the UK require consent for marketing email to individuals, with a narrow exception for a business's own customers.1819
  • Middle East and Africa: South Africa requires consent from anyone who is not already a customer,22 and the UAE's telecoms regulator set an opt-in rule for marketing electronic communications.23
  • Asia-Pacific: Australia requires consent, a clear sender identity and an unsubscribe option in every marketing message.21

Even where chat apps carry most everyday conversation, email remains the place for documents and account notices, which is why most organisations keep it alongside faster channels rather than replacing it.

What businesses use it for#

  • Notifications and records: order confirmations, receipts, invoices, shipping updates, statements, policy documents and contract copies. This is email's core job, because the customer can keep and search them.
  • Marketing: newsletters, product news, offers and event invitations to people who agreed to receive them.
  • Automation: sequences triggered by behaviour, such as a welcome series, a reminder about an unfinished checkout or a renewal notice.
  • Booking: confirmations with a calendar invitation attached, and reminders that reduce no-shows.
  • Support: ticket replies and follow-ups, where the thread itself becomes the case history.
  • Sign-in codes and links: email can carry a one-time code or a sign-in link, but it is slower and less certain than other channels when the person is waiting at a screen.

What it costs#

There is no fee to the recipient's mailbox provider; you pay the service that sends for you, and you pay in effort for reputation. The common models are:

  • Pay as you go per thousand emails, typical of sending infrastructure reached through an API or SMTP relay.
  • Monthly tiers by volume, with a set number of emails included.
  • Price by number of contacts stored, typical of marketing platforms that include a template editor, lists and automation.
  • Add-ons: a dedicated IP address (so your reputation is not shared with other senders), longer log retention, and deliverability tools.

As one official example, Amazon Simple Email Service lists outbound email at US$0.10 per 1,000 emails on its pay-as-you-go basis, and also sells plans with extra features, starting at US$0.16 per 1,000 emails for the first 10 million a month, as of October 2026.16 Check each provider's own rate card for your volume and region.

The hidden costs are often larger: setting up authentication, keeping lists clean, building templates that work on phones, in dark mode and in right-to-left Arabic, and someone to watch bounce and complaint rates.

Rules and regulation#

This section describes the rules in plain words; it is not legal advice. Two layers apply: the law where your recipients live, and the rules of the mailbox providers that decide what reaches the inbox.

The mailbox providers' rules

Google defines a bulk sender as one sending close to 5,000 messages or more to personal Gmail accounts in 24 hours. Bulk senders must pass SPF, DKIM and DMARC (a DMARC policy of "none" is enough), offer one-click unsubscribe on marketing mail using the method in RFC 8058, honour unsubscribes within 48 hours, and keep the spam rate below 0.3%. The one-click rule applies to marketing, not to transactional messages such as password resets.119 Yahoo asks for the same authentication, one-click unsubscribe honoured within two days, and low complaint rates.12 Outlook.com requires SPF, DKIM and DMARC from domains sending more than 5,000 emails a day, and warned that failing mail would be junked or rejected.13 M3AAWG, the industry's anti-abuse working group, goes further in its best practice: explicit consent before mailing an address, and an unsubscribe header in every message.24

What the largest mailbox providers ask of bulk senders

  • SPF and DKIM pass

    For the domain in the From address

  • DMARC published

    A policy of "none" is the minimum

  • One-click unsubscribe

    On marketing mail, honoured within two days

  • Spam rate under 0.3%

    Gmail advises staying under 0.1%

  • Mail to a bought list

    Drives complaints, the fastest way to the spam folder

The law, by region

  • United States: the CAN-SPAM Act does not require prior consent, but every commercial email needs accurate headers, an honest subject line, a valid postal address and a working opt-out. Each violating email can draw a penalty of up to US$53,088.17
  • European Union: the ePrivacy Directive (Article 13) requires prior consent for email marketing to individuals, with an exception for a business's own customers about similar products, provided they can object easily and free of charge.18 The GDPR governs the personal data itself.
  • United Kingdom: the Privacy and Electronic Communications Regulations (PECR) require consent or the "soft opt-in" for existing customers; the regulator, the ICO, says no bought-in list can meet the soft opt-in, and a separate soft opt-in for charities started on 5 February 2026.19
  • Canada: Canada's Anti-Spam Legislation (CASL) requires consent, sender identification and an unsubscribe mechanism, and the sender must be able to prove consent.20
  • Australia: the Spam Act requires consent, accurate sender details and an unsubscribe that is actioned within five working days.21
  • South Africa: under POPIA section 69, a business may approach a non-customer only once to ask for consent, and must identify itself and offer an opt-out in every message.22
  • United Arab Emirates: the TDRA's policy on unsolicited electronic communications sets an opt-in process for marketing messages.23
Starting point for marketing emailException or condition
United StatesSend, then honour every opt-outPostal address and working opt-out in each message
European UnionPrior consentOwn customers, similar products, easy objection
United KingdomConsent or the soft opt-inNo bought list qualifies; charity soft opt-in from February 2026
CanadaConsent, express or impliedThe sender must prove it
AustraliaConsent, express or inferredUnsubscribe actioned within five working days
South AfricaConsent for non-customersOne request for consent only
United Arab EmiratesOpt-inSet by the TDRA's policy

Limits and pitfalls#

  • "Delivered" is not "seen". A message accepted by the receiving server can still land in the spam folder or a promotions tab. See delivery rate is not a result.
  • Open rates are estimates. Privacy features load or block tracking images,14 so judge campaigns on clicks, replies and outcomes.
  • One stream for everything. If newsletters and password resets share a sending address, a spike in marketing complaints can delay account email. Separate them.
  • Old or bought lists. They raise bounces and complaints and, in the UK, cannot meet the soft opt-in at all.19
  • Forwarding and mailing lists can break SPF checks on the way; DKIM signatures usually survive, which is one reason to sign everything.613
  • Slow attention. Email suits records, not alerts that need action within minutes, and it is a weak carrier for one-time codes.
  • Lookalike senders. Anyone can register a domain that resembles yours. A brand logo next to your messages through BIMI (Brand Indicators for Message Identification) requires DMARC at enforcement and, at Gmail, a verified certificate for the logo.15
  • Rendering. The same message looks different across mail apps, in dark mode and in right-to-left scripts; test Arabic templates on real devices.

Strengths and weaknesses#

StrengthsWeaknesses
OwnershipYour domain and your list; no single platform can switch you offMailbox providers still decide inbox or spam
ReachAnyone with an address, on any deviceAttention is slower than on chat apps
ContentLong text, attachments and records people keepRendering varies by app, dark mode and script
CostLow per message at volumeAuthentication and reputation need ongoing work
MeasurementDelivery, bounce, click and complaint eventsOpen rates distorted by privacy features

What comes next#

  • A standard DMARC. RFC 9989, published in May 2026, is the new core DMARC specification on the Standards Track, published together with separate documents for reports; it obsoletes RFC 7489.8
  • Stricter enforcement at Gmail. Google describes its enforcement since November 2025 as gradual and progressive, with an accelerated timetable for new sending domains.11
  • Industry best practice. M3AAWG's sender best common practices were updated in August 2026 and ask for explicit consent before an address is mailed.24
  • Steady growth. The Radicati Group forecasts more than 4.9 billion users and about 424 billion emails a day by 2028.1

When to choose it#

Is email the right channel for this message?

  1. 01Will the person want to keep, file or forward it?
    Yes
    Use email
    No
  2. 02Is it long, or does it carry a document?
    Yes
    Use email
    No
  3. 03Must it be seen within minutes?
    Yes
    Use a faster channel, and send the record by email
    No
  4. 04Has the person agreed to hear from you this way, or asked for this message?
    Yes
    Use email
    No
    Ask for consent first

Choose email when the message is a record, when it is long, or when you need to reach people who have no app of yours and no particular chat app. Pair it with a faster channel when timing matters: a push notification or a message on a chat app for the alert, email for the receipt. The email channel page lists providers, choosing a channel per message covers the trade-offs in depth, and which channel for which need compares email with every other channel. Whatever you choose, record consent per channel and purpose: consent is a data model.

Sources

Every claim worth checking, with somewhere to check it.

  1. Email Statistics Report, 2024-2028: Executive SummaryThe Radicati Group · 2024
  2. Official Biography: Raymond TomlinsonInternet Hall of Fame · accessed 2026-10
  3. RFC 821: Simple Mail Transfer ProtocolIETF / RFC Editor · 1982-08
  4. RFC 5321: Simple Mail Transfer ProtocolIETF / RFC Editor · 2008-10
  5. RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1IETF / RFC Editor · 2014-04
  6. RFC 6376: DomainKeys Identified Mail (DKIM) SignaturesIETF / RFC Editor · 2011-09
  7. RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)IETF Datatracker · 2015-03
  8. RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)IETF Datatracker · 2026-05
  9. RFC 8058: Signaling One-Click Functionality for List Email HeadersIETF / RFC Editor · 2017-01
  10. Gmail introduces new requirements to fight spamGoogle (The Keyword) · 2023-10
  11. Email sender guidelines FAQGmail Help · accessed 2026-10
  12. Sender Best PracticesYahoo Sender Hub · accessed 2026-10
  13. Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume SendersMicrosoft Tech Community · 2025-04
  14. Apple advances its privacy leadership with iOS 15, iPadOS 15, macOS Monterey, and watchOS 8Apple Newsroom · 2021-06
  15. Set up BIMIGoogle Workspace Admin Help · accessed 2026-10
  16. Amazon SES pricingAmazon Web Services · accessed 2026-10
  17. CAN-SPAM Act: A Compliance Guide for BusinessUS Federal Trade Commission · accessed 2026-10
  18. Directive 2002/58/EC on privacy and electronic communications (ePrivacy Directive)EUR-Lex · 2002-07
  19. Electronic mail marketing (Guide to PECR)Information Commissioner's Office (UK) · accessed 2026-10
  20. Frequently Asked Questions about Canada's Anti-Spam LegislationCRTC · accessed 2026-10
  21. Avoid sending spamAustralian Communications and Media Authority · accessed 2026-10
  22. Guidance Note on Direct Marketing in terms of the Protection of Personal Information Act 4 of 2013Information Regulator (South Africa) · accessed 2026-10
  23. Regulatory Policy: Unsolicited Electronic CommunicationsTelecommunications and Digital Government Regulatory Authority (UAE) · accessed 2026-10
  24. M3AAWG Sender Best Common PracticesM3AAWG · 2026-08-27