Mailspring: Sometimes emails are sent with a blank body

Created on 9 May 2018  路  7Comments  路  Source: Foundry376/Mailspring

This happens quite often. Sometimes emails are sent with no body鈥攊t's just blank.

MacOS 10.13.4
Mailspring 1.2.1

Most helpful comment

Hey folks - thanks for filing this. I'm sorry this issue has languished for so long, it proved to be really difficult to narrow down. I'm going to merge this forward into #948 and post an update there. It turns out this happens reliably (hooray! much easier to fix that way...) if you are composing an email which contains a /ton/ of quoted text and you have "undo send" turned off. In this situation, a race condition can occur where the draft is still saving when it's sent. Will post more in #948. This will be fixed in the next release!

All 7 comments

Same happened to me once. I typed the email (I was replying to the email) and sent. The email went blank. Not able to reproduce, but this bug has potential to create a huge problem for the user.

@bengotow this continues to be a hard block for me using the app. any update? thanks!

@bengotow I wanted to bump this issue. This continues to be the overriding problem that I have with Mailspring. Everything else is working well enough, but I can't rely on it to send critical emails.

Thanks!

^ Agreed, critical problem here.

I can confirm I have seen this issue several times in the past few days. Never had a problem until recently. Running OS X 10.3.6 and Mailspring 1.3.0

Bump on this? It's been happening more and more often

Hey folks - thanks for filing this. I'm sorry this issue has languished for so long, it proved to be really difficult to narrow down. I'm going to merge this forward into #948 and post an update there. It turns out this happens reliably (hooray! much easier to fix that way...) if you are composing an email which contains a /ton/ of quoted text and you have "undo send" turned off. In this situation, a race condition can occur where the draft is still saving when it's sent. Will post more in #948. This will be fixed in the next release!

Was this page helpful?
0 / 5 - 0 ratings