118064 - [RFE]Encrypted mail in stored folders.

Status: NEW

(SeaMonkey :: Passwords & Permissions, enhancement)

Description

[jlarsen]

An option to encrypt mail stored locally should have an option to be encrypted
or obscured like the password manager does.

Comment 1

[Mitchell Stoltz (not reading bugmail)]

Reassigning to Morse, as this is similar to the encrypted Form Manager data
feature. Marking Enhancement. Steve, do you see any need for this feature? Is it
feasible? Please reassign or mark it Wontfix as you feel is appropriate. I'd
recommend Wontfix since we generally don't protect data locally except passwords
and certificate stores. This is related to the debate over password-protected
profiles, and I really don't want to open that can of worms again. I just want a
second opinion before closing this bug.

Comment 2

[Stephen P. Morse]

Marking as future.  Equivalent to wont-fix but with less flames.

Comment 3

[John Unruh]

Reassign

Comment 4

[Heikki Toivonen (remove -bugzilla when emailing directly)]

Reassigning to new module owner.

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 7

[Karsten Düsterloh]

Still valid.