On Tuesday, July 23, 2002, at 03:11 , John Rudd wrote: > > my first procmail recipe will look to see if the sender is in a "totally > banned" list (there aren't multiple levels of blacklist are there? not > like there are multiple levels of whitelist? I wish SA was my symetric > about what features it offers for blacklists and whitelists, but it might > just be my own lack of reading), it gets deleted no matter who it's to or > from. > > my second procmail reciple will look to see if it's to > "[EMAIL PROTECTED]", and deposit it into one particular folder if > it is. I will use that to review messages from people who claim that I > shouldn't have blacklisted them. If anyone ever spams that address, then > they'll get put into the "totally banned" list. I'll probably be creating/ > managing this list by hand, unless there are two different levels of > "blacklist", in which case I'll have the more severe blacklist used here. > > my third recipe will look to see if my mailscanner spamcheck says the > sender is in my SA blacklist. If it is, it gets deleted without review (I > do this AFTER rule 2, because blacklisted users are still allowed to send > mail to user+blacklist, so that I can get messages from friends who sent > me something that was a false positive for rule 4, so I can whitelist them > and remove them from the blacklist). > > recipe 4: the mailscanner spamcheck will see if the message IS spam, but > does NOT mention a whitelist. If it matches, then it gets sent to a > filter program which will: a) submit it to the razor (though, I don't use > the razor so I don't know how useful that is ... I'd like to make sure it > gets submitted to all the right places, anyone know where else I should > send it? > ), b) send a "you've been blacklisted, here's the possible causes, if you > want to appeal, send it to [EMAIL PROTECTED]" message to the > sender (the worst spammers wont get the response because the sender is > bogus, so they wont ever appeal), c) add them to my blacklist. (note: when > invoked via procmail, A wont actually happen, blocked out by CLI argument, > I just mention that feature here for complete description of the program) > I'm calling this program "blacklist". > >
Oh, I also thought about having "blacklist" add them to a file that would be added to my sendmail "access" db later on, so that I could block them at the sendmail access level. The problem with that, though, is that then they couldn't send messages to user+blacklist because the access list totally blocks the sender. So I'm thinking what I might do is have the "totoally banned" list be implimented using that functionality (in which case I don't need to have that first recipe). ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
