RE: [vchkpw] Re: domain problem
Typically when people recompile vpopmail they do it by running a make clean or make distclean in the source directory and reconfiguring it. I've found this to be just a tad unreliable and I usually erase the source dir, and untar a fresh batch of source to make my new build. This usually resolves oddities like you described below. Also, after a make install-strip vpopmail will attempt to chown everything with the vpopmail:vchkpw user and group. Sometimes to verify (usually for my own sanity more than anything else) before I run the make install-strip I'll move the ~vpopmail/bin to ~vpopmail/bin.old that way I know that when it installs it won't fail at attempting to overwrite a file that's currently in use. I also, before the make install-strip, stop any pop3 or smtp services that might be using vpopmail for the same reason. Give that a shot. -Clayton -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2003 8:01 AM To: Clayton Weise Cc: [EMAIL PROTECTED] Subject: [vchkpw] Re: domain problem Thanks for the great help. I am now able to receive mail and check it with sqwebmail. I do still notice one thing. When I first installed on the new box, vpopmail user and group was #97. It was #89 on the first box so I changed it to #89 on the new box after noticing problems. Now I have reconfigured and reinstalled vpopmail, sqwebmail, vqadmin, and qmailadmin so they will all 'see' the new user number. When I look at /var/qmail/usera/assign I see than when I create new domains the user/group is #97. Also, if I ls -all /home/vpopmail/domains I see the user and group is 97 and not 'vopmail' or something. I can't login with qmailadmin either, any domain or account. Please help, I'm loosing it, : ). Clayton Weise writes: In /var/qmail/users/assign. You'll notice that the uid/gid of vpopmail is in that file, change it to the new uid/gid of the vpopmail user then run /var/qmail/bin/qmail-newu -Clayton -Original Message- From: jake [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 1:30 PM To: [EMAIL PROTECTED] Subject: [vchkpw] domain problem I installed vpopmail on a server, then moved to a new box and moved data over. 1 thing i missed was the user account, the vpopmail user was 97 on one box and is 89 on the other. I have a domain that I cannot add or delete. I changed the file permissions on the domain's folder but that didn't help. When I do a vdominfo it shows that domain as owned by the old user acount, #97. Even if I mv the folder for that domain out of the domains directory, it still shows up in vdominfo. If I use vdomdel it says that domain doesn't exist, if I try to create is, it says it's already there. Where else is virtual domain info kept? -- jake
RE: [vchkpw] Re: domain problem
Well.. for one thing, I've never seen qmail-pop3d used with the -x option, so I'm not sure how tcpserver handles that. I can't say for sure whether it would work or not. One thing is simply to try and run that script as-is and see what errors you get (if any). Also, check your pop3d log files and see if they report any errors. And last, but not least, make sure that no other applications are listening on port 110. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2003 9:46 AM To: Clayton Weise Cc: [EMAIL PROTECTED] Subject: [vchkpw] Re: domain problem That did it! Thanks again for the assistance. Sqwebmail was broken after that so I did the same thing to it and now it works great. I still see one problem, when I do 'qmailctl stat' it show pop3d up for 0 or 1 second. I can't see any log entries that would point to why. The qmail handbook suggests there could be problems with a run script, but I haven't touched any and it was working. I checked to make sure nothing else is running on port 110. Could something I did with all this vpopmail stuff have done something? My /var/qmail/supervise/qmail-pop3d/run file: #!/bin/sh # Dave Sill, 2001-11-06 # For use with The qmail Handbook, ISBN 1893115402 MAXPOP3D=`head -1 /var/qmail/control/concurrencypop3` if [ -z $MAXPOP3D ]; then echo MAXPOP3D is unset in echo $0 exit 1 fi exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -R -H -l 0 -x /etc/tcp.pop3.cdb -c $MAXPOP3D \ 0 110 /var/qmail/bin/qmail-popup uptimecomputing.com /home/vpopmail/bin/vchkpw \ /var/qmail/bin/qmail-pop3d Maildir 21 Clayton Weise writes: Typically when people recompile vpopmail they do it by running a make clean or make distclean in the source directory and reconfiguring it. I've found this to be just a tad unreliable and I usually erase the source dir, and untar a fresh batch of source to make my new build. This usually resolves oddities like you described below. Also, after a make install-strip vpopmail will attempt to chown everything with the vpopmail:vchkpw user and group. Sometimes to verify (usually for my own sanity more than anything else) before I run the make install-strip I'll move the ~vpopmail/bin to ~vpopmail/bin.old that way I know that when it installs it won't fail at attempting to overwrite a file that's currently in use. I also, before the make install-strip, stop any pop3 or smtp services that might be using vpopmail for the same reason. Give that a shot. -Clayton
Re: [vchkpw] Re: domain problem
Hi [EMAIL PROTECTED], On Fri, 07 Mar 2003 12:36:27 -0600 [EMAIL PROTECTED] wrote: Nothing in the pop3d log since 3/4, when this all started. If I just run the 'run' script it starts supervising pop3d, but it still only runs 1 sec Do a 'svc -d /path/to/pop3d_startup' and execute the run-script _manually_ on a shell. You should see why it is exiting immediately and therefore be able to solve the problem before continuing and giving the supervise-script a 'svc -u ...' again. -- Peter
