[Mailman-Users] 4 things: conjugation with usenet, archivisation by arriving date, statistics, and link to the archives i

Andrzej Kasperowicz andyk at spunge.org
Mon Jan 12 21:53:31 CET 2004

> <http://mail.python.org/pipermail/mailman-developers/2003-November/016121.html>, 
> this was fixed in 2.1.3 (I had been using 2.1.2 at the time).  I 
> haven't seen 2.1.3 myself, and now that 2.1.4 is out, I believed that 
> this would carry the same solution forward.

Thanks for the info.

> >  Well, apparently some archivizers somehow overcome these problems,
> 	I'll believe that when I see it.

Here you go.


1998/02/18	(2.1.1)

	o  Added DATEFIELDS resource.  The resource allows the user to
	   specify the fields (and order) that are checked when
	   MHonArc extracts the date of a message.


By default. mhonarc looks at the Received fields of a message to 
determine a message's date. This tends to be more accurate as it tells 
when the message was actually received (it is better to trust a date/time 
you have control over vs what the sender has control over).
However, you may want to have the date based upon the time the sender 
composed the message. The Date field usually reflects the composition 

I don't know if it is foolproof, but I would wish also pipermail to look 
rather at the received date, than sender composed date (from 2024 or 
It really looks strange when there are so many dates from future stored 
in archive...

> 	I don't believe that you (or anyone else) can answer the 
> questions that I previously raised on this topic.

I'd prefer to have a few hours/days error in recognizing the date, than a 
few years one.

BTW, don't you think that there could be a search engine build in mailman 
archive (how did you find those links you quoted?)?


More information about the Mailman-Users mailing list