Benjamin Tomhave wrote:
So, I just modified that check as follows:
DUMMY=`test -d $VHOME/Maildir`
if ( $RETURNCODE == 1 )
{
to "! [EMAIL PROTECTED]"
exit
}
And as you mention below, this makes it so you cannot change your catchall through qmailadmin...
I see... qmailadmin does not handle automated things like that-that I know of. But wrapping vadduser around a script to create the .qmail file with the necessary filter would be fairly simple as well... *shrug* (of course, that would still be outside of qmailadmin)Yes, I could, but why should I if my current setup works? The only thing I end up breaking is the ability to change the catchall settings through qmailadmin right now, which is ok today. However, there's also the point that I have already trained my users to update their SA preferences through my SquirrelMail plugin, not through qmailadmin, and it would not be helpful or wise to tell them to go use something different now.
That's agreeable, but all the setting in qmailadmin does right now is turn on or off spam filtering. It doesn't change the preferences, so they'd still have to use your SquirrelMail plugin for that (at least, for the near future).
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.
Jeff --
/\ /\ .. .. .. [EMAIL PROTECTED] / \/ \ a t r i x . . . . . . . (770) 794-7233 s o f t w a r e i n c .. .. .. http://www.matrixsi.com
