Connecting business apps, ERPs, and CRMs
Accounting packages, ERP and CRM systems, helpdesks, document management tools, and other business software often send or read email with a username and password. This stops working when your email provider requires OAuth. OAuth is a more modern login method that uses a secret token generated by your mail provider instead of your actual password. Auth-Email fixes this by sitting between the app and your mailbox: the app keeps using ordinary SMTP, IMAP, or POP with a password, and Auth-Email signs in to your provider with OAuth on its behalf.
Nothing needs installing, and your app doesn’t need updating. You only change its email server settings.
💡 This guide works for any app that lets you enter an email server, username, and password. If you’re setting up a printer or scanner, see our scan to email guide; for code, see script integrations.
What you’ll need
- The address of the mailbox the app should send from (or read), and someone who can sign in to it once to link it
- Access to the app’s email or SMTP settings (often under Settings, Company preferences, System administration, or Email setup)
- An Auth-Email account – the free trial is enough to check that everything works, including sending a test message to yourself
Step 1: Link the mailbox to Auth-Email
- In your Auth-Email dashboard, add the email address the app uses
- Sign in to link it, then choose a password. This is the password your app will use – it is not your mailbox password
Is the mailbox a shared mailbox? See account delegation and shared mailboxes. Does your organization need to approve new apps? Send your administrator our guide for IT administrators.
Step 2: Enter the settings in your app
Apps name these fields differently, but they are always the same settings underneath. Use the selector to see the values for an account provided by Outlook:
| Your app may call it… | Enter |
|---|---|
| SMTP server, outgoing mail server, mail host, smart host | outlook.auth-email.com |
| Port | 465 |
| Encryption, security, connection type | SSL/TLS (sometimes called implicit TLS or SMTPS) |
| Authentication, “server requires authentication” | On – Basic, Normal password, Plain, or Login |
| Username, user ID, login, account | The full email address (e.g., you@outlook.com) |
| Password | The password you chose in step 1 |
| From address, sender, reply address | The same email address as the username |
For apps that read email, the incoming server is the same name, with port 993 for IMAP or 995 for POP, and SSL/TLS.
💡 These are examples. Your Auth-Email dashboard always shows the exact settings for each account, and the server settings page lists every provider.
If your app’s options don’t match
- Only “STARTTLS” or “TLS” on port 587 or 25: see the STARTTLS ports on the server settings page
- An older app that reports a TLS or certificate error: use our legacy client settings, which support older encryption versions
- A choice of “OAuth”, “Modern authentication”, or “Microsoft 365” sign-in: choose the ordinary password option instead (often Basic, SMTP, or Other). Auth-Email does the OAuth part on your behalf
- No username or password fields at all: the app sends without signing in, which Auth-Email doesn’t support – see your options for sending with Microsoft 365
Step 3: Send a test
Most apps have a Send test email button. Send a test to the mailbox’s own address first.
Your account’s connection page in the dashboard shows whether the app has connected, and explains any error it received, so you can tell whether a problem is with the app’s settings or the mailbox.
💡 During the free trial, messages are only delivered to your own address, so that you can check that sending works. Other recipients are skipped, and we email you to let you know. Paid plans send to anyone.
Troubleshooting
- “Authentication failed”: check that the username is the full email address, and that the password is the one you chose in Auth-Email (not your mailbox password)
- “Sender address rejected” or “SendAsDenied”: the app’s From address must be the linked mailbox, or an address that the mailbox is allowed to send as
- Microsoft 365 reports that SMTP AUTH is disabled: your organization has turned off SMTP sign-in. You can either enable it for the mailbox, or switch the account to Microsoft Graph, which needs nothing enabling
- Connection times out: the app’s server may block outgoing connections on the port. Ask your network administrator to allow outgoing connections to the Auth-Email server on the port shown in your dashboard
- Look up any other error with our email error code lookup, or see the troubleshooting guide
Guides for specific apps
- Microsoft Dynamics CRM
- Printers, scanners, and copiers, and step-by-step guides by brand
- Node.js, Python, and PHP
- Outlook, Apple Mail, Thunderbird, and other email apps
💡 Need help?
Tell us which app you’re connecting, and we’ll help you find the right settings straight away. Reach out anytime to support@auth-email.com.