MESSAGE
DATE | 2015-02-17 |
FROM | Rick Moen
|
SUBJECT | Re: [NYLXS - HANGOUT] Matching this mailing list for procmail rules
|
From owner-hangout-outgoing-at-mrbrklyn.com Tue Feb 17 00:39:54 2015 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix) id 51CD9161168; Tue, 17 Feb 2015 00:39:54 -0500 (EST) Delivered-To: hangout-outgoing-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix, from userid 28) id 4227E16118F; Tue, 17 Feb 2015 00:39:54 -0500 (EST) Delivered-To: hangout-at-nylxs.com Received: from linuxmafia.com (linuxmafia.COM [198.144.195.186]) by mrbrklyn.com (Postfix) with ESMTP id 797DB161168 for ; Tue, 17 Feb 2015 00:39:50 -0500 (EST) Received: from rick by linuxmafia.com with local (Exim 4.72) (envelope-from ) id 1YNass-00048B-Vm for hangout-at-nylxs.com; Mon, 16 Feb 2015 21:39:47 -0800 Date: Mon, 16 Feb 2015 21:39:46 -0800 From: Rick Moen To: hangout-at-nylxs.com Subject: Re: [NYLXS - HANGOUT] Matching this mailing list for procmail rules Message-ID: <20150217053946.GM2527-at-linuxmafia.com> References: <20150217042933.GH2231-at-linuxmafia.com> <54E2C76D.90706-at-panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <54E2C76D.90706-at-panix.com> 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-Connect-IP: X-SA-Exim-Mail-From: rick-at-linuxmafia.com X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false Sender: owner-hangout-at-mrbrklyn.com Precedence: bulk Reply-To: hangout-at-nylxs.com
Quoting Ruben Safir (mrbrklyn-at-panix.com):
> you mean majordomo. Procmail is it's own problem. I think I can add > mail headers if you point me to the RFC
I already did, you know. http://www.professional.org/procmail/listname_id.rc
Some common headers used for traffic control to/from mailing lists are, without particular attention to RFCs:
X-BeenThere: hangout-at-nylxs.com X-Mailing-list: hangout-at-nylxs.com Precedence: list List-Id: NYLXS General Discussion Forum List-Unsubscribe: List-Archive: List-Post: List-Help: List-Subscribe:
In majordomo's case, the List-Unsubscribe and List-Subscribe headers I created (supra) would not exactly work and are perhaps best omitted, because IIRC majordomo parses commands only if they are message body text, and ignores ones in the Subject header.
That pair aside, your mailing list's postings would be more compliant with current expectations for mailing list headers if those were added.
As to the implication of 'I'll add them if you can prove they have RFC imprimatur' (loosely paraphrased), I hope you are aware that IETF deliberately and consciously follows implementations rather than attempting to lead them. This key point, among others, is covered in IETF's essay 'The Tao of IETF', which please see: http://www3.ietf.org/tao.html
In a nutshell, the RFCs codify best practices that have already been worked out as a working consensus in real-world networks. They are not Thou-shalts, but rather 'This is the way the world works, and you do otherwise at your peril.'
I cover that point in my FAQ about why even stubborn listadmins stopped doing Reply-To munging when the consensus was settled in 2001. http://linuxmafia.com/~rick/faq/?page=netiquette#replyto
|
|