"Jason R. Mastaler" <[EMAIL PROTECTED]> writes:
> Lloyd Zusman <[EMAIL PROTECTED]> writes:
>
>> Sorry for the bandwidth ... and thanks for helping me see something
>> I had overlooked before.
>
> Use the logs Luke <wink>.
I used them but missed the significance of "postmaster". I incorrectly
thought it was a default that my MTA set because of <>. Duh!
By the way ...
The reason I manually set SENDER in cases such as these is because TMDA
throws an exception if there is no sender set. Given my complex set of
filters and the fact that I am running "tmda-filter -p" as one of these
filters, there are cases where my MTA doesn't get a chance to force the
SENDER variable to be set.
Is there any way that a future version of TMDA might handle the
no-SENDER case gracefully? ... perhaps by treating it as if it were "<>"
or something similar? Here's the exception that appears in debug.log in
these no-SENDER cases:
Uncaught Python 2.3 Exception (Fri Aug 29 16:05:24 2003):
---------------------------------------------------------
Traceback (most recent call last):
File "/usr/local/tmda/bin/tmda-filter", line 53, in ?
execfile(os.path.join(execdir, 'tmda-rfilter'))
File "/usr/local/tmda/bin/tmda-rfilter", line 222, in ?
raise Errors.MissingEnvironmentVariable('SENDER')
MissingEnvironmentVariable
--
Lloyd Zusman
[EMAIL PROTECTED]
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
