On Saturday, July 13, 2002, at 06:46 , Jim Meyering wrote: > > Of course, the workaround is to add something like this to user_prefs > > unwhitelist_from *@amazon.com > >
Yeah, I'd like to see something like that too. Primarily because I don't like the idea of modifying the global "from the distribution" rules files in /usr/share/spamassassin. The reason I don't want to modify them is that if I modify them once, now, then any time I upgrade I have to duplicate my changes AGAIN. In the long haul, that's not a good plan. I want/need to modify the whitelist file because for quite a few of the entries, it's just completely wrong. Amazon DOES send spam, so why the heck would I want to whitelist them? Ebay sends spam, too. Yahoo-inc.com is NOT where their authenticated mailing lists come from, it's where their SPAM comes from. Etc. So, to fix this, I basically comment out every entry in that file (on the ones I've got experience with, they're wrong, so I'm assuming they're wrong for the ones I've never received email from either). I'd much rather be able to put my local changes into a separate file (a file that doesn't need to be replaced/duplicated when I upgrade spam-assassin). Then I'd just put my "unwhitelist" entries in root's user_prefs (I use mailscanner, with root's user_prefs), and never have to worry about the default distribution again. The other thing I want: to be able to specify a separate file where my whitelists and blacklists exist. It could be something general like "require somefile" which would be a text file that could contain ANY user_prefs commands (not just whitelist and blacklist hosts), or it could be something like "whitelist_file /root/.spamassassin/whitelists" and "blacklist_file /root/.spamasssassin/blacklists", which would just contain the hostname globs one per line. Why? For setting up a system of auto-blacklisting, where a program would take in submissions, by dropping messages into a folder, and then the program will append to the existing blacklist file from addresses it gleans out of the dropped messages ... but I don't want to modify the user_prefs file, so I want it to be a separate file from user_prefs. In /usr/share/spamassassin, I'd just add a new file since the docs say they read every file, like in a rc directory. But, unless I've misread the docs, they don't say the same thing happens with your .spamassassin directory. If they do, then that's great (and someone please tell me). If they don't, then I'd love to have that "require" or "include" directive as a second choice (the "whitelist_file" and "blacklist_file" directives are a third choice). ------------------------------------------------------- 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
