Hi Michael, Am 13.09.2011 um 19:58 schrieb Michael Koppelman:
> D'oh. Chalk this up to user error. In every case I have investigated, the > person complaining they could not read the email did in fact, at one time, > have a key. > > So I'll change my complaint! :) > > Why does Mail "remember" that I clicked the encrypt button? Encryption is a > very deliberate act. I never want that button clicked by default. With the > new stripped-down preferences, I can no longer tell it to never click that > box for me. That is my wish. > GPGMail 2 is leveraging they way S/MIME is implemented in Mail.app and hence just as S/MIME remembers the last selected options. This is sometimes the unwanted result, but unfortunately we still have to work on it to make this smarter. Please follow this ticket http://gpgtools.lighthouseapp.com/projects/65764/tickets/317-minor-nits-with-203-beta#ticket-317-6 to track progress on this issue. > Sorry! and thanks! > > M. > Cheers, Lukas > > On Sep 13, 2011, at 12:49 PM, Lukas Pitschl | Dressy Vagabonds wrote: > >> Hi Michael, >> >> is this happening with one of the GPGMail 2 alphas? >> This should never happen, the buttons should be disabled if any keys are >> missing. >> >> Best, >> >> Lukas >> >> Am 13.09.2011 um 19:47 schrieb Michael Koppelman: >> >>> I apologize if this is a duplicate. >>> >>> This is driving me crazy. It generally goes like this. I encrypt an email >>> to someone that does have a GPG key. My next email is to someone who does >>> not have a GPG key. Mail leaves the encrypt button checked, even though >>> there is no key for that recipient, and then encrypts the message with my >>> own key, thus sending the recipient an unreadable message. >>> >>> The correct behavior is -- if you try to encrypt a message that has >>> recipients without keys, you should at least be warned. My guess is people >>> don't ever want to send an unreadable encrypted message, so you could go so >>> far as to not encrypt the message at all unless every recipient has a key. >>> >>> I have sent a lot of unreadable messages in the last few weeks! >>> >>> Thank you! I appreciate all the hard work that goes into this! >>> >>> M. >>> >>> _______________________________________________ >>> gpgtools-users mailing list >>> gpgtools-users@lists.gpgtools.org >>> FAQ: http://www.gpgtools.org/faq.html >>> Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users >>> Unsubscribe: >>> http://lists.gpgtools.org/mailman/options/gpgtools-users/lu...@dressyvagabonds.com?unsub=Unsubscribe&unsubconfirm=1 >>> >>> This email sent to: lu...@dressyvagabonds.com >> >> _______________________________________________ >> gpgtools-users mailing list >> gpgtools-users@lists.gpgtools.org >> FAQ: http://www.gpgtools.org/faq.html >> Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users >> Unsubscribe: >> http://lists.gpgtools.org/mailman/options/gpgtools-users/lol...@bitstream.net?unsub=Unsubscribe&unsubconfirm=1 >> >> This email sent to: lol...@bitstream.net > > _______________________________________________ > gpgtools-users mailing list > gpgtools-users@lists.gpgtools.org > FAQ: http://www.gpgtools.org/faq.html > Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users > Unsubscribe: > http://lists.gpgtools.org/mailman/options/gpgtools-users/lu...@dressyvagabonds.com?unsub=Unsubscribe&unsubconfirm=1 > > This email sent to: lu...@dressyvagabonds.com _______________________________________________ gpgtools-users mailing list gpgtools-users@lists.gpgtools.org FAQ: http://www.gpgtools.org/faq.html Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users Unsubscribe: http://lists.gpgtools.org/mailman/options/gpgtools-users/arch...@mail-archive.com?unsub=Unsubscribe&unsubconfirm=1 This email sent to: arch...@mail-archive.com
