Re: OT: Carriage return inserts in MS Exchange email -- fix?

--gatW/ieO32f1wygP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

on Fri, Jul 22, 2005 at 03:50:44AM +0200, A. Pagaltzis ([email protected]) w=
rote:
> * A. Pagaltzis <[email protected]> [2005-07-22 01:45]:
> > Add ???;format=3Dflowed??? to the Content-Type and watch the CRs
> > disappear from view. At least in mutt. I???m not sure this is the
> > right fix, to be honest; but it???s the only thing which managed to
> > excise those pesky CRs. (See <http://www.joeclark.org/ffaq.html>
> > as well as RFC2646.)
>=20
> Here???s a generic procmail recipe:
>=20
>     :0
>     * ^Content-Transfer-Encoding:.*quoted-printable
>     * ^Content-Type:.*text/plain
>     * ! ^Content-Type:.*format=3Dflowed
>     * B ?? \r
>     {
>         CONTENT_TYPE=3D`formail -x Content-Type`
>=20
>         :0 fhw
>         | formail -i "Content-Type:$CONTENT_TYPE; format=3Dflowed"
>     }
>=20
> This checks quoted-printable encoded text/plain messages that
> don't use format=3Dflowed for CRs in the message body. (procmail
> decodes the transfer encoding before applying regexen, hence `\r`
> instead `=3D0D`.)
>=20
> I'm still unsure whether this is the correct thing to do, but the
> only other solution I found is to sed the CRs out of the body,
> which is way more invasive.

Right.  And would break a number of things.

I've restricted this to dentrix for the moment:

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
# ----------------------------------------------------------------------
# Format=3Dflowed
# Rerwite rule for some mailers....
# Thu Jul 21 19:28:57 PDT 2005
:0 fhw
* 1^0 ^FROM:.*@dentrix.com
{
    :0 fhw
    | $FORMAIL -R "Content-Type:" "X-Original-Content-Type:"

    :0 fhw
    | $FORMAIL -a "Content-Type: text/plain; charset=3D\"iso-8859-1\"; form=
at=3D\"fl
owed\""
}
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D

=2E..which seems to do the trick.


Peace.

--=20
Karsten M. Self <[email protected]>        http://kmself.home.netcom.com/
 What Part of "Gestalt" don't you understand?
    So don't deal with it.  Don't use software that uses it.
    - Jeff Waugh, offering preferred GNOME usability workaround.
       http://zgp.org/pipermail/linux-elitists/2004-January/008588.html


--gatW/ieO32f1wygP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC4FrhefG8443k044RAnW7AKCC8a+O0gZFPAiAYVmwS1XXOd1YZgCgh9um
JYdpyBhy8XSS7yX3N1jakWg=
=zsDW
-----END PGP SIGNATURE-----

--gatW/ieO32f1wygP--