Munged Headers....

[Bruno Wolff III]

On Sun, Sep 27, 2009 at 13:08:00 +0800,
  Ed Greshko <Ed.Greshko at greshko.com> wrote:
> Here is one interesting example of your handiwork....  I love the Cc:

If you go back and look at Frank's message you will see that his email
client incorrectly tried to use RFC 2047 style encoding. Spaces are prohibitted
in quoted words. Mutt appears to try to avoid having partial RFC 2047 escapes
bare and so encodes them to prevent problems. So the actual cc from my message
should be displayed to look like the broken header from Frank's message.
So it will still look odd (because the header was messed up in Frank's
message(, but not as odd as the raw header (unless your email client doesn't
understand RFC 2047 encoding).

In other words my mail client was correctly using the to header from Frank's
messages to use in the cc header in the message I sent.

> From: Bruno Wolff III <bruno at wolff.to>
> To: Frank Cox <theatre at sasktel.net>
> Message-ID: <20090923173611.GB27527 at wolff.to>
> References:
> <OF18F6C2F1.693F43CD-ON8525763A.004995FD-8525763A.004A2679 at MACYS.com>
>         <1253713090.18252.2.camel at politzer.theorphys.helsinki.fi>
>         <20090923100526.69deafe9.theatre at sasktel.net>
> In-Reply-To: <20090923100526.69deafe9.theatre at sasktel.net>
> User-Agent: Mutt/1.5.18 (2008-05-17)
> X-RedHat-Spam-Score: -0.877  (AWL)
> X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12
> X-Scanned-By: MIMEDefang 2.67 on 10.5.110.10
> X-loop: fedora-list at redhat.com
> Cc: =?us-ascii?Q?=3D=3FISO-8859-1=3FQ=3F_Community=5Fassistance=2C_=5Fenco?=
>  =?us-ascii?B?dXJhZ2VtZW50LCA9MDlhbmRfYWR2aWNlX2Zvcl8/PSA9P0lTTy04ODU5LTE/?=
>  =?us-ascii?B?UT91c2luZ19GZWRvcmEu?= ?= <fedora-list at redhat.com>
> Subject: Re: Questionable Status