Hi! The problem is, that our tmda-server only acts as an relay for many other servers. There are no real local mailboxes, and I need an easy way how customers can simple manage the complete filter process. So I thougt, that I put an seperate list into the TMDA webinterface and check this list bevor all other TMDA-filters take care.
Hope you understand what I mean... so long, Andreas -----Urspr�ngliche Nachricht----- Von: R'twick Niceorgaw [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 26. April 2005 16:00 An: [email protected] Betreff: Re: Re: filter On Tue, April 26, 2005 9:42 am, Andreas Plachy said: > Hi! > > First thanks for answering, but this is not what I'm looking for. > To improve the performance I would check this list first. > After that there are several checks like spamassassin etc., which I would > not run if the mail would be dropped anyway at the end... > I would suggest running spamassassin before even getting to tmda .. that way tmda will not be overloaded. The other problem with your setup is how you going to maintain this list updated with all tagged addresses you will eventually generate? I'm also doing a user existence check as well as running SA on my server. However, I do it at MTA level (using qmail) (as soon as I get a RCPT request), I check for existence of the recipient and reject it with a permanent error if the mail is to a non existent user and run SA through qmail-scanner. If these two pass, then only mail gets to tmda. That keeps a lot of load off the server. -R'twick _____________________________________________ 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
