>>>> Barry writes: > I suspect that there will be plenty of mailing lists that get fed > messages from programs, e.g. think vcs -commit diff lists. Those programs can > also be buggy, but again I'd prefer that Mailman not compromise on this issue > for their sake.
I predict you will eventually lose on this. That's not an argument for changing, of course. :-) > The point being that messages that flow through Mailman will have that > hash in the message URLs in the Archived-At header and possibly in the > decorated footers. An archiver should certainly provide an interface to look > up a message by pure Message-ID or the hash. The hash is just a scheme to > regularize the message id and is a tiny fraction more user-friendly (because > of its limited alphabet and manageable, known-in-advance length). I would say that's actually quite significant, because the trash that I've observed in message-ids is varied, to be polite. It will be nice to be able to avoid URL-escaping, RFC 2047 soft line breaks, and all the rest. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
