"Jason R. Mastaler" <[EMAIL PROTECTED]> writes:

> First, when creating a dated address for a header, we must reset
> $TMDA_TIMEOUT if we are just taking the default timeout override.
> Otherwise, the previous value of that variable will be used instead.

[...]

> Index: tmda-inject
> ===================================================================
> RCS file: /cvsroot/tmda/tmda/bin/tmda-inject,v
> retrieving revision 1.69
> retrieving revision 1.70
> diff -u -r1.69 -r1.70
> --- tmda-inject       30 Sep 2002 23:45:54 -0000      1.69
> +++ tmda-inject       3 Oct 2002 04:51:34 -0000       1.70
> @@ -166,7 +166,9 @@
>      elif cookie_type == 'dated':
>       # Send a message with a tagged (dated) address.
>       if cookie_option:               # check for timeout override
> -         os.environ['TMDA_TIMEOUT'] =  cookie_option
> +         os.environ['TMDA_TIMEOUT'] = cookie_option
> +        else:
> +            os.environ['TMDA_TIMEOUT'] = ''
>       field = Cookie.make_dated_address(from_address)

Instead of fiddling around with TMDA_TIMEOUT, why not add a timeout
parameter to Cookie.make_dated_address().

def make_dated_address(from_address, timeout=None)

And if the timeout is not specified (is None), use TMDA_TIMEOUT.  Then
you don't have to set or reset TMDA_TIMEOUT - just pass in the explicit
timeout or don't pass anything (in the reply-to case you mentioned).


Tim
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers

Reply via email to