[Mailman-Users] Problem with Date:-headers
jonc at nc.rr.com
Tue May 6 19:42:32 CEST 2003
There is also a switch that you can use in Pipermail so that it ignores
the time told to it by the email and instead uses the local time that
the email arrived at the server - actually Mailman replaces the Date:
field in the message with the local time.
You may find this to be a good solution for your problem (not *you*
Richard... and thanks for the patch!).
=== From ~mailman/Mailman/mm_cfg.py ===
# This sets the default `clobber date' policy for the archiver.
# When a message is to be archived either by Pipermail or an
# external archiver, Mailman can modify the Date: header to be
# the date the message was received instead of the Date: in the
# original message. This is useful if you typically receive
# messages with outrageous dates. Set this to 0 to retain the
# date of the original message, or to 1 to always clobber the
# date. Set it to 2 to perform `smart overrides' on the date;
# when the date is outside
# ARCHIVER_ALLOWABLE_SANE_DATE_SKEW (either too early or too late),
# then the received date is substituted instead.
ARCHIVER_CLOBBER_DATE_POLICY = 2
ARCHIVER_ALLOWABLE_SANE_DATE_SKEW = days(15)
On Tue, 2003-05-06 at 13:00, Richard Barrett wrote:
> If you look at the mailman-users user archive at
> http://mail.python.org/pipermail/mailman-users you will see clear evidence
> of a problem in posting date handling by pipermail.
> In the current May 2003 archive, Jon Carnes <jonc at nc.rr.com> response to
> an original post from Stig Petterson <petterso at online.no> appears after
> Stig's post on the date index for the archive not before it. I believe this
> is caused by a bug in the pipermail archiver for which I have recently
> posted a patch for MM 2.1.2, see:
> This may or may not be Stig's original problem but it is definitely a
> problem for lists where people from different time zones are posting and
> can give a false impression in the ordering of events on a list.
More information about the Mailman-Users