> The problem with this approach is that sieve scripts are per user only. So > you'd have to create a script for each user. One could make a simple > bash/perl/whatever script that inserts and updates all the users' scripts, > but you won't be able to offer the custom sieve functionality to them.
This being true, I tend to create a basic sieve script per user, with webinterface for vacation message etc. Then allow users to create custom scripts if they want, but only if they explicitly ask for it and take notice they need to filter spam themselfs. _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
