David T-G wrote:

> % Still not parseable by (say) Outlook and Eudora.  The best way to go is
> % 
> % macro compose S "Fgpg -a --clearsign -u 0xEDEDEFB9"
> 
> Much better is Shane Wegener's pgp_outlook_compat patch so that you don't
> have to muck with macros.

Unfortunately, pgp_outlook_compat relies on pgp_create_traditional,
which only works for us-ascii mail as stated in the manual.  So for us
non-us users, we have to rely on macros do pgp-sign mail to Outlook
users.

Here's what I do:

        # This will select the correct behavior for all
        # non-Outlook-users
        send-hook . "set pgp_autosign; bind compose y send-message"

        # This is a list of Outlook users.  I overload the y key (for
        # send mail) to achieve the wanted behavior
        send-hook "~C [EMAIL PROTECTED]" "unset
        pgp_autosign; macro compose y 'Fgpg --armor --clearsign
        --local-user 0x23314340\ny<send-message>'"# some outlook user

This works almost transparently, but unfortunately it doesn't cache your
passphrase (not a big deal) and you risk data loss if you type in the
wrong passphrase three times.  You also have to keep track of all
Outlook users.  And it breaks the MIME standard.  Oh, well, at least it
works.

Cheers,
Viktor
-- 
Viktor Rosenfeld
WWW: http://www.informatik.hu-berlin.de/~rosenfel/

Attachment: msg20352/pgp00000.pgp
Description: PGP signature

Reply via email to