On Thu, 9 May 2002, Rob Siemborski wrote: > On Thu, 9 May 2002, Marc G. Fournier wrote: > > > Of course, I could do this using the .spamassassin/userprefs configuration > > file, but this won't work since there is no way for postfix to > > differentiate users :( > > I'll grant you that the extreme level of flexability you discuss > (modifying scores of individual tests) is probably not easily matched > using only sieve. Howevery, you can still aford a good deal of > flexability to the users using sieve, though per-catagory rescoring > becomes very difficult (esp when more than one catagory needs to be > re-scored). > > However, using the SA per-user preferences file doesn't work well under > the closed-server paradigm that Cyrus uses anyway (given that users don't > have home directories), so even if sieve was to have a "spam" extention, > you would still need to provide some sort of interface to modify and > locate that file (in a manner similar to timsieved).
Actually, that one is already built into Spamassassin, as it allows for the user of a database backend using DBI, which even has a rudimentary web based front-end to it ... I'm not asking for this to be added as 'default on all installs', only to take what Bob Finch created and put it in as a configure option (--enable-spam-extension), so that his work doesn't get lost and those of us that do want to use it don't have to go searching for and hoping the patch fits for "this version of cyrus" ... One of the things that I *really* like about SASL is the fact that I can add/remove features just by deleting the various auth libraries ... too bad there couldn't be some sort of 'programming API' for Sieve like this, where someone *could* easily add an extension outside of the spec(s) ...