Thanks, but we managed to find the problem and solve it after many hours of searching around!
It turned out that because we have two mail servers, both with mounts to a centralised filer, that when mail came into one of the boxes, the filter file couldn't read the cdb lists because "No module named cdb" was spat back. However, on one of the mail servers, cdb was installed, and when command line python was run, and running "import cdb" ran fine. Worked out that the other mail server did not have python-cdb installed, therefore whenever incoming mail was directed through that mail server (for load balancing), the cdb module couldnt be loaded! Thanks for the quick reply anyway. Mike > "Mike Usmar" <[EMAIL PROTECTED]> writes: > > > from-cdb ~/.tmda/blacklist.cdb bounce > > BTW, many find it easier to use from-file combined with the `-autocdb' > flag which maintains the .cdb file automatically. See > http://tmda.net/filter-sources.html > > > ImportError: No module named cdb > > > > Its saying there is no module named cdb, but I do have python-cdb > > installed. > > Strange. Can you cut and paste the exact output from python when you > import cdb? e.g, > > Python 2.2.2 (#1, Oct 17 2002, 18:12:45) > [GCC 2.95.4 20020320 [FreeBSD]] on freebsd4 > Type "help", "copyright", "credits" or "license" for more information. > >>> import cdb > >>> > > Also, what does your .forward or .qmail look like? I'd like to see how > you are invoking TMDA. > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
