Encrypting to self with S/MIME

[Christoph Ludwig]

Hi,

I am using the S/MIME features of mutt 1.5.4i. If I send an encrypted
mail, the copy mutt places in my fcc-folder is encrypted with the
recipients key. Granted, that's safe, but it does not allow me to
refer to my own messages... How can I make mutt save a plaintext copy
of my messages or - even better - a copy encrypted with my own key? (I
took notice of the tradeoff's discussed by Shawn McMahon in
http://www.mail-archive.com/mutt-***@mutt.org/msg25996.html. After
weighing the pros and cons, I decided I want to be able to refer to my
own messages.)

There was a recent thread how to achieve this with PGP, but how can
you do it with S/MIME? Right now I always include myself in the To: line, but
that's a nuisance. (Besides, if I open the messages, I get some
strange error message from OpenSSL's asn.1 routines about some header being
too long. But then it decrypts the message and verifies its
signature. I don't know whether there lies a problem waiting to bite
me...)

Regards

Christoph

[René Clerc]

Post by Christoph Ludwig
I am using the S/MIME features of mutt 1.5.4i. If I send an encrypted
mail, the copy mutt places in my fcc-folder is encrypted with the
recipients key. Granted, that's safe, but it does not allow me to
refer to my own messages... How can I make mutt save a plaintext copy
of my messages or - even better - a copy encrypted with my own key? (I
took notice of the tradeoff's discussed by Shawn McMahon in
weighing the pros and cons, I decided I want to be able to refer to my
own messages.)
There was a recent thread how to achieve this with PGP, but how can
you do it with S/MIME?

Omen Wild has developed a patch which adds this feature to mutt.

A version for mutt-1.5.1 is available at:

http://descolada.dartmouth.edu/mutt/

I remember it applied to 1.5.2 (the version I'm using) without not to
many problems; don't know if it will apply to 1.5.4 though.

HTH,

[Omen Wild]

Post by René Clerc
Omen Wild has developed a patch which adds this feature to mutt.
http://descolada.dartmouth.edu/mutt/
I remember it applied to 1.5.2 (the version I'm using) without not to
many problems; don't know if it will apply to 1.5.4 though.

Unfortunately, it does not. I'll try to update it to the newest mutt
this weekend.

Omen

[Christoph Ludwig]

Thanks for the link to the patch. The patch does not apply to
the current CVS, but it is not hard to do the necessary modifications
manually.

There are still error messages from OpenSSL when I read the saved
message, but I assume that is either a bug / restriction in OpenSSL or
with our certificates. I will investigate further and inform you if I
come to the conclusion that mutt causes the problem.

Regards

Christoph

Date: Fri, 2 May 2003 17:23:14 +0200
Subject: Re: Encrypting to self with S/MIME
- --XvKFcGCOAo53UbWW
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Post by Christoph Ludwig
I am using the S/MIME features of mutt 1.5.4i. If I send an encrypted
mail, the copy mutt places in my fcc-folder is encrypted with the
recipients key. Granted, that's safe, but it does not allow me to
refer to my own messages... How can I make mutt save a plaintext copy
of my messages or - even better - a copy encrypted with my own key? (I
took notice of the tradeoff's discussed by Shawn McMahon in
weighing the pros and cons, I decided I want to be able to refer to my
own messages.)
=20
There was a recent thread how to achieve this with PGP, but how can
you do it with S/MIME?

Omen Wild has developed a patch which adds this feature to mutt.
http://descolada.dartmouth.edu/mutt/
I remember it applied to 1.5.2 (the version I'm using) without not to
many problems; don't know if it will apply to 1.5.4 though.
HTH,
- --=20
It's not the fall that kills you. It's the sudden stop at the end.
- -Douglas Adams
- --XvKFcGCOAo53UbWW
Content-Type: application/pgp-signature
Content-Disposition: inline
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+so1iwja9HprOCscRAsQ8AJ4kxEQVnDhlHjcnlLnXYE3rxTaeyACgqIdY
gx8xsNYML4l1obQNLY0cFJw=
=OxDr
- -----END PGP SIGNATURE-----

[Omen Wild]

Post by Christoph Ludwig
Thanks for the link to the patch. The patch does not apply to
the current CVS, but it is not hard to do the necessary modifications
manually.

For those who are interested I put an updated version of my S/MIME
encrypt to self patch for the current CVS (1.5.4) at:
http://descolada.dartmouth.edu/mutt/patch-1.5.4+-ow.smime-encrypt-self.2

There is also a version there for 1.5.4 proper.

If anyone runs into any problems please let me know.

Omen