Connect your sending email
Pick your provider. Each guide walks you through the exact clicks, including where to find the app-password page that every major provider now requires.
.eml files, drag them into Outlook Drafts, and send from your corporate mailbox. See the Outlook export guide →Why an app password?
In 2022 Google retired “less secure apps.” Microsoft, Yahoo, and Apple all followed. You can no longer put your normal login password into a third-party SMTP client and expect it to work, even if you have 2FA turned off. Instead, each provider gives you a long, random-looking application-specific password that's scoped to exactly one app.
SAIDR only ever reads or writes with that app password, and you can revoke it in thirty seconds from your provider's account settings without changing your regular login.
@ in your sending address. If it's gmail.com, use Gmail. If it's your company domain and you log in at outlook.office.com, use Microsoft 365. If you log in at a Google Workspace admin, use the Workspace guide.SMTP vs. OAuth: which should you use?
Most users should start with OAuth at Settings → Integrations — one click, no app passwords, no 2-factor dance. The guides below cover custom SMTP for Proton, Zoho, Workspace on custom domains, and other providers that don't support OAuth in SAIDR yet. Both paths are equally supported; pick whichever matches the mailbox you want to send from.
Troubleshooting quick reference
- “Authentication failed” — you pasted your normal login password instead of the app password. Generate a new app-specific one.
- “Connection refused” — wrong port (use
587with STARTTLS for all guides on this page, not 465 / 25). - Email sent but went to spam — your sending domain likely has no SPF / DKIM / DMARC. See Troubleshooting.