Email not sending on iPhone

Same thing happened to me. After sending, I was unwittingly tapping Undo Send at bottom of screen by accidentally touching or swiping up to exit before mail had a chance to send. Undo Send option is on by default. There is a minimum 10 second delay to mail actually being sent, even after you hear the whoosh. Go to Mail preferences, scroll down to very bottom > Send > Undo Send Delay > Turn Off or choose 10/20/30 Seconds.

onemorefedup wrote:

Does not work. These 1000$ toys are just not working properly and they are trying to make us believe we are the problem. Just fedup

If you swipe up to kill the mail app when you close it, or tap unsend, you ARE the problem. And you can fix the problem you create by turning off Undo Send Delay in Settings/Mail (at the bottom of the page) then you can fix the problem you are causing. As user juliangallowagain posted.

1945R1946 wrote:

Shame on Apple. After every update to correct a problem there's another two or three created and it's never their fault. So sad, time for an android.

Ah, someone else who didn’t bother to read the thread before posting. So sad.

But you should always get the product that best meets your needs. I’m sure that whatever Android device you buy, it will be absolutely perfect, and you will never have any complaints about it.

飞263 wrote:

I'm having the same issue in iphone, but in PC, it is working fine.

You probably have either no password or the wrong password in your outgoing mail settings on your phone. Every email account actually connects to 2 servers, one for incoming and a frequently different server for outgoing. If you change an email password you need to change it in both places.

Usually the easiest way to fix the problem is to delete the email account in Settings/Mail/Accounts, restart your phone, and add the account back in Settings/Mail/Accounts. This will set up both incoming and outgoing.

Let me describe what happen to me. Last Friday, I could use iCloud mail to send or receive emails without any issue in my iPhone. But when I tried to send on Saturday, the email went to outbox and stuck there. An alert popup - outgoing server P210-SMTP.mail.icloud.com.cn cannot be connected. I didn't do any changes on the settings to my iPhone. Looks like the incoming server was working fine while the outgoing server disconnected. Then I logged in the email account on PC web. It was working fine, sending or receiving, no problem. I tried my iPad with the same ID, the same thing happened, outgoing server cannot be connected.

Today, I logged out apple ID in my iPhone and logged in again, restarted it, still cannot connected to outgoing server. Then I went to the SMTP server settings, added a new server "smtp.mail.me.com", Miracle happened, the mail in outbox gone, sending successfully. I turned off the iCloud SMTP server, just leave the new server on, the mail stuck again. Crazy..., I turned off the new added SMTP server and turned on the default iCloud SMTP server again, the mail sending or receiving became normal. Now I can send or receive mails normally as before. No setting changes at all. Just changed the SMTP server and changed back. It sounds like program bug.

I just want to share my experience here to someone that has the same issue.

I am having a similar problem, but my emails are never visible. The recipient is not receiving them as well. It always happens when I close the email app just after sending the message. It is really frustrating, especially considering how much you have to pay for Apple's stuff and yet not be able to send a simple email without any issues.

I've just read your "article". You should really give up on giving advice on technology, as you are obviously lost. Let's just agree that you have never stated that "you should NEVER force quit any app unless it isn’t working". For your sake only.

People like you are the reason others hate the Apple community.

@Lawrence Finch, you're not being helpful. Please advise folks coming to this thread with this problem to simply switch off "Delay Sending" in the Mail Settings. That fixes it.

You suggest, "...either no password or the wrong password in your outgoing mail settings ...Usually the easiest way to fix the problem is to delete the email account ... restart your phone...add the account back". I'm concerned for the poor folks doing this, and simply re-installing the default "Delay Sending" and thus not solving their problem.

Regarding "force quit" (on iPhone I guess you mean swipe-up a running app, whereas on OSX it's an actual command) it seems as if you assume that Apple does a poor job of cleaning up all the bits-and-pieces required to run an app. I actually assume the opposite: Apple does a good job of cleaning up loose ends when an app is closed, cancelled, or quit (forced or otherwise).

You may be drawing on Microsoft experience, where apps often leave processes running after an orderly or disorderly close, sometimes requiring a re-boot or even manual identification, detection, and killing of the process (and a gaping hole for hackers). This is extremely rare in Apple-World (and thus inherently much more secure).

Folks, if your Apple Mails on iPhone are not sending, go to Settings, Mail etc and switch off "Delay Sending". Simple. Done.

juliangallow wrote:

Regarding "force quit" (on iPhone I guess you mean swipe-up a running app, whereas on OSX it's an actual command) it seems as if you assume that Apple does a poor job of cleaning up all the bits-and-pieces required to run an app. I actually assume the opposite: Apple does a good job of cleaning up loose ends when an app is closed, cancelled, or quit (forced or otherwise).

When you swipe up a running app it is EXACTLY the same as choosing Force Quit on a Mac. iOS (or Mac OS) sends a Unix SIGKILL (kill -9) to the app, which terminates it immediately without giving it a chance to save its current state. The purpose, in both cases, is to stop an app that has stopped playing nice with cooperative multitasking. From: https://en.wikipedia.org/wiki/Signal_(IPC)

SIGKILL

"Signal kill"

The SIGKILL signal is sent to a process to cause it to terminate immediately (kill). In contrast to SIGTERM and SIGINT, this signal cannot be caught or ignored, and the receiving process cannot perform any clean-up upon receiving this signal.

This is the ONLY way to force quit an app that isn’t working in iOS (there are several ways in Mac OS). Apple included it to stop runaway processes; they never expected users to use it to stop an already suspended app that isn’t using any system resources.

Fair enough, Lawrence, although I'm not sure that ordinary users would ever need or encounter such a thing, much less suffer consequences ... and anyway, the thread is about "emails not sending". This everyday problem is solved in a few taps to switch off "Delay Sending" in Mail Settings. That's it.

Hey Apple, if you must make this "feature" the default when it previously never existed (which is extremely confusing: stuff that previously just worked - remember those days?) then at least pop-up a warning like "Email will send in 10 seconds - withdraw?" and defo let the countdown run in the background, even if the app is closed, or perhaps put the email in the Outbox until it sends so that we have some visibility of what's going on - and ffs do not reassure us with the "woosh" we hear that confirms an email is sent when it's in fact still counting down ... to infinity if you close the app before the clock is run out!

Arghhhhh, Apple doesn't fix the things we really want and complain about a lot (sensible meeting invite confirms in Calendar to *all* systems, even if they're Microsoft, so that we can work simply and effectively), but they add useless stuff nobody asked for - and then in a user-unfriendly, undo-working-systems that we've used hundreds of times per day for over a decade, and in a hopelessly confusing way.

Listen to your users, Apple!

If you just swipe to close the mail app, and don’t force-close the mail app, the message will be sent after the timeout you have set. As I said, Apple does not expect users to force close any app. There is no benefit to force closing, and contrary to expectations it actually slows down the phone and uses more energy from the battery when you next launch the app you have closed.

Apple added this feature to be competitive; other email providers, such as Gmail, have had it for a couple of years.

The feature is fine, just make its operation user friendly.

If you close the Mail app before the clock has run out, the email disappears forever. That's what everybody here is complaining about.

Just swipe (no force close) and hey presto - the email you carefully crafted has disappeared from everywhere forever (despite the "woosh").

Terrible UX.

juliangallow wrote:

Just swipe (no force close) and hey presto - the email you carefully crafted has disappeared from everywhere forever (despite the "woosh").

it doesn’t on any of my 4 iOS devices. My mail sends after I have closed the mail app by returning to the Home screen, after the 10 second delay I have set. Have you actually tested this? I did, several times.

Hundreds of people are complaining here about exactly that, including myself. It's great that yours works, but for the hundreds here - representing tens of thousands or more who haven't posted - it's a problem for which they found no intuitive "it just works" solution. Hopefully the Settings Mail "Delay Sending"-OFF solutions will work for them, as many here have reported it does.

May I respectfully suggest that if you don't have the problem, or are in fact solving a problem they don't have, that you let the folks who do have the problem occupy the thread so as to find a quick and really easy solution without undue distraction?

Thanks

Same here - it took me two very angry customers to realize that I was locking my phone directly after hearing the whoosh sound and that was causing emails to disappear without a trace. Maddening to say the least.