Afternoon, folks. Although not directly SmartList-related, I'm wondering if anyone can point me in the direction of the RFCs detailing the List-* headers that are recommended for mailing lists; adding them to rc.submit.20 and .bin/digest should be trivial, assuming I can figure out what the "standard" proposal is. Charlie
Charlie Summers <charlie@lofcom.com> writes:
Although not directly SmartList-related, I'm wondering if anyone can point me in the direction of the RFCs detailing the List-* headers that are recommended for mailing lists; adding them to rc.submit.20 and .bin/digest should be trivial, assuming I can figure out what the "standard" proposal is.
That would be rfc2369. Note that SmartList 3.15 supports the List-Post:, List-Help, List-Subscribe:, and List-Unsubscribe: header fields by default. Philip Guenther
Although not directly SmartList-related, I'm wondering if anyone can
From: "Charlie Summers" <charlie@lofcom.com> point
me in the direction of the RFCs detailing the List-* headers that are recommended for mailing lists; adding them to rc.submit.20 and .bin/digest should be trivial, assuming I can figure out what the "standard" proposal is.
Maybe a good starting point for your search would be RFC 2076: "Common Internet Message Headers". http://www.nexor.com/index-rfc.htm provides an excellent RFC search facility. Jelmer ----------------------------------------------------------- Drs. Jelmer Jellema - Spin in het Web www.spininhetweb.com Spin in het Web geeft internet inhoud ------------------------------------------------------------- Spin in het Web is de producent van: www.visinhetnet.nl: Niet Het Laatste Nieuws www.irritantman.nl: Irritant Man! - Reden tot Klagen
On Mon, Nov 13, 2000 at 02:39:16PM -0500, Charlie Summers wrote:
Although not directly SmartList-related, I'm wondering if anyone can point me in the direction of the RFCs detailing the List-* headers that are recommended for mailing lists; adding them to rc.submit.20 and .bin/digest should be trivial, assuming I can figure out what the "standard" proposal is.
These lines are included by default with the latest SmartList release. The only reason for this header lines could be to provide a standard way of using a mailing list. I think it's a futile effort. I don't know any mail reader making this header lines usable and most people don't even know what's a message header. Werner
On Tue, Nov 14, 2000 at 12:43:17AM +0100, Werner Reisberger wrote:
On Mon, Nov 13, 2000 at 02:39:16PM -0500, Charlie Summers wrote:
Although not directly SmartList-related, I'm wondering if anyone can point me in the direction of the RFCs detailing the List-* headers that are recommended for mailing lists; adding them to rc.submit.20 and .bin/digest should be trivial, assuming I can figure out what the "standard" proposal is.
RFC 2369 and <draft-chandhok-listid-04.txt>, see: http://www.nisto.com/listspec/ http://www.within.com/%7Echandhok/ietf/listid.shtml http://www.tidbits.com/tb-issues/TidBITS-472.html#lnk2
These lines are included by default with the latest SmartList release.
Excellent! (same goes for the latest versions of mailman, ezmlm, sympa, and others, I think) I made a trivial patch to an (old) version of smartlist to add these headers, in the section of rc.submit starting with "Main header munger for submissions passing through this list", adding lines like this: -I"List-Id: <$list.example.org>" \ -I"List-Help: <http://www.example.org/Mail/>" \ -I"List-Unsubscribe: <mailto:$listreq?subject=unsubscribe>" \ (those are the most useful of the bunch IMO; and of course you need to change example.org etc to your site)
The only reason for this header lines could be to provide a standard way of using a mailing list. I think it's a futile effort.
I disagree, I think they're an extremely good idea and will (eventually) solve many of the problems experienced by users and mailing list administrators. All mailing list maintainers should make sure their lists have these headers on outgoing messages, and maintainers of mailing list software like smartlist should have the software configured to include these headers on outgoing messages by default. More propaganda: http://www.nisto.com/listspec/letter-listmom.txt http://www.nisto.com/listspec/letter-serverdev.txt
I don't know any mail reader making this header lines usable
Pine 4.20+ [1], Eudora (announced [2], anyway; so far it just makes them clickable which is better than nothing), Exmh, others [2]. [1] http://www.washington.edu/pine/changes/4.10-to-4.20.html [2] http://www.nisto.com/listspec/#APPLICATION-SUPPORT The more mailing lists that use them, the more incentive there is for user agents to implement support for them.
and most people don't even know what's a message header.
That's true, but they shouldn't need to. -- Gerald Oskoboiny <gerald@impressive.net> http://impressive.net/people/gerald/
Werner Reisberger <werner@pure.ch> writes: ...
The only reason for this header lines could be to provide a standard way of using a mailing list. I think it's a futile effort. I don't know any mail reader making this header lines usable and most people don't even know what's a message header.
I hear that exmh provides menu items to subscribe, etc for lists that provide these headers. As for it being futile, I don't think so, but I think it's definitely a _very_ long term project. They were standardized over two years ago, but that's a blink of the eye in mail standards: the first standard for internet mail messages was published as rfc724 in May 1977. It has taken over five years to revise the SMTP standard and rfc822 and they're still waiting for IESG approval. Support for them will probably make it into the major MUAs some time in the next twenty years, so we might as well start supporting them now. Philip Guenther Procmail Maintainer
participants (5)
-
Charlie Summers -
Gerald Oskoboiny -
Jelmer Jellema -
Philip Guenther -
Werner Reisberger