[Mailman-Developers] VERP_DELIVERY_INTERVAL not yet functional ?
Dan Mick
dmick@utopia.West.Sun.COM
Mon, 11 Feb 2002 10:56:24 -0800
Fil wrote:
>
> @ Dan Mick <dmick@utopia.West.Sun.COM> :
> > Index: OutgoingRunner.py
> > ===================================================================
> > RCS file: /cvsroot/mailman/mailman/Mailman/Queue/OutgoingRunner.py,v
> > retrieving revision 2.7
> > diff -u -r2.7 OutgoingRunner.py
> > --- OutgoingRunner.py 2001/12/27 07:08:00 2.7
> > +++ OutgoingRunner.py 2002/02/05 23:36:20
> > @@ -49,7 +49,7 @@
> > if mm_cfg.VERP_DELIVERY_INTERVAL == 1:
> > # VERP every time
> > msgdata['verp'] = 1
> > - elif not int(mlist.post_id) % mm_cfg.VERP_DELIVERY_INTERVAL:
> > + elif not (int(mlist.post_id) % mm_cfg.VERP_DELIVERY_INTERVAL):
> > msgdata['verp'] = 1
> > # Fortunately, we do not need the list lock to do deliveries.
> > handler = mm_cfg.DELIVERY_MODULE
>
> Dan, I have used your patched version for a while, and the result is still
> very random. Some lists don't ever VERP, some others do. I can't find a
> reason. How are mlist.post_id modified ?
Well, as I said, I don't use this; I've hacked things so that every
message is VERPed by Postfix. So I'm not much of a testbed.
post_id is incremented for each post, by Handlers/AfterDelivery.py.