On Sat, 2002-11-23 at 19:05, Jason R. Mastaler wrote: > David Guerizec <[EMAIL PROTECTED]> writes: > > > Manually released messages did still show up as not released. > > [...] > > > Index: tmda-pending > > =================================================================== > > RCS file: /cvsroot/tmda/tmda/bin/tmda-pending,v > > retrieving revision 1.37 > > retrieving revision 1.38 > > diff -u -r1.37 -r1.38 > > --- tmda-pending 22 Nov 2002 21:50:57 -0000 1.37 > > +++ tmda-pending 23 Nov 2002 11:48:41 -0000 1.38 > > @@ -313,6 +313,7 @@ > > msgobj['X-TMDA-Released'] = Util.unixdate() > > # Reinject the message to the original envelope recipient. > > Util.sendmail(msgobj.as_string(), recipient, return_path) > > + os.rename(msg, msg + ':3,R') > > Are you sure this is necessary? > > When a message is released with tmda-pending, an ``X-TMDA-Released'' > header is added to the message before it's re-injected. > > When tmda-rfilter sees this header, it adds the ':3,R' to the > corresponding pending file. > > Indeed, this seemed to work fine for me before your patch.
mmh, yes, this works fine the way it was designed for. I guess mixing development (cvs) and production (0.65) versions don't do very well. So may I ask why it's done this way ? As you know I'm working on a common python lib (modules) to strip down tmda-* 'binaries' to be able to develop more application on TMDA codebase. If this absolutely needs to be in tmda-rfilter, then I have to modularize this part too. David _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
