Re: List/remove cached S/MIME capabilities

2010-02-24 Thread Michael Ströder
Nelson B Bolyard wrote: > On 2010-02-18 03:06 PST, Michael Ströder wrote: > >> I'm using Seamonkey 2.0.3 under Linux. Is there a way to list and tweak the >> cached S/MIME capabilities for certain recipients? > > There is no way to list them, at present. There could be. It just doesn't > exist.

Re: List/remove cached S/MIME capabilities

2010-02-24 Thread Michael Ströder
Nelson B Bolyard wrote: > On 2010-02-18 03:06 PST, Michael Ströder wrote: > >> I'm using Seamonkey 2.0.3 under Linux. Is there a way to list and tweak the >> cached S/MIME capabilities for certain recipients? > > There is no way to list them, at present. There could be. It just doesn't > exist.

Re: List/remove cached S/MIME capabilities

2010-02-20 Thread Nelson B Bolyard
On 2010-02-18 03:06 PST, Michael Ströder wrote: > I'm using Seamonkey 2.0.3 under Linux. Is there a way to list and tweak the > cached S/MIME capabilities for certain recipients? There is no way to list them, at present. There could be. It just doesn't exist. As for "tweaking" them, they get t

Re: List/remove cached S/MIME capabilities

2010-02-19 Thread Jean-Marc Desperrier
Michael Ströder wrote: This is because some influential people consider: > * S/MIME caps are just a part of "mail security protocol" Which is IMO complete non-sense. Yes, and I don't believe this is the major reason why it's not possible in Seamonkey/Thunderbird. The main reason is that

Re: List/remove cached S/MIME capabilities

2010-02-19 Thread Michael Ströder
Konstantin Andreev wrote: > No. No such mail client exists that allow tune/edit recipient's S/MIME > caps. > > This is because some influential people consider: > > * S/MIME caps are just a part of "mail security protocol" > * protocol shouldn't be exposed to end user to prevent security > c

Re: List/remove cached S/MIME capabilities

2010-02-18 Thread Konstantin Andreev
Hello, Michael. No. No such mail client exists that allow tune/edit recipient's S/MIME caps. This is because some influential people consider: * S/MIME caps are just a part of "mail security protocol" * protocol shouldn't be exposed to end user to prevent security compromise. * we should