From: Bill D. <bdu...@be...> - 2002-03-19 08:25:12
|
Deano! said: >> Personally, after having tried the "blacklist" approach for many >> years, I'm finding the "whitelist" approach is: >> (a) more effective, >> (b) less maintenance. >> >> Take a look at the TMDA website and see for yourself... You should >> not need anything else, and it's relatively maintenance free once set >> up. >> > > I agree that TMDA is a good solution. For SPAM. But, it doesn't file > the mail I want*, it just cuts down on unwanted messages... I guess I'm > asking if there's either a certain order of precedence that needs be > adhered to, so that the mail filter* app doesn't accept all the mail > before* TMDA runs, etc, and if SIEVE had any similar function to TMDA > built-in (whitelists, etc)... Filing mail isn't the purpose of TMDA. Use either the MTA or the delivery agent for that. I can only speak for myself, but using Exim as the MTA and procmail as the delivery agent, I can do all that. I use exim to handle deliveries to mail files without hitting TMDA (like for mail lists) while procmail can be used for mail which goes through TMDA, again, delivering mail where you want. > Also, is there any way, in TMDA land, to do the following: > > People without .tmdarc (or whatever) in their home directories, receive > all incoming mail normally; people with* .tmdarc just follow those > rules... Like, "default action is accept mail, unless user is actively > using* TMDA, in which case default is defer mail (unless whitelisted)". > Is this possible? I believe in wrapper scripts. The wrapper script I supply with the TMDA plugin checks for a user's .tmdarc file first for dealing with outgoing mail. Of course incoming mail is dealt with in the .forward file if one is present. If it is not (or just uses procmail) then it won't hit TMDA. So yes, all this is possible. -- Bill Duncan, VE3IED - BeachNet --> http://www.beachnet.org bduncan@BeachNetCommunications.com |