Fil wrote:
in fact I was living with 2.1.6b (ouch!) up till today, and I had disabled the bounce processors; I just upgraded tonight and am checking logs and stuff...
If it is a real bounce, send it to me, and I'll update the recognizers.
Seem real. I'm sending them to you.
Thanks. I have updated bzr at rev 1098 on the 2.1 branch. This patch to SimpleWarning.py will recognize these delay warnings. === modified file 'Mailman/Bouncers/SimpleWarning.py' --- Mailman/Bouncers/SimpleWarning.py 2007-11-12 05:40:15 +0000 +++ Mailman/Bouncers/SimpleWarning.py 2008-06-15 04:04:44 +0000 @@ -1,4 +1,4 @@ -# Copyright (C) 2001-2007 by the Free Software Foundation, Inc. +# Copyright (C) 2001-2008 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License @@ -49,6 +49,10 @@ (_c('Delivery attempts will continue to be made'), _c('.+'), _c('(?P<addr>.+)')), + # Googlemail + (_c('THIS IS A WARNING MESSAGE ONLY'), + _c('Message will be retried'), + _c(r'\s*(?P<addr>\S+@\S+)\s*')), # Next one goes here... ]
Also, reading the code, I understand that the .getDeliveryStatusChangeTime method is not used anywhere (except in bin/export.py and Mailman/Commands/cmd_set.py); wouldn't it be sensible to remove it altogether?
The time is set by the setDeliveryStatus method. Since the time is there, it seems reasonable to have a method to get it, even if it isn't widely used. -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan