PGP5, mutt, and signed messages

[Matthew Gregan <kinetik@ihug.co.nz>]

Greetings everyone.

After seeing quite a few postings about Mutt and PGP in the past few
days, I decided I'd finally get around to setting it up myself. I've
got it working fine with GnuPG and PGP2, but I have a question about
PGP5... I don't know if this is really specific to Mutt, though.

I sent a test message to myself, and signed it with PGP5. When I
receive the message, Mutt checks the signature and reports that it's
'good'.

   Good signature made 1999-07-08 00:39 GMT by key:
     1024 bits, Key ID C22BCF6F, Created 1999-06-28
      "Matthew Gregan <kinetik@ihug.co.nz>"
   This signature applies to another message

That last line has me a little worried. Is that the way PGP5 is
supposed to work (since the signature is attached to the message using
MIME, rather than being part of it (such as the older method of PGP
signing messages used). That's the only thing I can think of, I just
thought I'd check and see what experiences others have had.

One other thing, I saw references to 'language.txt' and
'language50.txt' (for PGP2 and PGP5, respectively) in the Mutt
docs. However, it appears that the Debian package doesn't come with
these files. Would this be considered a bug, and if so, should I file
a report? Or is there a Debian policy which doesn't include such
things?

Thanks.

-- 
Matthew Gregan                                  kinetik@ihug.co.nz