MacOS 10.12.6
1.0.8
--
Bug?
No
Gmail maybe?
Steps to reproduce:
I had a similar situation. I sent later an email, put my laptop in sleep, and opened again after the set time. Mailspring seemed to have some trouble deciding when to send that email. The desired behavior should be sending the email right now if the time has already passed, but it was actually sent way later.
Hey! This is correct鈥攔ight now, features like snooze and send later rely on Mailspring being open because the app doesn't send your email credentials to the cloud. We've got the infrastructure to support running the "send later" from Mailspring's servers, but when it was a feature in Nylas Mail there was a lot of feedback from users that they didn't want their email passwords being stored in the cloud to power those features, so it was removed for Mailspring 1.0. Definitely hoping to bring it back as an opt-in soon so you can choose the behavior you want!
On this particular issue (and before I go filing new issues), can I ask what the expected behavior would be at the moment for people who use Mailspring on multiple computers?
For instance, I have Mailspring connected to the same e-mail account(s) on three computers. If I snooze a message on one of them, and not use that computer when that message was supposed to be resurfaced (but keep using Mailspring in my other computers), that message is not going to pop back, right?
(Asking because I can think of ways through which that could be achieved through the Mailspring ID alone without uploading any e-mail credentials - or any PII for that matter - to the cloud, so don't know if that has been implemented already).
I like the idea of making it an option. For me, send later is almost always used so that something goes out when the computer is asleep (and when I'm asleep), so the feature loses a fair amount of its power if it only sends once I'm back at my computer.
For me send later doesn't work at all, circle loader just keeps on rolling..
What is the latest on this issue -- does Mailspring still have to be open for items to send later? And how does that relate to using different computers at different times -- does the one it was written on have to be open or can any copy of the program be open? I find this functionality potentially quite useful but its implementation is still quite confusing to me.
Seems this is STILL an occurring issue over three years later, with still no option to send later without leaving your computer on all night. This is the second serious problem I've discovered in Mailspring's UX in days. I'd be willing to look past it if Mailspring was free, but the "Send later" feature and others like it is costing me $8 a month, so this is quite frankly appalling.
Most helpful comment
Hey! This is correct鈥攔ight now, features like snooze and send later rely on Mailspring being open because the app doesn't send your email credentials to the cloud. We've got the infrastructure to support running the "send later" from Mailspring's servers, but when it was a feature in Nylas Mail there was a lot of feedback from users that they didn't want their email passwords being stored in the cloud to power those features, so it was removed for Mailspring 1.0. Definitely hoping to bring it back as an opt-in soon so you can choose the behavior you want!