Dude, you've gotta slow down. I don't like having 400 messages waiting for me to try to make sense of when I come back.

>> and the creation of the mysql vpopmail database seemed to go fine. However, the little test in the guide does not work

Login to mysql first. Try this...

/usr/bin/mysql --password="yourpass"

You should get a mysql prompt like this...

mysql>

This is where you input those 2 magical commands. If you did everything like he says to do, then you should be able to enter those 2 test commands and it'll work.

>> are we supposed to enter 'pass' and 'pass2k' literally, or are we supposed to enter real passwords

Real passwords. Just make up your own, but don't forget them.

>> part of the vpopmail section, it appears that I should be in the /home directory when I start

No, you should still be in /usr/local/src. At the beginning of that section, it says to untar the vpopmail source. This is done in the src directory. Any time you untar another package, always do that in /usr/local/src.

>> And finally, what do the following mean:

That stuff is only for Debian users. I think you're on Suse, so just ignore those. If you have errors afterwards, we may need to install those packages it talks about.

win32sux, I don't know what your problem is, but please stop. If it's not abundantly clear to you by now, the guy has made it pretty obvious that he's following ONE particular howto. He's NOT following qmailrocks.org. Did you just hear that last part? Should I repeat it???

You know what's going to happen? You're going to convince him to try something stupid like blending the 2 howtos together and he's going to get really really confused and have such a mucked-up installation that he's going to end up starting over again completely or end up quitting forever.

Please dude, if you want to help him, how about helping him with his current task and stop trying to confuse him by throwing a completely different set of instruction in his face.

there's nothing wrong with getting information from several sources... there's nothing wrong with variety... there's nothing wrong with making an INFORMED DECISION... and i'm not even speaking of the whole qmail guide, i'm just speaking of the vpopmail section...

DROP THE SARCASM.

Quote:

You know what's going to happen? You're going to convince him to try something stupid like blending the 2 howtos together and he's going to get really really confused and have such a mucked-up installation that he's going to end up starting over again completely or end up quitting forever.

stop jumping to conclusions, and stop under-estimating people...

qmailrocks.org is the most popular qmail guide out there and it's pretty ridiculous if you believe one won't be able to get any valuable information out of it... dude, IT HAS GOOD INFORMATION, in case you haven't noticed... that information can be helpful... dadepfan can read the information and decide for himself if he wants to use it, he doesn't need anybody convincing him to do anything... if it's not abundantly clear to you by now, this guy isn't a newbie, don't treat him like one...

Quote:

Please dude, if you want to help him, how about helping him with his current task and stop trying to confuse him by throwing a completely different set of instruction in his face.

i'm not trying to confuse anybody, now you're just making stuff up... i was just trying to let him know he had the option of not getting vpopmail set-up with mysql unless he really needed it, like for example, if he was gonna be dealing with several domains...

don't be so uptight man, relax...

Thanks

I think I got it installed OK!

Now, I'm trying to install qmail-scanner, but it needs perl-suid. The only place I could find perl-suid was in a Debian package. I downloaded that and unpacked the files, but I don't know how to install it.

D.

I'm actually running mine without suidperl. You can try this and see if it works for you... When you get the qmail-scanner-queue.pl script created by running the commands to compile it, you can edit the file and change the first line to read...

#!/usr/bin/perl -T

Then do...

chmod u+s qmail-scanner-queue.pl

This file belongs in the /var/qmail/bin directory.

i found an rpm in case you want one...

http://rpmfind.net//linux/RPM/fedora...18.1.i386.html

I hesitated to offer an RPM because I couldn't find one for Suse. The one you linked to is for Fedora, which might work just fine, but I dont know if it'll install everything where it belongs. If it works, that would be cool, but somehow I have a feeling it wont. I base that on nothing. It may work fine for all I know.

I do not have that file, so my installation probably did not get that far.

D.

Actually, I found that RPM earlier and tried to install it. There was a perl version conflict, so I updated my entire perl installation to a new version. Then the SUID RPM installed OK, BUT, as you guessed, it still doesn not work.

D.

When you run the commands for qmail-scanner, you should end up with a file called qmail-scanner-queue.pl in your source directory. You can move this file to /var/qmail/bin where it belongs.

mv /usr/local/src/qmail-scanner-1.22/qmail-scanner-queue.pl /var/qmail/bin

>> BUT, as you guessed, it still doesn not work.

How do you know? What makes you believe that? Did you see some error messages? Normally the problem renders itself when you try running qmail-scanner without suid and you may get some errors to that end showing up under /var/spool/qmailscan/qmail-queue.log.

Apparently all you need are a few perl modules and you'll have everything you need for suid perl. Try running these commands at the prompt (one at a time) and see if they work for you...

This should download and install the needed perl modules.

Well... All of these commands worked, and they did a whole lot of stuff. Want to tell me what they did??

In any case, after I ran these commands I tried the Qmail-Scanner install again, and still got this:

Trying to connect to the mail server from another PC on my home netword, using a correct Linux user and password, still does not accept the valid user & password. Even if I try the mail client in Linux on the same machine, checking mail returns this error:

>> Want to tell me what they did??

These are packages used by perl. The commands you ran installed the perl modules needed for qmail-scanner.

>> Can't do setuid

Well damn. I figured that would work. I guess we're stuck for the moment. I will see what I can find out. Hang in there.

Also realize you won't be able to check your email and properly test the system until you've gotten at least through step 11 because all of these take care of your run scripts.

If you want to bypass qmail-scanner, you can edit /home/vpopmail/etc/tcp.smtp and everywhere you see "qmail-scanner-queue.pl" you can change it to "qmail-queue". This will bypass qmail-scanner and interface directly with the normal qmail scripts. After you make this change, be sure to run...

/usr/local/bin/tcprules /home/vpopmail/etc/tcp.smtp.cdb /home/vpopmail/etc/tcp.smtp.tmp < /home/vpopmail/etc/tcp.smtp
chmod 644 /home/vpopmail/etc/tcp.smtp.cdb

... which will reread the file you modified. But again, all of this is pointless until you get through step 11.

Ok, I think I found something to help you...

cd /usr/local/src/qmail-scanner-1.22/contrib
gcc -o qmail-scanner-queue qmail-scanner-queue.c

Now you have a file called "qmail-scanner-queue" in your contrib directory. This is the wrapper we've been hearing so much about which will allow you to avoid running suidperl.

mv qmail-scanner-queue /var/qmail/bin/
chown qscand:qscand /var/qmail/bin/qmail-scanner-queue
chmod 4755 /var/qmail/bin/qmail-scanner-queue

The above commands will move your wrapper into the qmail/bin directory and change the ownership and permissions so that it's running suid.

Now, from the last time you did all this, you should have already copied your qmail-scanner-queue.pl script into your /var/qmail/bin. If you want to be sure, just check under /usr/local/src/qmail-scanner-1.22 and see if you have qmail-scanner-queue.pl in there. Move it to /var/qmail/bin as well.

Edit this file and change the top line from... "/usr/bin/suidperl -T" to just "/usr/bin/perl"

That's it! Lemme know how this does.