After some system upgrades, I began to get this in my debug log:
Uncaught Python 2.3.4 Exception (Thu Aug 19 17:30:13 2004):
-----------------------------------------------------------
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 891, in ?
main()
File "/usr/bin/tmda-rfilter", line 830, in main
orig_msgin_size)
File "/usr/lib/python2.3/site-packages/TMDA/FilterParser.py", line 1040, in
firstmatch
cmdin.flush()
IOError: [Errno 32] Broken pipe
Uncaught Python 2.3.4 Exception (Thu Aug 19 18:00:08 2004):
-----------------------------------------------------------
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 891, in ?
main()
File "/usr/bin/tmda-rfilter", line 830, in main
orig_msgin_size)
File "/usr/lib/python2.3/site-packages/TMDA/FilterParser.py", line 1039, in
firstmatch
cmdin.write(msg_headers + '\n' + msg_body)
IOError: [Errno 32] Broken pipe
I read the source, and noted that lines 1039 and 1040 were in the part
of FilterParser that deals with pipe filters. I tested each of the pipe
filters outside of TMDA, found the one that had broken, and corrected it.
Shouldn't we have a try block around the appropriate lines in
FilterParser, to catch IOError and perhaps others, so that failures at
least print the line that has the problem in the debug log?
Ed
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
