What are the odds of letting administrators input their own .qmail-default? I definitely agree with getting rid of catch-alls. They're a never ending thorn in my side, but I'd love to be able to enter a custom .qmail-default file, or change on of the pre-existing options...I'm guessing as always I'm finding the most complicated way of doing it, but suggestions would be great.
Also, I've been setting my .qmail-defaults as permissions 644 owner root so that the user can't change them back. If the simple answer is to keep doing these manual changes on new domains that's fine, I'll write a wrapper, but I like qmailadmin and vqadmin. Also is there any progress on the skin able qmailadmin that was being talked about on the list about 4 or 6 months ago? I've been eagerly awaiting that. Thanks! Tren ----- Original Message ----- From: Michael Krieger <[EMAIL PROTECTED]> To: [email protected] <[email protected]> Sent: Sat Sep 08 09:24:24 2007 Subject: Re: [qmailadmin] New features I just modified the template to remove the text/link for the option of setting remote catch-alls. I could easily remove the dot for local catch-alls, but don't mind those as much. Modifying it out of the template means it's still possible, but good enough for all but the very clever. -M Jeremy Kister wrote: > On 9/7/2007 8:30 PM, Jeff Koch wrote: >> I think a really nice feature would be the ability to remove global >> catch-alls and enforce 'bounce-no-mailbox' in the configuration. > > +1 > > I have code that goes through all .qmail-defaults every few days to > make sure all are set to bounce. not letting users set it that way > would be better. >
