procmail regex help ... sometimes works, sometimes doesn't...

[Mark Shroyer]

On 3/29/2010 3:27 AM, parv at pair.com wrote:
>> From: "osdeiiftnvpp at gmail.com" <xjyfgzyjm at gmail.com>
>> Reply-To: "osdeiiftnvpp at gmail.com" <xjyfgzyjm at gmail.com>
>> Message-ID: <533pbxxy2oc>
>> To: me <me at me.com>
>> Subject: Fw: \xb8\xf2\xad\xe8\xa5X\xa8\xd3\xbd\xe6~\xb1o\xb4\xa9\xa9f\xaa\xb1\xb5L\xaeM\xa4\xba\xaeg\xb2n\xa7o
>> X-Mailer: inhalation
>> Organization: Microsoft Outlook Express 6.00.2462.0000
>> Mime-Version: 1.0
>> Content-Type: multipart/alternative;
>>         boundary="1-104247307-2712732737=:8213"
>> Status: RO
>> X-Status:
>> X-Keywords:
>> X-UID: 63502
>>
>> --1-104247307-2712732737=:8213
>> Content-Type: text/plain; charset="big5"
>> Content-Transfer-Encoding: quoted-printable
>
> [...]
> 
> Is "Content-Type:" completely missing from the body of your first
> example?  Do you have your examples flipped?  I would have thought
> that first example would have delivered in your inbox & second one
> in your unreadable_messages one.

It's actually a single example of a multipart message; that blank line
followed by the random dashes and numbers delimits a part.  I'm
wondering if Procmail is having trouble matching this because the
offending charset is specified in a multipart content header rather than
in the message headers.

-- 
Mark Shroyer
http://markshroyer.com/contact/