The Deliverable Diary

Microsoft is retiring Basic Authentication for SMTP AUTH Client Submission in Exchange Online. If your printers, scanners, scripts, or legacy applications send email through Microsoft 365 using username and password authentication, they need a new solution before Basic Auth is permanently removed. Here’s everything you need to know about the timeline, impact, and your options […]

You came here for templates. They’re below. But first, the safest default for most people: Subject: Out of office until [return date] Hi, Thanks for your email. I’m out of the office from [start date] and back on [return date]. I’ll reply when I return. For anything urgent before then, please contact [colleague’s name] at […]

You sent the email. The recipient never got it. Now your dashboard says “hard bounce” or “soft bounce” or, if you’re an SMTP2GO user, possibly “rejected.” Three different statuses, three different causes, three different things you should do about them. Here’s the short version, then the long one. Quick Answer Hard bounce: the email failed […]

Verifying your sender domains just got a whole lot easier! Did you know there are two ways to verify your sender domains? You can set up DNS records manually or choose automatic sender domain verification. The automatic option saves time and simplifies DNS updates, making the process quick and hassle-free. Powered by Entri, this trusted […]

If you’ve ever contacted our support team about an email issue, you may have been asked to provide the full headers. While that can sound technical, it’s actually a normal and helpful request! So, what are headers? Are they dangerous to share? And why do we ask to see them instead of just reading the email itself?! […]

We believe in being limitless wherever we can. But every email service worth trusting has a few guardrails in place, and ours exist for a single reason: to protect the deliverability of every sender on our network. This page is the canonical answer to “what are SMTP2GO’s sending limits?” Bookmark it. We will keep it […]