Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 81199 - Evolution sends message in the clear when Compose is cancelled and message is re-sent from Compose window
Summary: Evolution sends message in the clear when Compose is cancelled and message is...
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: evolution
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-01-06 18:15 UTC by Need Real Name
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-01-12 20:14:12 UTC

Attachments (Terms of Use)

Description Need Real Name 2003-01-06 18:15:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

Description of problem:
If you are composing a message in Evolution, and click Send, you are (initially)
prompted for a dialog to enter your gpg passphrase. If you click Cancel on this
dialog, you are returned to the Compose window. If you change your outgoing name
or account from the Compose window in the "From:" field, and click Send again,
the message is sent in the clear, and no prompting for a gpg passphrase is offered. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Compose a message in the normal Compose window

2. Make sure you have gpg enabled, and click Send

3. When the gpg passphrase dialog pops up and asks for your passphrase, click
Cancel, which will return you back to the Compose window

4. Change the outgoing address in the "From:" field of the Compose window

5. Click Send again

Actual Results:  The message is sent in the clear, and no prompting for the gpg
passphrase is offered or used. 

Expected Results:  The message should have offered the option of sending with
gpg signing, encrypting, or otherwise. 

Additional info:

Comment 1 Jeremy Katz 2003-01-12 20:14:12 UTC
I'm pretty certain this was a conscious design decision made upstream.  If you
cancel signing, then it disables signing on the message by default.

Note You need to log in before you can comment on or make changes to this bug.