Many of us use either qmail-scanner-queue or simscan via patched qmail
ahead of vpopmail. If, as is good prcatice, we allow the scanner to run
under its own user ID, vchkpw will fail because instead of running as
user vchkpw it is running as the scanner user which doesn't have
access to the
On Wednesday 22 August 2007, Rick Widmer wrote:
http://vpopmail.sf.net/
5.4.20 - released 21-Aug-07
Feels odd to ask this, but in the UPGRADE document, it lists the pw_domain
columns as requiring updates, but my databases have just domain in them
except for the vpopmail table.
I've upgraded
When new users are added to vpopmail and you reach a certain number of them,
it creates a new folder and puts users in that folder. Then, when you reach
another level of users, it adds a new folder and repeats the cycle.
Presumably, it does the same thing with domains, but we have 25 domains at
On 2007-08-22, at 1534, Bob wrote:
Many of us use either qmail-scanner-queue or simscan via patched
qmail ahead of vpopmail. If, as is good prcatice, we allow the
scanner to run under its own user ID, vchkpw will fail because
instead of running as user vchkpw it is running as the scanner
On 2007-08-22, at 1952, John Simpson wrote:
On 2007-08-22, at 1534, Bob wrote:
Many of us use either qmail-scanner-queue or simscan via patched
qmail ahead of vpopmail. If, as is good prcatice, we allow the
scanner to run under its own user ID, vchkpw will fail because
instead of running