I am forwarding an e-mail from the RPMS list, discussing the qmail rpm by
Bruce Guenter. The point is, that running qmail-pw2u effectively destroys
the /users/assign file and all virtual domain info that is there. the
question is, how do we deal with that, and how should programs like vpopmail
deal with that (theoretically there is users/append, but it seems that
nobody is using it, it holds redundant data)? all documentation concerning
virtual domains is talking about users/assign, so it seems qmail is stepping
on it's own toes here.
>On Mon, Mar 19, 2001 at 07:45:06AM -0600, Jim Cook wrote:
>> At any rate, when I first got vpopmail implemented, I go and create a
>> virtual domain and a virtual user, and all is good. I can telnet into
>> port 110 authenticate myself and everything is working fine. Then within
>> 30 to 40 minutes of doing this, I try to authenticate myself and it says:
>>
>> vpopmail[1820]: vchkpw: No user found [EMAIL PROTECTED]:127.0.0.1
>What likely happens is that vpopmail plays with
>/var/qmail/control/users/*. My qmail RPM includes an hourly cron job in
>/etc/cron.hourly that rebuilds those files from /etc/passwd. What
>vpopmail needs to do is to put its bits into users/append instead of
>directly into users/assign so that when qmail-pw2u is run it won't wreck
>the changes.
