Problem with blfs bugzilla headers

Gerard Beekmans gerard at
Sun Aug 4 18:44:35 PDT 2002


Jesse, after you made the Bugzilla upgrade, something went fubar with BLFS' 
Bugzilla email reports that are sent out.

Here's an example of headers that come from blfs-bugs:

From: blfs-bugs at
To: blfs-book at
Subject: [Bug 98] Add fam-2.6.9 to book 
Date: Sun,  4 Aug 2002 12:59:16 -0700 (PDT)
Delivered-To: maillist at
Delivered-To: blfs-book at
X-Bugzilla-Reason: QAContact 
http: // 
X-listar-version: Listar v0.129a
X-original-sender: blfs-bugs at
Precedence: bulk
Reply-To: blfs-book at
X-list: blfs-book
X-Spam-Status: No, hits=0.6 required=5.0 tests=NO_REAL_NAME version=2.1

Here's a properly constructed email to lfs-book:

From: bugzilla at
To: lfs-book at
Subject: [Bug 58] linux-2.4.19
Date: Sun,  4 Aug 2002 12:56:17 -0700 (PDT)
Delivered-To: maillist at
Delivered-To: lfs-book at
X-Bugzilla-Reason: QAContact
X-listar-version: Listar v0.129a
X-original-sender: bugzilla at
Precedence: bulk
Reply-To: lfs-book at
X-list: lfs-book
X-Spam-Status: No, hits=0.6 required=5.0 tests=NO_REAL_NAME version=2.11

See how the link to http://* in an email to blfs-book 
is stuck right smack in the middle of the headers for some reason, while at 
lfs-book it's part of the body. Oficially an blfs-book email's header ends 
when the link starts and the remaining headers (most notable the X-List: 
header) may be ignored. I've noticed the ignore behaviour in Kmail filters. 
Procmail however doesn't ignore the remaining headers, but it should be doing 
so, so procmail is at fault (which has the result of sometimes not noticing 
the problem).

Anyways, I don't know exactly what you changed to blfs-bugs, if anything, so 
can you please look into this and see if it maybe a simple mis-configuration? 

Gerard Beekmans

-*- If Linux doesn't have the solution, you have the wrong problem -*-
Unsubscribe: send email to listar at
and put 'unsubscribe blfs-book' in the subject header of the message

More information about the blfs-book mailing list