Question 1

Do I need 2048-bit DKIM?

Accepted Answer

NO (1024 is fine)—Bigger keys sound safer, but 1024-bit DKIM is RFC-compliant, accepted by every major mailbox provider, and satisfies every bulk-sender requirement. 2048 buys you DNS headaches, not deliverability.

Question 2

Do I need accessible emails?

Accepted Answer

YES—Of 376,348 emails analyzed in 2026, eight passed every accessibility check. The fixes are small and mechanical—and they serve screen readers, dark mode, bright sunlight, and the agents now reading mail on humans' behalf.

Question 3

Do I need BIMI?

Accepted Answer

NO (nice to have)—BIMI puts your logo next to your emails, which is lovely branding—and does nothing for deliverability. It also quietly requires the thing that does matter: an enforcing DMARC policy.

Question 4

Do I need a custom return path?

Accepted Answer

YES (the default is fine)—Your ESP already sets a working, aligned Return-Path on a subdomain it manages—deliverability-wise you're covered. Customize it when branding or a picky security review demands it.

Question 5

Do I need a custom tracking domain?

Accepted Answer

YES (if tracking is on)—Tracking links default to a domain you share with strangers—and their reputation becomes yours. If you track opens or clicks, the redirect domain should be one you own.

Question 6

Do I need a dedicated IP?

Accepted Answer

IT DEPENDS (most likely no)—If you have to ask, you probably don't. Dedicated IPs pay off for senders with high, steady volume and deliverability expertise—everyone else inherits a cold IP and a warming project.

Question 7

Do I need DKIM?

Accepted Answer

YES—DKIM is your cryptographic signature—proof the message came from you and wasn't altered in transit. Every major provider expects it, and DMARC is hollow without it.

Question 8

Do I need DMARC?

Accepted Answer

YES (at least p=none)—Every serious mailbox provider now expects a DMARC policy on your domain. Publishing p=none costs nothing, breaks nothing, and shows you exactly who is sending as you.

Question 9

Do I need p=reject?

Accepted Answer

IT DEPENDS (earn it first)—Reject is where DMARC actually protects your domain—but publish it before every legitimate sender passes and aligns, and you'll block your own mail. Monitor, fix, then enforce.

Question 10

Do I need to read my DMARC reports?

Accepted Answer

IDEALLY (rua, at minimum)—Publishing DMARC without reading the reports is buying a smoke alarm and never checking the battery. The aggregate reports are where misconfigured senders and spoofers show up first.

Question 11

Do I need to warm up my domain?

Accepted Answer

YES—A brand-new domain has no reputation, and inbox providers distrust strangers who shout. Ramp volume gradually—and re-warm whenever your provider, IP, or volume changes significantly.

Question 12

Do I need double opt-in?

Accepted Answer

IDEALLY—Nothing proves consent like a click in a confirmation email. It's not legally required everywhere, but it keeps bots, typos, and grudges off your list—most lists are better with it.

Question 13

Do I need email verification?

Accepted Answer

IDEALLY (at the edges)—Verify at the boundaries: a check at signup keeps typos and bots out, and a cleaning pass before mailing an old list saves your bounce rate. A pristine double-opt-in list needs neither.

Question 14

Do I need Gmail Postmaster Tools?

Accepted Answer

YES (if you send bulk to Gmail)—It's free, it's first-party, and it's the only way to see your domain reputation the way Gmail sees it. If Gmail matters to your list, sign up before you need it.

Question 15

Do I need idempotency keys?

Accepted Answer

IDEALLY (if your code retries)—Networks fail mid-request and retries are how you cope—but a retried send without an idempotency key is how a customer gets three copies of one receipt. One header makes retries safe.

Question 16

Do I need my own mail server?

Accepted Answer

NO (please, no)—Running Postfix in production means owning IP reputation, blocklists, TLS, key rotation, feedback loops, and 3 a.m. deliverability archaeology—to rebuild a commodity. Keep SMTP, drop the server.

Question 17

Do I need one-click unsubscribe?

Accepted Answer

YES (if you send bulk)—Send 5,000+ emails a day to Gmail or Yahoo and RFC 8058 one-click unsubscribe headers are mandatory, not optional. Below that, they're still the cheapest complaint-rate insurance available.

Question 18

Do I need open tracking?

Accepted Answer

IT DEPENDS (not for transactional)—The pixel lies: privacy proxies fire false opens, image blocking hides real ones, and inbox providers read trackers as a promotional smell. Fine for marketing trends, off for transactional.

Question 19

Do I need a plain-text version?

Accepted Answer

IDEALLY (cheap insurance)—HTML-only mail usually lands fine—but the multipart text version costs nothing and quietly serves watches, screen readers, strict clients, and cautious filters. Cheapest robustness win in email.

Question 20

Do I need a preference center?

Accepted Answer

IDEALLY (topics beat goodbyes)—A lone unsubscribe link is all-or-nothing: one unwanted promo and you lose the reader entirely—or worse, they hit the spam button. Topic-level preferences turn goodbyes into downgrades.

Question 21

Do I need a subdomain for sending?

Accepted Answer

YES—Send from notifications.acme.com, not acme.com. Subdomains isolate reputation damage and tell inbox providers what each mail stream is for—while your root domain stays clean.

Question 22

Do I need to avoid "spam trigger words"?

Accepted Answer

NO (mostly a myth)—No secret list of forbidden words decides your fate. Modern filters weigh reputation, authentication, and engagement—"FREE!!!" in a subject line is a style crime, not a spam sentence.

Question 23

Do I need SPF?

Accepted Answer

YES—SPF is table stakes. It's a single DNS record telling mailbox providers which servers may send for your domain—and every major provider expects to find it.

Question 24

Do I need to buy an email list?

Accepted Answer

NO (never)—Bought lists are consent-free by definition—spam traps, stale addresses, and people who've never heard of you. There is no faster way to torch a domain reputation.

Question 25

Do I need an unsubscribe link?

Accepted Answer

YES (for anything promotional)—Marketing and nurture email must carry a visible way out—law and inbox providers agree. Transactional mail is exempt, but hiding the exit is how you earn spam complaints.

Question 26

Do I need a warmup service?

Accepted Answer

NO—Warmup is real; warmup services aren't. Synthetic opens and scripted replies are detectable, meaningless to inbox providers, and can actively damage the reputation they claim to build.

Do I need…all of it?

YES

IDEALLY

NO

IT DEPENDS