On Tue, 2 Feb 2016 10:45:22 +0100 Jaromil <[email protected]> wrote: > On Tue, 02 Feb 2016, Florian Zieboll wrote: > > > Another loose thought on this: To spare the mailing list machine(s) > > the additional burden of hashing, wouldn't it be sufficient to add > > a simple counter to mailman and make it inject the count (plus > > perhaps some list and/or machine ID) as a new header to the mail > > before passing it to the archiver? > > I haven't look at any existing solution, but I believe that a good > approach would be to use the actual message-id: in the headers, which > is also an identifier to retrieve email from lurker. But I have no > idea if that header is exported as a variable for mailman's templates.
The mailman wiki document(1) that hellekin had linked in this thread, states regarding the message-ID header | ...that RFC 2822 does not require the header, instead specifying that | the header SHOULD be included. The header also SHOULD be globally | unique but of course, because this is supplied by the client, it may | no actually be unique. Also my "simple counter" approach gets questioned (I should have read it earlier), due to the possibility of a counter reset by the mailing list software. So why not combine it with a time stamp? For the worst case the archiver should be able to handle duplicate sequence numbers, e.g. by appending a suffix and - when queried for such a duplicate - presenting a choice of all applicable messages. Florian (1) http://wiki.list.org/DEV/Stable%20URLs _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
