On 1999-02-19 09:20:24 +0100, Boris Wesslowski wrote:
> I recently switched from sendmail to exim and had to turn mutt's
> allow_8bitmime off. Since then my PGP signed messages are
> corrupted. The transport encoding modifies the content, e.g. the
> signature separator:
If I understand you correctly, you imply that exim is altering
multipart/signed content? This would be an outright breach of RFC
1847, 2.1:
The entire contents of the multipart/signed container must be
treated as opaque while it is in transit from an originator to a
recipient. Intermediate message transfer agents must not alter the
content of a multipart/signed in any way, including, but not
limited to, changing the content transfer encoding of the body
part or any of its encapsulated body parts.
Note that the problem has nothing to do with our allow_8bit setting,
since mutt has to ignore that option for multipart/signed messages.
> diff test1 test2
> [...]
> 14c31
> < Content-Length: 870
> ---
> > Content-Length: 868
> 20c37
> < Content-Transfer-Encoding: quoted-printable
> ---
> > Content-Transfer-Encoding: 8bit
> 24c41
> < --=20
> ---
> > --
urgs.
> Is there something mutt can do to avoid this?
Complain to the exim developpers. Loudly. (But only if exim is
really the faulty software, and not fetchmail or some local MDA or
procmail script. Vladimir Sizikov had a similar problem recently,
without any exim being listed on the messages' received headers.
Please double-check this. Vladimir: Have you been able to track down
the problem?)
tlr
--
http://home.pages.de/~roessler/
