Reference
Email glossary
61 terms from email authentication, deliverability, bounces and GDPR, each with a plain definition and links to the tools and guides that go deeper.
Authentication and DNS
- SPF (Sender Policy Framework)
- SPF is a DNS TXT record that lists which servers may send mail using your domain in the envelope sender (Return-Path). Receivers check the connecting server against that list.
- DKIM (DomainKeys Identified Mail)
- DKIM adds a cryptographic signature to each message's headers. Receivers fetch the public key from DNS and confirm the message came from a server holding the private key and wasn't changed in transit.
- DKIM selector
- A selector is the label that tells receivers which DKIM public key to fetch: the key for selector s1 on example.com lives at s1._domainkey.example.com.
- DMARC
- DMARC is a DNS TXT record at _dmarc.yourdomain that tells receivers what to do with mail that fails SPF and DKIM alignment (none, quarantine or reject) and where to send reports about it.
- DMARC alignment
- Alignment means the domain that passed SPF or DKIM matches the domain in the From header. DMARC only counts a pass as a pass when it aligns.
- DMARC aggregate report
- An aggregate report is an XML file a receiver emails to your rua address, usually daily, summarising every IP that sent mail claiming your domain and whether it passed SPF, DKIM and DMARC.
- BIMI (Brand Indicators for Message Identification)
- BIMI is a DNS TXT record at default._bimi.yourdomain that points to your logo as an SVG, so supporting inboxes can show it next to authenticated mail.
- VMC (Verified Mark Certificate)
- A VMC is a certificate from a certificate authority that ties your BIMI logo to your organisation, usually based on a registered trademark. Its URL goes in the BIMI record's a= tag.
- ARC (Authenticated Received Chain)
- ARC lets an intermediary, such as a mailing list or forwarding service, record the authentication results it saw before it modified a message, so the final receiver can take them into account.
- MTA-STS
- MTA-STS lets a domain tell sending servers to deliver its inbound mail only over TLS with a valid certificate, instead of falling back to plaintext.
- TLS-RPT (SMTP TLS Reporting)
- TLS-RPT is a TXT record at _smtp._tls.yourdomain that asks sending servers to report, daily, the TLS failures they hit when delivering to you.
- Return-Path (envelope sender)
- The Return-Path is the address in the SMTP MAIL FROM command. Bounces go there, and it's the domain SPF is checked against, which is different from the From header people see.
- PTR record (reverse DNS)
- A PTR record maps an IP address back to a hostname. Receivers expect a sending IP to have one, and expect that hostname to resolve back to the same IP.
- MX record
- An MX record tells other mail servers which hosts accept mail for a domain, with a priority number. Lower numbers are tried first.
Deliverability and reputation
- Email deliverability
- Deliverability is whether your mail reaches the inbox, not just whether the receiving server accepted it. Accepted mail can still land in spam.
- Sender reputation
- Sender reputation is the score mailbox providers keep for your sending domain and IPs, based on how recipients react to your mail. It decides inbox or spam more than content does.
- Inbox placement
- Inbox placement is the share of delivered mail that lands in the inbox rather than the spam folder.
- IP and domain warmup
- Warmup is raising sending volume gradually on a new domain or IP so mailbox providers can build a reputation for it before it sends at full volume.
- Dedicated IP
- A dedicated IP sends only your mail, so its reputation depends only on your sending. The opposite is a shared pool.
- Shared IP pool
- A shared pool is a set of IPs that carries mail for many senders. Its reputation is the average of everyone on it, so the provider's policing of abusive senders matters.
- Blocklist (DNSBL, RBL)
- A blocklist is a list of IPs or domains seen sending spam, published over DNS so receivers can check a sender in one lookup. A listing can get your mail rejected outright.
- Greylisting
- Greylisting is a receiver temporarily rejecting mail from a sender it hasn't seen before, with a 4xx reply, on the bet that real mail servers retry and spam tools don't.
- Feedback loop (FBL)
- A feedback loop is a mailbox provider telling the sender when a recipient marks a message as spam, so the sender can stop mailing that person.
- Complaint rate (spam rate)
- Complaint rate is the share of delivered messages that recipients marked as spam. It's the reputation signal mailbox providers watch most closely.
- Bounce rate
- Bounce rate is the share of sent messages that the receiving server rejected. Hard bounces drive it, and a high rate signals a list nobody is maintaining.
- Spam trap
- A spam trap is an address that never signed up for anything and exists only to catch senders who mail lists they didn't collect properly.
- Google Postmaster Tools
- Postmaster Tools is Google's free dashboard showing how Gmail sees mail from your domain: spam rate, authentication results, encryption and delivery errors.
- Bulk sender (Gmail and Yahoo)
- Gmail defines a bulk sender as one that has sent close to 5,000 or more messages in a day to personal Gmail accounts. Bulk senders must meet stricter authentication, unsubscribe and spam-rate rules.
- One-click unsubscribe (List-Unsubscribe)
- One-click unsubscribe is a pair of headers that let a mail client show an unsubscribe button and unsubscribe the recipient with a single POST request, without opening a web page.
Bounces and SMTP replies
- Hard bounce
- A hard bounce is a permanent rejection, such as an address that doesn't exist. The receiving server answers with a 5xx code and retrying won't help.
- Soft bounce
- A soft bounce is a temporary failure, such as a full mailbox or a busy server. The receiver answers with a 4xx code and a later retry may succeed.
- SMTP reply code
- An SMTP reply code is the three-digit number a mail server answers each command with. The first digit says the outcome: 2 success, 4 try again later, 5 permanent failure.
- Enhanced status code
- An enhanced status code is a three-part code like 5.1.1 that follows the basic SMTP reply and says precisely what went wrong: class, subject, detail.
- DSN (Delivery Status Notification)
- A DSN is the machine-readable bounce message a mail server sends back to the envelope sender when it can't deliver a message, or to report delay or success.
- Backscatter
- Backscatter is bounce mail sent to an innocent address because a spammer forged it as the sender. The bounce goes to the forged Return-Path, not to the spammer.
- Suppression list
- A suppression list holds addresses a sender must not mail again: hard bounces, spam complaints and people who unsubscribed or asked to be removed.
Sending and APIs
- Transactional email
- Transactional email is mail triggered by something a user did or something that happened to their account: a password reset, a receipt, a login alert. One recipient, sent because of an event.
- Marketing email (broadcast)
- Marketing email is mail sent to promote something or to tell many users the same thing: newsletters, product announcements, offers. It needs consent and an unsubscribe.
- MTA (Mail Transfer Agent)
- An MTA is the server software that relays email between systems over SMTP: it queues messages, connects to the recipient's MX host and handles retries and bounces.
- SMTP relay
- An SMTP relay accepts mail from your application over SMTP (usually port 587 with STARTTLS and a username and password) and delivers it onward, so code that already speaks SMTP can use a provider without an SDK.
- Email webhook
- An email webhook is an HTTP POST your provider sends to your server when something happens to a message: delivered, bounced, complained, opened, clicked.
- Webhook signature (HMAC)
- A webhook signature is an HMAC of the request body computed with a secret only you and the provider know. Checking it proves the request came from the provider and wasn't altered.
- Idempotency key
- An idempotency key is a unique value you send with a request so that retrying it, after a timeout for example, can't send the same email twice.
- Open tracking
- Open tracking adds a tiny unique image to an HTML email. When the mail client loads it, the sender records an open.
- Click tracking
- Click tracking rewrites the links in an email to go through the sender's redirect, which records the click and forwards the reader to the real URL.
- Email validation
- Email validation checks whether an address is worth sending to before you send: syntax, whether its domain can receive mail and whether it's a disposable address.
- Double opt-in
- Double opt-in means a new subscriber confirms by clicking a link in an email before you add them to a list. It proves they own the address and asked to be on it.
- Dual-sending
- Dual-sending is running two email providers at once during a migration, moving traffic over in steps while both are authenticated for the same domain.
- Inbound email parsing
- Inbound parsing receives mail sent to an address on your domain, parses it and posts it to your app as JSON, so replies and emailed input can be handled in code.
Privacy and GDPR
- GDPR
- The GDPR is the EU regulation (2016/679) on processing personal data. Email addresses, names and message content are personal data, so every email provider you use is covered.
- Data controller
- The controller decides why and how personal data is processed. If you send email to your users, you're the controller for that data.
- Data processor
- A processor handles personal data on the controller's behalf and only on its instructions. An email API processing your recipients' addresses and messages is a processor.
- DPA (Data Processing Agreement)
- A DPA is the contract Article 28 GDPR requires between you and any provider that processes personal data for you. Without one, using the provider breaches the GDPR.
- Sub-processor
- A sub-processor is a company your processor uses to process your data, such as its cloud host or delivery infrastructure. Under the GDPR you must be told about them and able to object.
- SCCs (Standard Contractual Clauses)
- SCCs are contract clauses adopted by the European Commission (Decision 2021/914) that make a transfer of personal data to a country without an adequacy decision lawful under the GDPR.
- Data residency
- Data residency is where personal data is physically stored and processed. For email it covers message content, logs, events and backups, not only where the API runs.
- CLOUD Act
- The US CLOUD Act (2018) lets US authorities require a US provider to hand over data in its possession, custody or control, wherever in the world that data is stored.
- Right to erasure
- Under Article 17 GDPR a person can ask you to delete their personal data, and you must do so without undue delay unless an exception applies. That includes copies at your email provider.
- Log retention
- Log retention is how long a provider keeps message logs and events: who was sent what and what happened to it. It's a debugging tool and a GDPR question at once.
- Lawful basis
- A lawful basis is one of the six reasons in Article 6 GDPR that make processing personal data legal. Every kind of email you send needs one.
- NIS2
- NIS2 is the EU directive (2022/2555) on cybersecurity for essential and important entities. It requires risk management, incident reporting and supply-chain security, which reaches the SaaS vendors those entities use.