Why "It Sent" and "It Arrived" Are Different Questions Now
2026's tighter authentication enforcement means a configured sender and a deliverable one are no longer the same thing — which is exactly why the email app has a real test-send step, not a cosmetic one.
For a long time, "did the email send" and "did the email arrive" were close enough to the same question that most small businesses never had to think about the difference. That gap has widened, and 2026 is the year it became impossible to ignore: Microsoft's tightened Outlook authentication enforcement, alongside industry-wide pressure on SPF, DKIM, and DMARC compliance, means an improperly authenticated sender doesn't just risk landing in spam anymore — it risks outright rejection.
That's the market reality behind a design decision in the email app that might otherwise look like unnecessary friction: campaigns don't send until your workspace has a real, verified sending path configured, either through Resend or through your own SMTP connection. And critically, there's a dedicated verification step — POST /api/v1/email/settings/verify — that does an actual SMTP dial and test send, rather than just confirming you filled in a form correctly.
That distinction exists because "configured" and "deliverable" genuinely are different states now. An SMTP password with a typo, a hostname that doesn't resolve, an API key that's expired — none of those look wrong at a glance in a settings form. They only show up when something actually tries to send through them, which is exactly what a real test send catches and a form-validation check doesn't.
If you've been treating sender setup as a formality — enter some credentials, assume it works, move on — 2026's enforcement environment is a good reason to stop. Run the verification step before your first real campaign, and treat "it sent" and "it arrived" as genuinely separate questions, because right now, for a growing share of recipients, they are.