The rules that decide whether your email reaches the inbox are published by the companies that run the inboxes, so those rules are where our research starts. This page explains how EMV Email Desk researches, checks, dates and corrects its guides, and why no company can pay to change what they say.
Who writes our guides
Every article on this site carries the byline “EMV Email Desk editors.” The byline stands for the whole desk. Each guide is researched, written and checked against the same standards, and the desk as a whole is responsible for what it says.
What we cover
We cover the tools people use to send email and the rules that decide whether it arrives:
- Email service providers for newsletters and marketing campaigns
- Transactional email services and sending APIs
- Deliverability: SPF, DKIM, DMARC, BIMI, blocklists and sender reputation
- List hygiene, consent and unsubscribe handling
- Inbox how-tos for Gmail, Yahoo Mail, Outlook and Apple Mail
The sources we rely on
We build each guide from primary sources first and add secondary reporting only when it brings something new. In order of weight, those sources are:
- Mailbox providers’ and email clients’ official documentation. That means Google’s sender guidelines and Gmail help pages, Yahoo’s sender requirements, Microsoft’s Outlook and Microsoft 365 documentation, and Apple’s support pages for Mail and iCloud Mail.
- The rules themselves. For US commercial email, that is the Federal Trade Commission’s “CAN-SPAM Act: A Compliance Guide for Business.” For EU privacy and consent, it is the text of the General Data Protection Regulation (Regulation (EU) 2016/679). When a guide covers other laws, such as Canada’s CASL or the UK’s PECR, we read the official text or regulator guidance for that law.
- Technical standards. These are the published specifications behind SPF, DKIM and DMARC, plus the standards for one-click unsubscribe.
- Vendors’ own pages. Email platforms’ pricing pages, plan terms, help centres and developer docs are used for facts about their own products.
- Established trade reporting. We cite it by name, and only to add context to a primary source, never in place of one.
Forum threads and social posts can point us toward a change. They never confirm one on their own. Anything we can’t trace back to an official source is either labelled unconfirmed or left out.
How we report what companies say
When a vendor says its platform does something, we report that as the vendor’s claim. A mailbox provider’s published requirement gets the same treatment: a requirement, credited to the company that wrote it. We don’t claim to have run test accounts, sent test campaigns or measured inbox placement. Our guides are research-based, and they say so. If a provider’s documentation is vague or missing, the guide says that plainly rather than filling the gap with a guess.
How we handle numbers and dates
Anything that can change gets an “as of” date. Prices, free-plan limits, send caps, penalty amounts and policy thresholds all fall under this rule. A typical line reads: “as of November 2026, the free plan allows 500 contacts.” That way you know how old the figure is, even if you’re reading months later.
We also date the rules themselves. Two examples:
- Google and Yahoo’s requirements for bulk senders took effect in February 2024. Google defines a bulk sender as anyone sending more than 5,000 messages to Gmail accounts in a day. The requirements cover SPF, DKIM, a DMARC policy, one-click unsubscribe and low spam complaint rates.
- Microsoft’s requirements for high-volume senders to Outlook.com, Hotmail.com and Live.com addresses took effect on May 5, 2025. Senders of more than 5,000 messages a day must pass SPF and DKIM and publish a DMARC record of at least p=none.
Where a rule has changed over time, we give the dates of each stage instead of merging them into one. We also note the currency for every price. When two reliable sources give different figures, we show both and explain why they differ.
How we read benchmark reports
Industry benchmarks on open, click, bounce and unsubscribe rates come from the companies and research firms that publish them. We don’t produce these figures ourselves. For every report we cite, we state:
- Who published it, and whether they sell an email product
- The sample size and time period, when the report discloses them
- How each metric is defined
- The report’s limits, such as data drawn only from one platform’s customers
Open rates get extra caution. Apple’s Mail Privacy Protection, introduced with iOS 15 in 2021, preloads images in Apple Mail, and that inflates reported opens. Two reports can show very different “average” open rates simply because they measure different senders in different ways.
How we keep older articles up to date
Email rules and plan pricing change often, so we revisit guides on a schedule and whenever a provider announces a change. When we update an article:
- The original publish date stays. You can always see when a guide first appeared.
- An update date is shown next to it, so you know when the content was last checked.
- Outdated parts are marked. A requirement or plan that no longer applies is either removed or kept as dated history in the past tense (“until 2025, the plan included…”). It is never left looking current.
If a provider discontinues a plan or feature, we change the guide. We don’t leave the old details in place.
How corrections work
If you spot a wrong price, an outdated limit or a factual error, contact us through the site and tell us the page and the details. Our commitments:
- Every correction request is read and checked against the primary source within two business days.
- Confirmed factual errors are fixed within one business day of being confirmed.
- Any correction that changes the substance of a page gets a short note at the end of the article. Examples are a wrong figure, a misattributed claim or a changed conclusion. The note says what was corrected and when.
- Typos and small wording fixes are made without a note.
We don’t quietly rewrite a conclusion and leave readers unaware that it changed.
Independence: no payment, no sponsored articles, no guest posts
EMV Email Desk accepts no payment for coverage, placement or rankings. We don’t publish sponsored articles, advertorials or guest posts. No vendor can buy a review, pay to rank higher in a comparison, or approve what we write before it goes live. Companies can send us corrections of fact about their own products. We check those against their public documentation like any other source.
What we will never recommend
Some advice ends up in the spam folder for good reason, and we won’t give it:
- Buying, renting or scraping email lists. These lists damage sender reputation, drive up complaint rates and break the terms of nearly every reputable provider.
- Ways around anti-spam and privacy law. That includes CAN-SPAM, the GDPR and ePrivacy rules, CASL, PECR and comparable laws.
- Deceptive tactics. That means misleading subject lines, hidden or broken unsubscribe links, sender spoofing, and tricks meant to slip past spam filters instead of earning the inbox.
When a guide covers compliance, it explains what the rules require in plain terms. It is not legal advice. For decisions with legal consequences, get advice specific to your situation.
Checking our work yourself
Every claim in a guide should trace back to a source you can check: a mailbox provider’s documentation, the FTC’s CAN-SPAM guide, the GDPR text or a vendor’s own pricing page. If you can’t find what a figure is based on, or it no longer matches the source, please tell us. That report is the fastest way to get the page fixed.