Matt Gourley wrote:
We're running that combination here, along with .procmail and .qmail files in each virtual user's home directory. Anything SpamAssassin marks as spam gets sent to the user's Spam folder accesible via sqwebmail, instead of being downloaded via POP. The solution runs great, but something is occasionally corrupting the .qmail files, causing delivery failures.
The .qmail file:
|preline /usr/bin/procmail -p -m .procmailrc
becomes:
&|preline &/usr/bin/procmail
vpopmail.vchkpw own the file, and permission is set to 600 (u=rw g= o=).
Here's the relevence to this list: I changed permissions on .qmail to 400 (u=r g= o=), and now, when I try to change the user's password using qmailadmin, I'm getting the following error:
Server error!
The server encountered an internal error and was unable to complete your request.
Error message: Premature end of script headers: qmailadmin
If you think this is a server error, please contact the webmaster Error 500
This is because qmailadmin cannot write to the .qmail file, since you changed the permissions.
The next release of qmailadmin (and a little further off, the next stable release) includes an option to allow per-user settings of spam checking.
In this new version, you would enable it with the following two configuration options:
--enable-modify-spam=Y
--enable-spam-command="|preline /usr/bin/procmail -p -m .procmailrc"
Then you wouldn't need to change permissions of the .qmail file, and it would no longer ruin your .qmail file.
Look for the developmental release announcement Very Soon.
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
