GPGMail: Message meant to be sent as plain text was encrypted once being queued in Mail outbox
When I had the plug-in (version 2.6b2, build1105b) set to encrypt drafts by default in OS X Mail for El Capitan (version 9.2), I composed a message while offline to a correspondent who doesn't use encryption. When I clicked to send it, Mail placed the message in the outbox but the plug-in did not decrypt it then or when Mail finally sent it after I got back online, resulting in an encrypted message and a confused recipient.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Steve on 16 Feb, 2016 01:10 PM
Hey Rob,
excuse the misunderstanding in the blog reply. We're alive and well.
We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.
All the best,
steve
Steve closed this discussion on 24 Mar, 2016 04:50 PM.
Steve re-opened this discussion on 31 Mar, 2017 10:11 AM
Support Staff 2 Posted by Steve on 31 Mar, 2017 10:11 AM
Hi Rob,
the issue where drafts where unintentionally encrypted twice has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.
Should the problem persist, please re-open this discussion and let us know. For more questions that are not related to this specific problem, you are welcome to create a new discussion any time.
Best, steve
Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.
Steve closed this discussion on 31 Mar, 2017 10:13 AM.
Steve closed this discussion on 31 Mar, 2017 11:18 AM.