NANOG-futures

[Rich Kulawiec]

On Sun, Mar 16, 2008 at 03:51:04PM +1300, Simon Lyall wrote:
> In that case people filtering by using the "To: " header so the emails
> would not be correctly filtered.

I don't filter on "To:" or "Subject:" for nanog; I use:

	 ^Sender:.*owner-nanog@merit.edu

in procmail.  So let me take this opportunity to request that 
nanog lists be furnished with an appropriate set of headers to
make this issue moot, e.g. RFC 2919 headers such as:

	List-Id: <nanog.merit.edu>
	List-Subscribe: <mailto:nanog-request@merit.edu?body=subscribe>
	List-Unsubscribe: <mailto:nanog-request@merit.edu?body=unsubscribe>
	List-Help: <mailto:nanog-request@merit.edu?body=help>
	List-Post: <mailto:nanog@merit.edu>
	List-Archive: <http://www.nanog.org/email.html>

Of which List-Id is appropriate for filtering.  I believe the list is
still run by majordomo; if so, then these can be placed in the majordomo
config file for the list in the "message-headers" section:

	message_headers     <<  END
	List-Id: <$LIST.merit.edu>
	List-Subscribe: <mailto:$LIST-request@merit.edu?body=subscribe>
	List-Unsubscribe: <mailto:$LIST-request@merit.edu?body=unsubscribe>
	List-Help: <mailto:$LIST-request@merit.edu?body=help>
	List-Post: <mailto:$LIST@merit.edu>
	List-Archive: <http://www.nanog.org/email.html>
	END

The variable LIST is interpolated by majordomo at run time.

This doesn't solve the cross-posting problem (and I'm not sure it's
a problem so much as a policy discussion) but it at least does make
it easy for everyone to identify list messages...so that they know
which ones to argue about. ;-)

---Rsk

_______________________________________________
Nanog-futures mailing list
Nanog-futures@nanog.org
http://mailman.nanog.org/mailman/listinfo/nanog-futures