on 7/14/05 10:44 AM, Michael Shell <[EMAIL PROTECTED]> wrote: > I'd like to know what contents are allowed in the forward field of > qmailadmin - specifically as it relates to spam filtering. > > Suppose we want to add a line such as this to the forward > field (on a site that hosts many virtual domains): > > |preline /usr/local/bin/maildrop /mail/domains/0/mydomain.com/.spamfilter > > but this won't work (at least not under 1.2.0). This is probably > due to security concerns - there is a related post on this > topic recently: > > http://www.mail-archive.com/[email protected]/msg06124.html > > So, is there a better/alternative approach? Are there some new features > in later (post 1.2.0) or that are being planned for future versions > that might be of help? Although it might not be desirable to allow users > to put anything they want in the forward field, there should be a way to > support at least some form of spam-test-based forwarding. One approach > might be to allow users a way to select from a choice of valid lines > pre-created by the sysadmin.
We each came up with similar ideas independently. I was interested in a set of pre-fixed alternatives for the spam filter, and you are interested in doing something similar with the forwarding field. Maybe it is really one problem we both want to solve, but it is clear that for some, the interaction between forwarding and the --enable-spam-command option does not quite provide a solution. This was addressed in the thread "qmailadmin 1.2.7, forward to and spam detection" that started on 4/7/05, and I kind of assumed by your message subject that you were partly referring to that thread. I'm wondering at this point whether people think that pressure for new features to be added to "modify user" will continue to strain the limits of the current .qmail file model. I'm getting into vpopmail territory here, but it occurs to me that the .qmail file being a vpopmail thing is not really constrained by the limits of the Qmail heritage, and maybe some generalization of that model might help make it possible for an interface like QmailAdmin to provide more general and orthogonal control over a possibly ever-growing set of features. So anyway I thought this might deserve a little thought before anyone jumps to a solution for any of the related issues currently being discussed. Maybe I shouldn't try to get to specific at this point, but one thing that comes to mind as a possible ingredient in generalizing vpopmail's .qmail file functionality in a helpful way might be the ability for a .qmail line, perhaps one ending in the "|" symbol to be a filter line whose presence would alter the input received by all subsequent lines in the .qmail file. I'm not sure if this is a good idea, especially taken alone. In general I tend to envision that somehow the .qmail file capabilities might somehow support a more general control-flow and pipelining model. This then might permit QmailAdmin enhancements on the modify user page to flow more freely and for separate features to interact with each other in more well-behaved ways. Just some thoughts. -Kurt
