header modification from this list list manager software

[Neil Williams]

On Sunday 11 Jan 2004 2:49 pm, Richard J. Cattien wrote:
> normally my Content-Type of signed messages is:
> Content-Type: multipart/signed; micalg=pgp-sha1;
>         protocol="application/pgp-signature";
> boundary="XXXXXXXXXXXXXX"

If you choose 'e' in mutt to view the entire text of the email, as you 
received it, you'll find that it is still defined as multipart/signed:

From your post to the list, as I received it:
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="xxxxx"
Content-Disposition: inline

> this leads my mutt to not detecting signed mails as signed and reports
> that the Signature could not be verified (Well, the gpg output is

Is that because the public key could not be retrieved?

Do you get the same with my messages sent via the list? 

-- 

Neil Williams
=============
http://www.codehelp.co.uk/
http://www.dclug.org.uk/
http://www.isbn.org.uk/
http://sourceforge.net/projects/isbnsearch/

http://www.biglumber.com/x/web?qs=0x8801094A28BCB3E3
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
Url : /pipermail/attachments/20040111/8202d891/attachment.bin