On 2000.07.22, in <[EMAIL PROTECTED]>,
"Dennis Robertson" <[EMAIL PROTECTED]> wrote:
> Hello List,
> I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!)
>with PGP
> 6.5.3. I use mutt and gnupg 1.0.1 ;). When he invokes decrypt on my messages all
>he sees
> is: "Content-type: text/plain: charset=us-ascii". That is the end of the process;
>no text
Are you certain that you have mutt properly configured? What do you
for a content-type if you bcc yourself one of these messages? What
about Fcc:?
> is visible. He has no difficulty corresponding with me and others using pgp and
>windows. I
> have read of mutt's alleged shortcomings with mime on the qmail list.
> Is there a way to make mutt/gnupg and windows/eudora/pgp 6.5.3 talk to each other?
I don't know about these allegations. As far as I know, mutt does
PGP/MIME perfectly, but does not do SMIME or application/pgp. Eudora
4.3.2 will issue valid PGP/MIME, which mutt can read, but it can not
read PGP/MIME issued by either mutt or itself. (Yes: Eudora cannot
read its own output.)
There are procmail rules for bending Eudora's usual PGP output into a
format Mutt can work with. Check the web site or list archives.
So, short answer: Eudora can send to Mutt, but Mutt can't send to
Eudora, and it's Eudora's fault.
(Actually there are ways to make Mutt send messages that Eudora can
handle, but these are kludgy and don't involve proper MIME. I think
they involve macros. Again, check the web or archives.)
--
-D. [EMAIL PROTECTED] NSIT University of Chicago
