> On Tuesday, July 8, 2003, at 01:08 PM, Jeff Hedlund wrote:
> > So anyway, back to the original topic of why I avoided using
> > .qmail-default: It allows for a global mailfilter script that doesn't
> > break functionality of qmailadmin (with regard to catchall, etc) and
> > that works in all situations.
>
> Perhaps we could include a configuration option to insert an extra line
> before the vdelivermail line in .qmail-default. Or, should it be a
> part of vpopmail, so vadddomain and QmailAdmin both build the
> .qmail-default the same way?
>
Yes? :) I don't think it should go with vpopmail because it's not a
POP3/POP3S thing. This is an add-on feature, really, and as such belongs
with a companion product like qmailadmin. That being said, if we make the
migration away from compiled CGI, or at least create options to do an
SSL-wrapped call to the CGI in order to authenticate and add a user, this
would be very useful. For me, it all comes down to automation that will
allow customers to self-provision. Given the current ongoing economic
climate (cold and stormy), I'm looking for ways to keep overhead and
headcount low while still maintaining a high quality of service for my
customers, including adding new features upon demand, such as spam
filtering.
