Generic Listname Identification

As you might suspect, I’m subscribed to a large number of mailing lists (most of which I host myself).

One of the problems with mailing lists is that, if you use a singe email address for all your list subscriptions, there isn’t an easy way to file individual list messages based on the list name.

The other day, however, I found a rather handy procmail recipe that helps with that work…


# Generic Listname identification
# 20030517/1134 SBS     Updated to handle quoted Sender text
# 20040210/2140 SBS     Optimized to eliminate shell/sed in the fallback
#                       portion.

# First, grab stuff based on common "extra" headers inserted by lists,
# including RFC-2369 and RFC-2919 specified headers, compensating for
# text comments which have been encountered on some lists.

# Disable icky delivery notifications (if you like 'em, go ahead and enable
# them here).
COMSAT=no

:0
* 9876543210^0 ^(Sender:[       ]*owner-|X-BeenThere:[  ]*|Delivered-To:[ ]*mailing list )\/[-A-Za-z0-9_+]+
* 9876543210^0 ^(List-Post:[    ]*(

To invoke the recipe, just include it in your .procmailrc file and file the identified messages appropriately... something like this ...


LOGFILE=$HOME/procmail.log
VERBOSE=on
INCLUDERC=/usr/local/share/procmail/listname_id.rc

:0 : * ! LISTNAME ?? ^^^^ mail/$LISTNAME

[tags]mail, procmail, mailing lists[/tags]

Related posts ...
If you're seeing a lot of messages about untrusted TLS connections in your mail log
We all agree that email is crucial to modern life. But what email should you
As part of my migration to the cloud, I terminated the Comcast Business internet service
With my recent migration of servers from my basement to Amazon cloud servers, I had

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.