On Mon, Jul 22, 2002 at 01:38:33AM -0400 or thereabouts, Anthony E. Greene wrote: > On 19-Jul-2002/12:28 -0500, Gary <[EMAIL PROTECTED]> wrote: > [snip] > > It is really stupid to use this old outdated method. > > Except that more mailers can handle inline OpenPGP messages. The ones that > don't can be easily worked around using copy/paste. Yes, you are correct about that unfortunately.
> Setting up mutt to send/receive inline OpenPGP messages was not difficult. > The hardest part was finding the info I needed to do it. > I use vim as my mailer, so I added this line to ~/.muttrc: > > set editor="/usr/bin/vim -N -s $HOME/.vimrc-mail" > > My ~/.vimrc-mail conmtains some settings for editing mail, and a few for > easily calling GPG from within vim: Now that is a slick way of doing it. My GPG is totally handled within my .muttrc file.. I like this idea of putting it in the .vimrc file. I can see where this will work nicely. > :set tw=74 > :set fo=tcq > :cmap cs %!gpg --clearsign > :cmap es %!gpg -seat -r > :cmap ee %!gpg -eat -r > :set background=dark > :set syntax=mail > :syntax on > > The first two lines handle wrapping. The next three lines create macros > that call GPG to process the text. To clearsign a message from within vim, > I use: This is a really nice. Thank you Anthony for your input. > To have mutt properly handle incoming inline OpenPGP messages, I added a > filter to the top of my ~/.procmailrc that changes the MIME type on inline > OpenPGP messages so that mutt will know that it needs to call GPG to > handle them: Right, I have this too... -- Best regards, Gary Sorry, but my karma just ran over your dogma. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
