> The reason I chose to move away from using the .qmail-default file is > because you won't always get the correct username. If you are not using > per-user preferences, then it wouldn't matter. > I'm using sql-based per-user preferences with maildrop and SpamAssassin. Everything is work well. Only problem has been aliases, which are done away with, so no more problem.
> So it's not a matter of being a bad thing, just doesn't cover all > the bases. > Hasn't been a problem for me. I set a default left for those who don't have preferences assigned and then if they do have preferences, those get used instead. > It is easy to modify qmailadmin to default spam filter to on. When > creating an account, you just want the spam filtering checkbox in the > checked state, which is a matter of modifying the template. > Except that under the current compiled-CGI design, I can't use qmailadmin for automated account creation, I still have to use ssh keyed calls to the mail server for use of the vadduser command. This is one of the reasons I'm hoping a PHP version will take off soon.
