In article <[EMAIL PROTECTED]>,
 [EMAIL PROTECTED] (Jason R. Mastaler) wrote:

> Doug Hardie <[EMAIL PROTECTED]> writes:
> 
> > Granted, but tmda should point out this limitation since it doesn't
> > have a workaround for it.
> 
> I didn't realize anyone used NIS any longer.  This is the first time
> in 5 years I can remember anyone bringing this up actually.
> 
> > At least the pending messsages go in the right directory now.
> > However, on a 1 GHz machine it takes several seconds to process a 2
> > line message.  I am a bit concerned about performance as our
> > mailserver processes hundreds of thousands of messages daily.
> > Python reads a ton of junk before it starts to do anything.
> 
> Something is wrong, as that sort of delay is not typical.  There are
> sites running TMDA on servers that process as much or more mail than
> this, but obviously I'd recommend several layers of spam defense
> before TMDA.  TMDA should generally be placed near the end of the
> spam-processing sequence to reduce the number of challenges being sent
> out.

Well, had to make more changes.  The filter definition files are not 
executed so couldn't use my workaround.  Finally figured out how to make 
HOME work.  However, when Defaults.py is called it first uses ~ to find 
the crypt key file before it reads tmdarc.  So I have come up with the 
following at the front of tmdarc:

os.environ['HOME'] = os.environ['HOMEDIR']
HOMEDIR = os.environ['HOMEDIR']

And then I have added the HOMEDIR envronmental variable which is set 
before calling tmda-filter.  The standard default definitions for the 
file names can be used.  Now everything through delivery works 
(whitelisted addresses).  Still have to try the response to a challenge 
yet.

NIS is a simple, low overhead tool that works quite well for us.  This 
tmda will eventually be at the end of the mail processing line which 
includes clamav and dspam (I doubt anyone will actually use both dspam 
and tmda).

_____________________________________________
tmda-users mailing list (tmda-users@tmda.net)
http://tmda.net/lists/listinfo/tmda-users

Reply via email to