Bugs item #665732, was opened at 2003-01-10 15:05 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable)
Status: Closed Resolution: Fixed Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: List-Id should be one line
Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* <kmail\.mail\.kde\.org>$ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. ----------------------------------------------------------------------
Comment By: Bernhard Reiter (ber) Date: 2004-03-12 15:46
Message: Logged In: YES user_id=113859 I have done more research on this bug over time. Procmail does concatenate the header lines, but it leaves the tabular character in. The version I've tried: debian package 3.22-5 So it looks more like a procmail bug to me now. I suggest to to the mailman documentation that the following procmail pattern will work with changing List-Id lines. The brackets contain a space and a tabular. :0: *^List-Id:.*[ ]<kmail\.kde\.org>$ kmail-incoming KMail also can utilise those extended header lines. Mailman 2.1.4 leaves in the long line, but has other problems violating the standards for List-Id. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:05 Message: Logged In: YES user_id=113859 I'm attaching a patch which fixes this bug against 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103