Re: Extended Expiration?

Excellent. I'm looking forward to trying it out.

I'm currently in the middle of a rebuild project on my server though, and switching to FC6 at the same time, so it may be a little while before I get TMDA up on the new box with the latest build.

But once I do, I will definitely implement this idea.


----- Original Message ----
From: Mark Horn <[email protected]>
To: David Hoffman <[email protected]>
Cc: [email protected]
Sent: Friday, October 27, 2006 3:28:52 PM
Subject: Re: Extended Expiration?


On Fri, Oct 27, 2006 at 01:22:24PM -0700, David Hoffman wrote:
>Is there a way to feed the variables for times and actions from the config file instead of having to modify the code? Is your "ACTION_EXPIRE_DATED =" being taken from the config file, or do you actually have that in the code block like shown below? 

It will be taken from the config file.  I just put it in there in the
example code because I needed to get something from somewhere.  That
particular code will actually work.  If you copy it into a file, and run it
like this:

    ./MultiExpire.py 32d

It will give an answer based on whatever ACTION_EXPIRED_DATED is
set to.  I just put that variable directly in the file because I'm
not actually reading a config file, and I need to get that data
from somewhere.

When I modify tmda-rfilter, I'll use Defaults.ACTION_EXPIRED_DATED
which will be read from the TMDA config file.

>if the config file can have a line like:
>ACTION_EXPIRED_DATED = {'default':'confirm','1w': 'bounce','30d': 'hold','1Y':'drop'}

Yes.  Python will happily allow both formats.

Thanks for the feedback.