It's a common occurrence that many of the confirmation requests sent out
by TMDA will bounce. However, on my system, when these bounce messages
return, they trigger the following error (see the bottom of this
message), due to the fact that there is no SENDER set.
I am using TMDA within a larger system of spam control that consists of
SpamAssassin and some of my own, home-grown filters. I run this all
under the Courier MTA (I'm using version 0.43.2 of that software, a
fairly recent release). Because of all this, one of the paths that
email travels through does not result in SENDER being set before TMDA
gets invoked (this occurs when the MTA returns a non-delivery message).
This is the cause of the problem I mention above.
Non-delivery responses to confirmation requests should never require any
further response. Therefore, I believe that TMDA doesn't really need to
know the sender in this case. Can any of you think of a way to make
TMDA recognize these kinds of responses, and to thereby handle the
message in such a way that the code on line 236 of tmda-rfilter is
completely bypassed?
Thanks in advance.
Here's the error, from debug.log:
Uncaught Python 2.3 Exception (Wed Nov 5 06:44:57 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 236, in ?
raise Errors.MissingEnvironmentVariable('SENDER')
MissingEnvironmentVariable
--
Lloyd Zusman
[EMAIL PROTECTED]
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
