Date: Mon, 29 Mar 2010 08:22:22 -0400 From: Mark Shroyer <subscriber+freebsd@markshroyer.com> To: freebsd-questions@freebsd.org Cc: parv@pair.com Subject: Re: procmail regex help ... sometimes works, sometimes doesn't... Message-ID: <4BB09B7E.5080304@markshroyer.com> In-Reply-To: <20100329072756.GA1322@holstein.holy.cow> References: <471394.79697.qm@web111611.mail.gq1.yahoo.com> <20100329072756.GA1322@holstein.holy.cow>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/29/2010 3:27 AM, parv@pair.com wrote: >> From: "osdeiiftnvpp@gmail.com" <xjyfgzyjm@gmail.com> >> Reply-To: "osdeiiftnvpp@gmail.com" <xjyfgzyjm@gmail.com> >> Message-ID: <533pbxxy2oc> >> To: me <me@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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BB09B7E.5080304>