Sam Carleton <[EMAIL PROTECTED]> writes: > The main thing I don't understand is the whitelist & > blacklist. > > I want to enable CONFIRM_APPEND so that when someone confirms > their email address, it is automagically added to my > whitelist. Does this mean that I set that to the same thing > as FILTER_INCOMING?
The incoming filter, set by the FILTER_INCOMING variable (default: ~/.tmda/filters/incoming), is a list of rules that TMDA processes in order to determine whether to let the mail through, to throw it away or to request a confirmation. The filter file format is documented at http://tmda.net/config-filter.html Among the rules you can use is the 'from-file' rule. You can tell TMDA to read a file and perform some action if the email address of the sender (hence 'FROM-file') is in the file. The following URL lists the rules and their options. It also gives some idea of how each is used: http://tmda.net/filter-sources.html Here is how you might specify a blacklist using the 'from-file' rule (this line is text you put in the incoming filter file): from-file ~/.tmda/blacklist drop This means that, if the sender's email address is found in the ~/.tmda/blacklist file, TMDA should 'drop' or throw that email away, no questions asked. The file containing the list of email addresses can be named anything you want. It does not have to be 'blacklist'. Actually, TMDA has no idea of whitelists or blacklists. It only knows how to do the action you specify if one of the sender addresses is listed in the from-file. The sender addresses are any addresses in the From and Reply-To fields as well as the envelope sender. This is documented in FAQ 4.6. http://tmda.net/faq.cgi?req=show&file=faq04.006.htp Here's how to make a rule for a whitelist: from-file ~/.tmda/whitelist accept It's the same 'from-file' rule, but you give it a file that contains addresses of people whose email you want to see immediately. The only difference from the blacklist rule (except for the file used, of course), is that your action is 'accept' instead of 'drop'. You can use more than one 'from-file' rule in your filter. I have three whitelist files. One is my main whitelist. I use the -autocdb option on that list so that TMDA maintains a hashed database of those addresses for speedy lookups. Since the hashed databases (either CDB or DBM) can't contain wildcards, I keep a second, text-only whitelist for my wildcarded domains. Finally, I keep a third, text-only file whose name is specified in my CONFIRM_APPEND configuration variable. I have TMDA append confirmed addresses there and I periodically move regular correspondents to my main whitelist file. That part of my incoming filter looks like this: # Search the explicit whitelist (a .cdb file) which is fast but # doesn't support wildcards. from-file -autocdb ~/.tmda/lists/whitelist accept # Now search the confirmed whitelist. These are "auto-whitelisted" # addresses just waiting to be moved to the whitelist.cdb. from-file ~/.tmda/lists/whitelist_confirmed accept # Finally, search the wildcard whitelist. This is a flat text file # allowing for wildcards in the addresses. from-file ~/.tmda/lists/whitelist_wildcards accept My blacklist file comes before any of these, to ensure that those addresses don't get through, even by accident. I hope that gives you some idea. There are sample rules at the bottom of the config-filter.html page referenced above. They are just examples to show how the rules can be used. Don't copy that whole block of text and use it as your incoming filter. It won't be what you want! Tim _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
