Troubleshooting: Email won't send or receive
Step-by-step diagnosis when your Email channel stops sending or receiving: credentials, port, TLS, and the usual Gmail and Outlook gotchas.
When to use this guide
Your Email channel shows as connected but messages don't go out, don't come in, or both. Here we split the two sides — sending (SMTP) and receiving (webhook) — because they almost always fail for different reasons.
First: is it sending or receiving?
- Customers don't receive your replies → a sending / SMTP problem.
- Customer emails never appear in the Inbox → a receiving / webhook problem.
Open Channels, go into your Email channel and check its status, then follow the matching section.
Email won't send (SMTP)
- Credentials: go back to Channels → your channel → edit and re-type Username and Password. On Gmail and Outlook a normal password almost never works.
- Port and encryption: use Port
587withTLSencryption (STARTTLS), or Port465withSSL. Mixing 465 with TLS is the most common mistake. - Correct SMTP Host:
smtp.gmail.comfor Gmail,smtp.office365.comfor Outlook/Microsoft 365. - Consistent From Email: the From Email address should belong to the same account that authenticates; many servers refuse to send "on behalf of" another address.
Email won't receive (webhook)
- Confirm the Inbound Webhook URL (
https://omnifox.io/api/webhooks/email) is configured at your inbound provider (SendGrid Inbound Parse or Mailgun). - Check the MX record of the receiving domain or subdomain.
- The address customers write to must exactly match the channel's From Email: Omnifox routes inbound mail by the recipient.
Gmail / Google Workspace
- Turn on 2-step verification and generate an app password; use it as the channel Password (not your normal one).
- Still can't send? Check your account for a "blocked sign-in attempt" alert and approve it.
Outlook / Microsoft 365
- Microsoft is disabling basic auth (SMTP AUTH). If your tenant has it off, plain SMTP sending will fail; ask your admin to enable SMTP AUTH for the mailbox or use an account that allows it.
- Correct host:
smtp.office365.com, port587,TLS.
If none of that works
- Send a test email and open the conversation: if a delivery error message appears, copy the exact text — it usually names the cause (auth, relay, TLS).
- Recreate the channel from scratch in case a credential was saved half-way.
Tips
- Store sending credentials in a manager: rotating app passwords without updating them in Omnifox is the most common silent failure.
- Test sending and receiving separately; fixing one doesn't guarantee the other.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.