I recently upgraded TMDA on the GNU mail servers from 0.59 to 0.80,
and we're having some issues with the new version.
We process around 250K messages per day, and a few thousand of those
messages are handled by TMDA. We're running into the previously
reported get_payload issue (a lot), and it's something that should
probably be handled in TMDA itself.
The standard log entry from tdma_debug.log is:
Uncaught Python 2.2.3+ Exception (Fri Jul 11 14:49:37 2003):
------------------------------------------------------------
Traceback (most recent call last):
File "/usr/bin/tmda-filter", line 53, in ?
execfile(os.path.join(execdir, 'tmda-rfilter'))
File "/usr/bin/tmda-rfilter", line 152, in ?
orig_msgin_as_string = Util.msg_as_string(msgin)
File "./TMDA/Util.py", line 541, in msg_as_string
File "./TMDA/pythonlib/email/Generator.py", line 103, in flatten
File "./TMDA/pythonlib/email/Generator.py", line 131, in _write
File "./TMDA/pythonlib/email/Generator.py", line 157, in _dispatch
File "./TMDA/pythonlib/email/Generator.py", line 298, in _handle_message
File "./TMDA/pythonlib/email/Message.py", line 189, in get_payload
TypeError: Expected list, got <type 'str'>
This causes tmda-filter to return a status code of 75 (EX_TEMPFAIL).
Our MTA treats this as a temporary error, and queues the message for
later delivery. Of course it's actually a permanent error, since TMDA
will never be able to handle the message, no matter how many times the
MTA sends the email back to TMDA for processing.
Could tmda-filter be changed to return a different status code (to
represent a permanent failure) for this error situation?
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
