![\"Diagram](\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/09\/why-cant-i-send-email-1-1024x768.jpg\" "\\"\\"")
<\/figure><\/div>\n\n\n<\/p>\n\n\n\n
An email will not send problem can describe failures at very different stages of the process.<\/p>\n\n\n\n
If Outlook, Gmail, or a phone’s mail app won’t send a message, start with the client: it can be your connection or account settings. But the same symptom can also come from the server side – an outage, a mail server timeout, a blocked account, or a provider rejecting the connection. You can notice the problem on the client, but it doesn’t automatically mean that it started from there.<\/p>\n\n\n\n
If a campaign or workflow sends mail through an SMTP server or an API, checking starts with the sending service. A blocked IP or an expired certificate can cause rejection, but you won’t be able to spot it in Outlook. Either way, the main problem is usually the same: something wasn’t verified correctly.<\/p>\n\n\n\n
If You’re Using Outlook or Gmail (Desktop\/Web Client)<\/h2>\n\n\n\n
If your Outlook will not send email, go through the settings first. These steps will help you see the problem and spot its reason:<\/p>\n\n\n\n
- \n
- Check the Outbox. If your message was stuck, it means that Outlook already tried to send the email. Check the recipient and attachment, and see if the status bar says “Working Offline” or “Disconnected.”<\/li>\n\n\n\n
- Sign in again if prompted. If you changed your password recently or your account was flagged, it can trigger a sign-in request. In this case, the system usually doesn’t crash on its own: you just need to sign in again.<\/li>\n\n\n\n
- On a manually configured account, check the SMTP host, port, and encryption. Port 587 typically uses STARTTLS; port 465 uses implicit TLS – these get misconfigured more often than people expect.<\/li>\n\n\n\n
- Remove large attachments and retry. Gmail personal accounts cap at 25 MB, and if your attachment is larger, use a Drive link instead – some providers reject the message outright instead of just trimming it.<\/li>\n\n\n\n
- On Gmail Web or Outlook on the web, try a different browser or check for a storage or sending-limit warning. There’s no SMTP setup to check there at all.<\/li>\n\n\n\n
- If security software seems to be involved, check its mail-scanning rules or ask your IT admin rather than disabling protection to test it.<\/li>\n\n\n\n
- If mail isn’t sending in Outlook, it doesn’t mean there’s only one setting to fix – in practice, it’s usually about spotting what Outlook is or isn’t telling you first.<\/li>\n<\/ul>\n\n\n\n
If You’re on Mobile: “Connection to the Server Failed”<\/h2>\n\n\n
\n![\"Connection](\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/09\/why-cant-i-send-email-2-1024x768.jpg\" "\\"\\"")
<\/figure><\/div>\n\n\n<\/p>\n\n\n\n
If your iPhone shows “Cannot get mail, the connection to the server has failed,” work through these checks before changing account settings:<\/p>\n\n\n\n
- \n
- Confirm your phone is actually online. A weak signal or a Wi-Fi network with a login page (hotels, cafes) can trigger this message with nothing wrong on your account – open a browser and check that a page loads first.<\/li>\n\n\n\n
- Check if the mail service itself is down. A quick search usually confirms an outage in minutes, and there’s no point troubleshooting the phone if the server’s the problem. If the service itself is fine and you need to dig deeper, use the error-code table below to find your exact SMTP error.<\/li>\n\n\n\n
- Review the account’s server settings. Go to Settings, find the account, and check the incoming and outgoing server details – a recently changed or expired app-specific password produces this exact error rather than a clear “wrong password” message.<\/li>\n\n\n\n
- Remove and re-add the account. This resolves “connection to server failed” errors faster than hunting for the one broken field, especially after an iOS update.<\/li>\n\n\n\n
- Verify the port and SSL settings manually if the problem started right after an update – Apple’s setup wizard doesn’t always carry over provider-specific settings correctly.<\/li>\n<\/ul>\n\n\n\n
If you’re seeing the “cannot get mail, connection to server failed” error specifically on iPhone, it’s worth checking Apple’s system status page too – some connection failures trace back to Apple’s mail infrastructure, not your provider’s.<\/p>\n\n\n\n
If You’re Sending in Bulk: SMTP and API Errors<\/h2>\n\n\n\n
With bulk or automated sending, the first thing to identify is which layer failed. An API request can be rejected before any email transaction starts – a 401, 403, or 429 from the provider’s API, with no SMTP involved yet. If the API accepts the request but the receiving mail server later refuses the message, that’s when an SMTP error appears, usually in an event log or bounce notification. For SMTP errors specifically:<\/p>\n\n\n\n
- \n
- Read the full response, not just the code. A 550 signals a permanent refusal, but the enhanced code and text explain why – for example, an invalid mailbox, a policy rule, or an access restriction.<\/li>\n\n\n\n
- Note whether it’s 4xx or 5xx. A 4xx response means retry later; a 5xx means don’t resend the same request unchanged – fix the underlying issue first.<\/li>\n\n\n\n
- Check the scale. One failed address often points to that recipient or mailbox. If messages fail across the batch, check your sending account, domain configuration, credentials, and rate limits.<\/li>\n\n\n\n
- For API requests, start with the HTTP status code and response body. An authentication error usually indicates an expired API key or invalid SMTP credentials. SPF and DKIM are separate checks: they verify the sender’s domain and can cause the receiving server to reject or filter the message, but they do not authenticate your API or SMTP connection. For a deeper look at authentication failures specifically, see the full guide to fixing SMTP authentication errors<\/a>.<\/li>\n<\/ul>\n\n\n\n
Once you have the exact SMTP code, the table below shows the likely cause and links to the relevant troubleshooting guide.<\/p>\n\n\n\n
Find Your Exact SMTP Error Code<\/h2>\n\n\n\n
![\"SMTP](\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/09\/why-cant-i-send-email-3-1024x768.jpg\" "\\"\\"")
<\/figure>\n\n\n\n<\/p>\n\n\n\n
Match the code from your bounce message or server response to the likely cause below.<\/p>\n\n\n\n
![\"Problem](\"https:\/\/www.warmy.io\/blog\/wp-content\/uploads\/2026\/09\/why-cant-i-send-email-4-1024x768.jpg\" "\\"\\"")
<\/figure>\n\n\n\n