Am Mon, 03 Sep 2001, schrieb Andre Bonhote:
> Hi!
>
> On Mon, Sep 03, 2001 at 12:44:33PM +0200, Volker Moell wrote:
> > Two Words: outlook! :-(
>
> You missed one word: sucks!
>
> > Use Inline Signatures:
> > set pgp_create_traditional=yes
>
> Does not work.
>
> > Note that PGP/MIME will be used automatically for messages which have
> > a character set different from us-ascii, or which consist of more than
> > a single MIME part.
>
> This is what I 've done:
>
> set charset="us-ascii"
> set pgp_create_traditional=yes
>
> Still no clue about it ... Any other Ideas? I mean, I don't have to
> stick on PGP on the windows side ... is there something else which can
> be handled easily? Or are there patches for PGP 6.5.X?
The Problem is not PGP, but Outlook.
I defined two macros in my muttrc, so I can encrypt and sign
messages in a way MS Outlook (and a lot of other Windows Email
Clients) understand:
(Sorry for > 68 characters, but the lines are so long)
macro compose S "Fgpg --clearsig=on\nj^T^Utext/plain; format=text; x-action=sign\n"
macro compose E "Fgpg -a -e -s\nj^T^Utext/plain; format=text; x-action=encrypt\n"
The problem about this solution is that you'll have to know whether the
recipient of your mail uses a PGP/Mime capable MUA (which are only
mutt and Eudora AFAIK) or not.
PGP/Mime has great advantages so I do not understand why so many
MTAs cannot deal with it.
Christoph
--
Christoph Maurer - Paul-Röntgen-Straße 7 - D - 52072 Aachen
mailto:[EMAIL PROTECTED] - http://www.christophmaurer.de
On my Homepage: SuSE 7.0 on an Acer Travelmate 508 T Notebook
