[Mailman-Developers] Important Mailman 2.1.9 to 2.1.10 upgrade note.
bob at nleaudio.com
Tue Apr 22 18:44:33 CEST 2008
+1 on the auto-delete. I have a lot of boxes running Mailman that I periodically have to go into to
clean out stuff, and having more junk pile up, while helpful for debugging, isn't great for production.
David Lee wrote:
> On Tue, 22 Apr 2008, Mark Sapiro wrote:
>> Actually, this note really applies to just restarting mailman a Mailman
>> 2.1.9 installation, with or without upgrading to Mailman 2.1.10. But in
>> installations that just 'run' without intervention, this restart may not
>> occur until an upgrade.
>> There is an error in Mailman 2.1.9. In the introduction of the backup
>> and recovery of queue entries, we neglected to remove the backup queue
>> entry for an unparseable message. Thus, if you sometimes receive
>> unparseable messages which are ignored, you may have an accumulation of
>> .bak files in qfiles/in from these messages. When you restart Mailman,
>> these will all be reprocessed, resulting in a flood of error log entries.
>> There is no real harm done, but it would be a good idea when upgrading
>> to stop Mailman and remove any qfiles/in/*.bak files.
> Just a thought, Mark, for consideration...
> If this is deemed "Important" (for anyone upgrading over the next year or
> more), and if this cleaning process is well-defined and capable of
> mechanisation, then might it be worth superseding 2.1.10 with a "2.1.10a"
> (or 2.1.11 or whatever nomeclature is appropriate) that automatically does
> this cleaning?
> (I realise that 2.1.x was intended to be frozen at 2.1.10, but wasn't
> there allowance for significant security fixes and bug fixes?)
> (Only sending this to -developers list.)
More information about the Mailman-Developers