Alan Murrell <[EMAIL PROTECTED]> writes: > Hello, > > I am running: > > Mandrake 9.1 > Vpopmail > Qmail > TMDA v1.0 (installed from RPM) > > I used tmda-cgi to "install" TMDA to my email account, > and all seemd to go fine. I sent a test message to my > email account, but it just sits in the queue. I get > the following in '/etc/vpopmail/tmdadebug.log': > > --- START --- > Uncaught Python 2.3 Exception (Mon Jan 19 12:06:22 > 2004): > --------------------------------------------------------- > Traceback (most recent call last): > File > "/usr/lib/python2.3/site-packages/bin/tmda-filter", > line 53, in ? > execfile(os.path.join(execdir, 'tmda-rfilter')) > File > "/usr/lib/python2.3/site-packages/bin/tmda-rfilter", > line 213, in ? > orig_msgin_as_string = Util.msg_as_string(msgin) > File > "/usr/lib/python2.3/site-packages/TMDA/Util.py", line > 542, in msg_as_string > genclass = Generator.HeaderParsedGenerator > AttributeError: 'module' object has no attribute > 'HeaderParsedGenerator' > --- END ---
The problem is that the version of the "email" package that comes with Python 2.3 is being used instead of the customized version that comes with TMDA. The customized version can be found in the directory '/usr/lib/python2.3/site-packages/TMDA/pythonlib/email'. I suspect it is there, but the Python interpreter can't find it because of a botched search path (this is *not* the same path as your PATH environment variable). > The RPM actually installed 'tmda-filter' into > '/usr/bin', but I noticed froma bounce-back that it > was trying to find it in > '/usr/lib/python2.3/site-packages/bin', so I created > that directory (only 'bin' was missing), and copied > all the files the RPM put into '/usr/bin' into > '/usr/lib/python2.3/site-packages/bin'. Hmm. Unless your dot-qmail files specifically mention '/usr/lib/python2.3/site-packages/bin' on the first line or '/usr/lib/python2.3/site-packages/bin' is in your PATH (unlikely), you are still running the version in /usr/bin. That's ok, though. RPMs often cause Python tracebacks to print the path to where the program was built rather than the path where it is actually installed. You should be able to remove the .../site-packages/bin directory without causing any problems. Is there a "paths.py" file in /usr/bin? If so, it shouldn't be there. Removing it might solve this problem. Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
