Am 12.10.05 18:30 schrieb(en) Jean-Luc Coulon (f5ibh):
Teh message is signed, the wrongly displayed one appear with a grey lock while the other with the green one.
Do you see the gray lock in the list of messages? It indicates that Balsa detected multipart/signed as top-level content type. If you run Balsa from a console, you might see some information indicating what went wrong when trying to verify the signature. Balsa should display the contents even if it is not possible to check the signature, though.
Attached both the messages, saved with mutt.
From the first attached message:
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at coulon.evette MIME-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; oundary="=-STfzKObCKnLFIsfv7tQQ"; boundary="=-esALAT/lY5ezwVHXoVA9"
Hmmm, that doesn't look good! One broken boundary entry, and a second good one (the line break seems to come from Balsa) which doesn't match the boundary actually used. In the other (2nd) message...
Content-Type: multipart/signed; micalg=PGP-SHA1; protocol="application/pgp-signature"; boundary="=-STfzKObCKnLFIsfv7tQQ"
...the header looks good (assuming again that the line break comes from Balsa). Maybe you can have a look at the source of both the good and the bad message and verify this?
However, in the 2nd message is a line reading
X-Balsa-SmtpServer: Défaut
which IMHO breaks the rules as headers MUST be US-ASCII, and this one isn't. Or am I wrong here?
Cheers,
Albrecht.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123 Bonn (Germany)
Phone (+49) 228 6199571 - mailto:albrecht dress arcor de
GnuPG public key: http://www.mynetcologne.de/~nc-dreszal/pubkey.asc
_________________________________________________________________________
Attachment:
pgp5GkGwF9HvJ.pgp
Description: PGP signature