|FROM ||Rick Moen
|SUBJECT ||Re: [NYLXS - HANGOUT] Matching this mailing list for procmail rules
|From owner-hangout-outgoing-at-mrbrklyn.com Mon Feb 16 23:33:38 2015
Received: by mrbrklyn.com (Postfix)
id C3B2F16116C; Mon, 16 Feb 2015 23:33:37 -0500 (EST)
Received: by mrbrklyn.com (Postfix, from userid 28)
id B38E9161174; Mon, 16 Feb 2015 23:33:37 -0500 (EST)
Received: from linuxmafia.com (linuxmafia.COM [126.96.36.199])
by mrbrklyn.com (Postfix) with ESMTP id E156A16116C
for ; Mon, 16 Feb 2015 23:33:36 -0500 (EST)
Received: from rick by linuxmafia.com with local (Exim 4.72)
for hangout-at-nylxs.com; Mon, 16 Feb 2015 20:33:36 -0800
Date: Mon, 16 Feb 2015 20:33:36 -0800
From: Rick Moen
Subject: Re: [NYLXS - HANGOUT] Matching this mailing list for procmail rules
Content-Type: text/plain; charset=utf-8
Organization: If you lived here, you'd be $HOME already.
X-Mas: Bah humbug.
User-Agent: Mutt/1.5.20 (2009-06-14)
X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false
Correcting edit errors:
> I noticed that postings to this mailing list kept landing in my personal
> mbox rather than in ~/inboxes/lists, the way mailing lists ought to, on
> my system. 'WTF?', I thought. 'Why aren't my procmail rules catching
> the X-BeenThere or X-Loop or X-Mailing-List/Mailing-List headers?'
> And then I remembered: Right, Ruben's still using procmail, which
> completely fails to implement mailing list headers required by RFCs
> after 2000 because it's been unmaintained proprietary code since about
> I've just appended a new special-case match to catch Hangout, as shown
> below. (Notice that we have to look for owner-hangout-at-brklyn.com, even
'mrbrklyn.com', which of course was correct in the procmail recipe.