On Sun, Dec 31, 2006 at 03:23:59AM +0100, Dilyan Palauzov wrote: > Except for local addresses, most users don't use the results of > spamassassin. Hence I would appreciate if there is an option for the > user, that disables the filtering, or even better, global setting > (on/off), which can be ajusted by each user personally. In this way I > can finally escape from the spam attacks causing DOS.
The best way to do this is outside of SpamAssassin. There's no point in having a SpamAssassin config option telling it to not do anything, just don't ask it to do anything. :) > applies also for other settings. Therefore I would suggest if the > settings of all involved users in a mail are read and "the least > restrictive" one is choosen. E.g. if user1 and user2 have the same > adjustment, it is always taken into account. If user1 has > required_score 5 and user2 has required_score 6 and the site-default > is required_score 7, then a mail with 6 scores shall be announced as > spam for both users. And so on for each setting. SpamAssassin doesn't (and likely won't) do anything like this. It's up to the caller to request the right thing. If you're filtering in a site-wide setup, then you won't have user configs. If you want to try to fake something to do both outside of SA, and then call SA with the appropriate request, good luck. :) > From time to time, users want to rename their address. In such > cases I would like to have an interface like sa-user --rename user1 > user2, which transferes all settings (and bayer knowledge) from user1 > to (the new) user2. This is really only useful for SQL, otherwise it's going to involve filesystem operations which is better done outside SA. > And as I said some users have more addresses, but they want to keep > the same settings and bayer-knowledge for all of them. For such cases > it would be like to have user preference like > equivallent_user user1 user2 > meaning that if a mail is coming to user1 then the settings of user2 > shall be taken into account (and this implies also the bayes knowledge). SA already does this -- if you're running in delivery mode, so there's user configs and individual databses, you'll call SA with the appropriate user which should be after aliasing has completed. If you're running in site-wide mode (pre aliasing), you don't get individual configs or dbs, so this isn't an issue. -- Randomly Selected Tagline: "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." - Larry Wall
pgp7bS2mniyux.pgp
Description: PGP signature
