I have the same problem, right pain really. One of the reasons I
switched from Outlook was the beautiful GUI, Gmail shortcuts and
some other features, but the whole experience with offline mail is
making me switch back to Outlook.
For me it appears to happen when my Mac has a network connection
but that connection isn't providing internet access. This happens
regularly on my daily rail commute. I connect to the train's WiFi
network, but as we travel through rural areas access to the
internet drops out.
As well as causing failure of sent messages I've found that most
folder actions fail. e.g. I delete a load of messages in Airmail,
but they don't get deleted on my mail server. (I can still see them
on my phone and if I login to the web app.) Airmail doesn't give
any indication that the deletions (or moves) have failed to
propagate to the server.
Others may have other scenarios in which it occurs.
The scenario where Outlook really shines is, say I have a flight
coming up, I can download all my mail while I have internet
connection at the airport, then whilst I'm on the plane I can
respond to all my mail, and whilst it doesn't send it just sits in
the Outbox. When I get internet connection again upon landing,
Outlook will just email out all the pending mail in Outbox and make
all read status updates in my inbox.
My recent experience with Airmail is that whilst I can download
all my mail prior to my flight just fine, and I can respond to
everything ok, when I land again:
- none of my changes have been made, i.e. read emails still stay
unread - I have to go into Drafts, which now show a "Failed"
status, and open each mail I've sent whilst offline and resend them
I have similar issues, seems to mostly happen when I have no or
a bad internet connection, such as sometimes in my home or at an
airport. I feel this mainly happens with replies, rather than with
"original" mails, so if I redact and send an email to someone they
will mostly go through, but when I reply to an email or thread, my
reply usually ends up in my draft box, as "failed to send" and I
mostly will not be able to send it off anymore, also not when I
reopen the mail and press send again. Only solution then is to
copy-paste the text in a "fresh" new email and send it off, having
my reply falling out of the thread... Attached pic of mail trying
(and failing) to send as I am writing this, so connection is weak
I have still had this issue this month. I have been updating to latest version every time. @Nigel is exactly correct; I think it happens when I am connected to a network but the internet connection is intermittent. So instead of waiting for a better connection, it just crashes and says "failed"
on 07 Apr, 2017 11:24 PM
Still a problem in build 420 (v3.2.4)
This is an absolute deal-breaker for me, I don't understand how such an otherwise great email app can fail so badly at the fundamental task of either sending an email or letting the user know it failed.
I am testing Airmail at the moment as a replacement for Thunderbird. I had sent a bunch of emails lately which hadn't got any response, so I went looking for why.
It turns out MANY OF THE EMAILS WERE NEVER SENT!!! I found them as this thread says, secretly hidden away in the drafts folder with 'Failed' next to them.
If an email app fails to send at the time, it needs to either:
1) automatically send later, as soon as it can; or
2) make it very, VERY clear to the user that they weren't sent, and given them an easy option to trigger that sending later
Airmail seems to have been written on a flawed assumption that the user has a solid internet connection 100% of the time. People like myself who are frequently working while travelling can tell you this isn't the case.
So, sorry Airmail, but you've just lost my trust with this disrespect of delivery 'sanctity'. When I hit 'send' on an email I need to know that it will be sent, if not right away, then as soon as possible, not silently failing (other than a brief and temporary osx notification popup).
Not only are messages NOT being sent when I reconnect to the internet, but when I manually send them they break from the message thread they are a part of and start a new thread, which is really annoying. I completely agree with Bart and Andrew: if this email client only works when I'm connected to the internet, why even use it!?!? Might as well stick with gmail in a browser, because I just never know if these messages are going to be reliably sent or not.
I am on 421. I still got a message that failed to send. In this case, I was connected to a network, but did not have an internet connection. It was while I was in the process of paying for an internet connection on an airplane, so it looks like the system thought I was connected and tried to start sending, even though there was not a connection, and it failed. I am done dealing with this. Honestly, I am so frustrated at this point. This has been an issue with Airmail for many months now.
yes, this is for a gmail account. It did not retry the send, just showed failed and kept in the drafts folder, even after a stable connection was obtained. i got a notification from AM that the message couldn't be sent.
3 times doesn't seem like the right approach. if there is no stable connection, AM should continue checking if a stable connection is established and then send all messages once there is internet. that's how every other off-line email service in the world works.
I didn't try that because I was still in the process of working on other emails. It's hard for me to test this, because it only occurs when I am in the process of connecting to a hotel or airplane wifi for the first time (with connection but no internet access).
Airmail on 08 Apr, 2017 07:03 PM
if you can provide feedback is welcome
I can also provide a version with verbose logs for sending
my idea is that when AM check the internet reachability it obtains a false positive
but the bandwidth is not enough to send the email
the best solution would be to track the error type and do not manage it as a proper send failure
in the bar view under the 3dots button > more > you can send logs
i you can specify a time frame when the event occurred
I have figured out a work-around for this, but it's really annoying. I manually turn off my wifi and work in offline mode in airmail. I then quit airmail, login to a new wifi network, and when I have full connectivity I relaunch airmail and my messages send. Have you figured out any ways to fix this? Again, this is a serious flaw of the program.
Also, when the messages do send after being offline, they all break from their message thread (they become message 1 of a new thread even if they were replies to a previous thread). That is a huge problem, because I have to go searching for previous messages in the same thread.
Please please please try to fix these offline sending issues. This should really be a priority for your software.
I have this issue as well and it's crazy frustrating. Most of the value of a desktop client is to read, write, send emails when offline to have them synch when back online. What's the fix for this? Manually "sending" the emails isn't work.