Your message dated Mon, 28 Aug 2006 21:10:18 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385038: procmail: formail doesn't recognize mails which
begin with "*From"
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: procmail
Version: 3.22-16
Severity: important
When trying to split a mailbox into one file per message like this:
formail -ds sh -c 'cat > msg.$FILENO' < mbox-test
I noticed that formail skips over mails that begin (after the From-line)
with a headerfield that matches "*From: ". If this headerline comes
lateron formail splits just fine, but a mailbox like e.g. the following is
treated like one single mail:
------8<-----8<-----8<-----8<-----8<-----8<-----
From [EMAIL PROTECTED] Mon Jul 10 12:52:11 2006
TFrom: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: foo bar whatever 1
To: [EMAIL PROTECTED]
Date: Mon, 10 Jul 2006 12:51:14 +0200
mailbody
From [EMAIL PROTECTED] Mon Jul 10 13:48:11 2006
TestFrom: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: foo bar whatever 2
To: [EMAIL PROTECTED]
Date: Mon, 10 Jul 2006 13:45:17 +0200
mailbody
From [EMAIL PROTECTED] Mon Jul 10 14:30:11 2006
XFrom: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Subject: foo bar whatever 3
To: [EMAIL PROTECTED]
Date: Mon, 10 Jul 2006 14:29:06 +0200
mailbody
------8<-----8<-----8<-----8<-----8<-----8<-----
The mailserver of my provider happens to add a "KFrom: " headerfield
right at the beginning of the mail which renders formail useless. :-(
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (900, 'unstable'), (400, 'proposed-updates'), (400, 'stable'),
(300, 'testing-proposed-updates'), (300, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages procmail depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
Versions of packages procmail recommends:
ii fetchmail 6.3.4-5 SSL enabled POP3, APOP, IMAP mail
ii sendmail-bin [mail-transport- 8.13.7-2 powerful, efficient, and scalable
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 28 Aug 2006, Andy Spiegl wrote:
> Package: procmail
> Version: 3.22-16
> Severity: important
>
> When trying to split a mailbox into one file per message like this:
> formail -ds sh -c 'cat > msg.$FILENO' < mbox-test
>
> I noticed that formail skips over mails that begin (after the From-line)
> with a headerfield that matches "*From: ". If this headerline comes
> lateron formail splits just fine, but a mailbox like e.g. the following is
> treated like one single mail:
>
> [...]
>
> The mailserver of my provider happens to add a "KFrom: " headerfield
> right at the beginning of the mail which renders formail useless. :-(
Well, formail was never designed to do the kind of miracles you expect
from it, so this is not really a bug. The algorithm to split messages
expects *known* header fields (which KFrom: is not). See src/header.h
in the source code to see what I mean.
Try preprocessing the mailbox before giving it to formail, for example,
try filtering via:
sed -e 's/^KFrom: /X-From: /'
or something alike. You might want to contact your provider as well.
People should not use non-standard header fields so happily, that's
why the X-foo convention exists.
--- End Message ---
