#463 ✓ duplicate
Noah Kantrowitz

Don't sign or encrypt messages to self

Reported by Noah Kantrowitz | March 1st, 2012 @ 10:57 PM | in 2.0b8 (closed)

Makes iCal reminder emails annoying since they prompt for a passphrase before "sending".

Comments and changes to this ticket

  • Luke Le

    Luke Le March 1st, 2012 @ 10:58 PM

    • State changed from “new” to “open”

    Hi Noah,

    could you please further describe the issue and provide steps to reproduce.
    If signed isn't checked you shouldn't be asked for a passphrase.

  • Luke Le

    Luke Le March 1st, 2012 @ 11:00 PM

    • Importance changed from “” to “”

    Also, which version of GPGMail are you using?
    One of the nightlies? They behave very differently when it comes to
    set the sign & encrypt status for new messages.

  • Noah Kantrowitz

    Noah Kantrowitz March 1st, 2012 @ 11:00 PM

    If my last mail was signed though (and I leave it on for all real messages), it will still have that setting. I can take a screenshot in a few minutes when my passphrase clears from memory.

  • Noah Kantrowitz
  • Noah Kantrowitz

    Noah Kantrowitz March 1st, 2012 @ 11:02 PM

    Actually thats a bad example since that is sending to someone else, moment.

  • Noah Kantrowitz
  • Luke Le

    Luke Le March 1st, 2012 @ 11:06 PM

    Could you please test the latest nightly from nightly.gpgtools.org.
    If you reply to a message, the sign & encrypt status is now set according
    to the original message.
    So if that wasn't signed, by sign is off if you reply.
    Same for encrypted.

    Please let me know if this already solves the problem.

  • Noah Kantrowitz

    Noah Kantrowitz March 1st, 2012 @ 11:13 PM

    This technically fixes the problem because signing is now off for non-replies by default, but that seems like a terrible default to me. I sign every email I send, thats the whole point.

  • Luke Le

    Luke Le March 1st, 2012 @ 11:15 PM

    That was just an example of the new "intelligent" way of setting sign & encrypt status.
    We track the status and used security method for every send message.
    Based on that the next decision is formed.
    So if you chose to sign most of your messages, this will also set sign on for the next message.
    It's based on sender address and recipients.

  • Luke Le

    Luke Le March 1st, 2012 @ 11:17 PM

    • Milestone changed from 2.0 Final to 2.1
    • Importance changed from “” to “”
  • Luke Le

    Luke Le March 1st, 2012 @ 11:20 PM

    Please test the nightly which incorporates the new intelligent way.
    We've already discussed to add preference for what you want and it will be implemented
    if a lot of users request it.
    So if you still feel that the intelligent way doesn't work for you, please reply to this ticket:

    #457 - Add default options for security method, sign and encrypt status

  • Noah Kantrowitz

    Noah Kantrowitz March 1st, 2012 @ 11:46 PM

    I tried sending a signed message and the default setting for the next email was still unsigned. If at any point the default for signing becomes true via the intelligent discovery (is it based on N recent emails or something?) then this issue might return though. I guess I'm unclear on what the logic is to sign or not sign an outgoing message by default. I just don't want to have to check the box on every new email.

  • Luke Le

    Luke Le March 1st, 2012 @ 11:49 PM

    We're still trying to work out the kinks, but it should in fact have signed your next message.
    At the moment it's based on the signed count vs. not signed count, for the recipient.
    If you send the next message to a new recipient, the default is not signed again.
    We'll change that to last sign status.

    Also, we'll be adding a mean to only consider the last N sent messages for a period of time to get better results.

  • Noah Kantrowitz

    Noah Kantrowitz March 1st, 2012 @ 11:57 PM

    Those rules sound much better and would still resolve this bug :-) In the interim, will it cause any problems if I drop back to a30?

  • Luke Le

    Luke Le March 2nd, 2012 @ 12:03 AM

    No, not at all. Feel free to change back.
    We'll be releasing the first stable version of 2.0 soon.

  • steve

    steve January 20th, 2013 @ 12:23 PM

    • Assigned user cleared.
    • Importance cleared.
  • steve

    steve April 23rd, 2013 @ 01:00 PM

    • State changed from “open” to “new”
  • steve

    steve May 31st, 2013 @ 07:34 PM

    • Milestone changed from 2.1 to 2.0b7
    • Importance set to “Low”
  • Luke Le

    Luke Le June 1st, 2013 @ 08:06 PM

    • Milestone changed from 2.0b7 to 2.0b8
  • Luke Le

    Luke Le June 1st, 2013 @ 08:07 PM

    • State changed from “new” to “duplicate”

    DUPLICATE of #552

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Shared Ticket Bins