On Fri, Oct 28, 2005 at 06:28:50PM +0200, Javier Fernández-Sanguino Peña wrote: > Package: gnupg > Version: 1.4.2-2 > Priority: wishlist > > There are some MUAs (like mutt) that do not encrypt mails you send with your > own key, which makes them unreadable to you once stored in a folder. Since > this issue can be prevented by the use of the 'encrypt-to' option in GnuPG it > would be nice if the default skeleton file for gnupg documented it a bit > more.
This done upstream for GnuPG 1.4.3. Here's the patch. David
Index: options.skel =================================================================== --- options.skel (revision 3924) +++ options.skel (working copy) @@ -39,6 +39,14 @@ #default-recipient some-user-id #default-recipient-self +# Use --encrypt-to to add the specified key as a recipient to all +# messages. This is useful, for example, when sending mail through a +# mail client that does not automatically encrypt mail to your key. +# In the example, this option allows you to read your local copy of +# encrypted mail that you've sent to others. + +#encrypt-to some-key-id + # By default GnuPG creates version 3 signatures for data files. This # is not strictly OpenPGP compliant but PGP 6 and most versions of PGP # 7 require them. To disable this behavior, you may use this option
