The committed fix will fix this bug for systems in which the mailman installation is all on a single server.
For installations with multiple servers accessing Mailman via a shared file system, there can still be manifestations of this bug if there is time skew across the servers.
A complete fix would add another Defaults.py/mm_cfg.py setting such as
# Maximum time skew in seconds between servers in a shared file system environment.
# Set to 0 if the Mailman file system is on a single server.
SERVER_MAX_TIME_SKEW = 0
and changing line 611 of Mailman/MailList.py from
if mtime < self.__timestamp:
to
if mtime + mm_cfg.SERVER_MAX_TIME_SKEW < self.__timestamp:
The committed fix will fix this bug for systems in which the mailman installation is all on a single server.
For installations with multiple servers accessing Mailman via a shared file system, there can still be manifestations of this bug if there is time skew across the servers.
A complete fix would add another Defaults. py/mm_cfg. py setting such as
# Maximum time skew in seconds between servers in a shared file system environment. MAX_TIME_ SKEW = 0
# Set to 0 if the Mailman file system is on a single server.
SERVER_
and changing line 611 of Mailman/MailList.py from
if mtime < self.__timestamp:
to
if mtime + mm_cfg. SERVER_ MAX_TIME_ SKEW < self.__timestamp: