Re: oddies with enigmail

[Simon Josefsson <jas@extundo.com>]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>>>> "Simon" == Simon Josefsson <jas@extundo.com> writes:
>
>     Simon> Werner Koch <wk@gnupg.org> writes:
>     >> On Wed, 13 Jul 2005 18:29:03 +0000, Uwe Brauer said:
>     >> 
>     >>>  The   question is can I  clear   sign the  message  such that
>     >>> enigmail would not complain?
>     >> 
>     >> Do you say  that pgg inserts the Hash  line?  This is obviously
>     >> wrong - it is best to let gpg  create the cleas signed message.
>     >> This will make sure that the correct header is used.
>
>     Simon> PGG doesn't insert nor remove any  Hash: lines.  The output
>     Simon>  from gpg  is used directly,  except  for QP encoding  when
>     Simon> needed.   Gnus will QP encode  the output from gpg,  so the
>     Simon> receiver  till  have to perform  QP decode  before it looks
>     Simon> like  a valid OpenPGP packet.  This  might  break some MUAs
>     Simon> that expect  the OpenPGP armor   to not be QP escaped,  but
>     Simon> rather, only the signed data.   But such a message wouldn't
>     Simon> conform to MIME specs (the '='  in the CRC24 tag is invalid
>     Simon> QP unless escaped), and some MTAs bounce those messages...
>
>     Simon> That the morale is to use PGP/MIME instead is hopefully obvious.
>
> Well that is what I used
> mml-secure-message-sign-pgpmime

Oh.  Ok.  Still, PGG shouldn't alter any Hash: headers.  Was that
definitely the problem here?  Perhaps something else is somehow
modifying that header.