Hello mutt-users...

I recently have set up GPG, and have mutt using it to sign mail... a
few questions:

I have pgp_autosign and pgp_sign_as set, but when I go to send a
message, mutt choses MD5 as the MIC algorithm. If i manually do a sign
as, then select my key, it detects it as SHA1. Is this normal
behaviour, to not have it check what type of key my pgp_sign_as is? I
think a GPG Elgamal+DSA key sent with MD5 is still valid, just
slightly less secure. (Yes, i know there is a set to forge the MIC
algorithm, just making sure this isn't a bug before I turn that on...
if it isn't, the manual.txt should explain you probably want to use
that set too, when you use pgp_sign_as).

Next, i've noticed that mutt trys to use mailcap to view
application/pgp-signature... then it bells and prints No matching
mailcap entry found.  Viewing as text... should it default to handling
it itself, instead of searching mailcap?

Last, I'm sure everyone is quite aware of how stupidly outlook/OE
handle gpg signed mails from mutt... im just curious where it gets the
attachment names from... I sent a message from mutt to my outlook
machine... in mutt's send screen... the attachment names are in the
form:

- I     1 /tmp/mutt-foozle-31258-0     [text/plain, 7bit, us-ascii, 1.4K] 

mutt-hostname-junk... when outlook recieves it, the text and signature
are in two files named:

ATT00166.txt
ATT00169.dat

Are these in the mime mail somewhere, or does outlook just make them
up?

Also, does it's refusal to even display the text/plain attachment have
anything to do with its type being 'quoted'?

Thanks in advance, to anyone who can clear up some of these issues I
have! (Please Cc: me on responses, not on this list anymore)

/jmd

-- 
Jeremy M. Dolan <[EMAIL PROTECTED]>
OpenPGP key = http://turbogeek.org/openpgp-key
OpenPGP fingerprint = 494C 7A6E 19FB 026A 1F52  E0D5 5C5D 6228 DC43 3DEE

PGP signature

Reply via email to