Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I got this location from the sig of another poster, and he (DonBoy) has been good enough to provide me with a constant supply of advice. Here was one of the last posts on the "Qmail Error" thread:
Originally posted by Donboy ummm, no you misunderstood.., maybe I confused you somewhere. You actually need qmail-pop3d. When a user wants to login to your system and check their email, qmail-pop3d is responsible for checking their username and password to be sure they are real users. Once they are approved, qmail-pop3d will download messages from their /home/vpopmail/domains folders and deliver the messages to the end user.
I hate to say it, but I'm afraid you may want to think about starting over. Don't get depressed. This stuff takes time. If anyone could do it, you'd have 11 year olds running servers! And I can also tell you that I went through this myself a couple of times before I finally got it right. The problem is... you're not used to seeing the output of these commands and you don't' know if everything is going like it should be going.
Just take your time and walk through each step VERY carefully and be sure you do exactly what it says. I know you've done this already, but after doing it again, you'll be faster because you'll know what to expect from these commands and you'll feel better about having done it right.
I also suggest dumping webmin for this. God only knows what kind of things webmin is doing to your configuration, and if it's doing something I don't know about, I may become lost and unable to help you because I don't know what things webmin has changed behind our backs. You should be able to install everything from a simple shell.
Another tip... don't just copy a hunk of commands and paste them into your shell window. Do each line at a time to be sure it works. You may also want to have a text window open and paste the same commands into there too, so eventually you'll have a script that you can run all at once and install a whole bunch of stuff knowing it will work fine because you've tested it already. This will allow you to start over and not lose much time because you've already got your commands sorted out.
On the bright side, it looks like you've got chkconfig all figured out! I can tell you're not comfortable using the command line, but believe me... once you get a good handle on it, you'll never use anything else. It's way too convenient.
Just hang in there... take it slow... and post back here when you hit even the smallest snag. I'm not going anywhere, and I don't mind helping. Yes it'll take a little longer, but once you've done it once, you'll never need anyone's help again because you'll KNOW what you're doing.
To kill qmail, just go to the /etc/inittab file and comment out that line that says SV:123456:respawn:/command/svscanboot. Now do "kill -HUP 1" and it should stop qmail completely.
Do a ps -ef and see if there are any qmail-related processes going. Post the output here if you're in doubt, but there shoudl be none.
To delete qmail, you can just do...
rm -rf /var/qmail
and that will take care of 90% of it.
Since you're starting over from scratch, I suggest getting rid of the users and groups you made in the last install, and get rid of ucspi-tcp and daemontools stuff also. Basically just go through the last howto you used and reverse everything you did so that there are no traces of a prior qmail install.
First, I'll complete the removing of all the stuff from the last try at installing this. Here are a couple of questions (for anyone) regarding the "how-to" I'm using.
1. The guide is all command-line work, and it does not specifically tell me exactly where I should be located (in Konsole). What directory should I be positioned in? For most things, it does not seem to matter, I usually go the the directory above the one being created by the 'mkdir' command because the following command usually moves me into the new directory. But it is not clear in all the guide sections.
2. This guide installs Qmail 1.03, and then applies patches. Can I substitute the latest netqmail? If I do, should I change the instructions to name directories and files netqmail? If I still run the patches, will it mess anything up?
3. Where can I get perl-suid for step 10 in the guide??
On this install, I'm going to go slower and ask questions whenever I see something wrong.
I'm in step 1 (installing QMail) of the http://sylvestre.ledru.info/howto/ho....php#tcpserver guide. I used netqmail-1.05 instead of qmail, and ran the ./collate sh as per the readme. That seemed to apply a patch, but the above guide applies 5 patches in step 1.3. Is the netqmail patch all-inclusive? When I try the "wget" command from the guide for the additional patches, I get the following for some of them:
I also got around the "forbidden" problems I posted in my last post, by downloading the files from a different site.
Now, I am at step #3 in the guide (TCPserver), and when I get to the next-to-last command in this section (make setup check) I get the following:
Linux:/package/ucspi-tcp-0.88 # make setup check
install: fatal: unable to write .../bin/tcpserver: text busy
make: *** [setup] Error 111
I'm not sure how to fix this. I'll look to see if I have a TCP server running somewhere, and try and shut it down. There is no 'tcpserver' located in directory /bin, but there is one in my current install directory (/package/ucspi-tcp-0.88/) and one in /usr/local/bin/.
I think you want to start in /usr/local/src and the guide assumes you are downloading everything into that dir and then unpacking stuff in there. So under /usr/local/src, there should be your qmail-1.03 and so forth.
After you begin using the guide, it should tell you to change directories when needed.
>> Can I substitute the latest netqmail?
Yes, but there are going to be some patches that don't apply. For example, in Netqmail they are taking care of the errno patch and I believe also the 0.0.0.0 patch, so you don't need to apply the pathes in the howto. Generally, you can apply whatever patches and use whatever qmail you want.
>> If I do, should I change the instructions to name directories and files netqmail?
Yeah, if you decide to use netqmail, you'll want to pay attention to the howto and always substitute "netqmail-1.05" instead of qmail-1.03.
>> If I still run the patches, will it mess anything up?
If you try to apply the patches from the howto into netqmail, I'm sure they will fail.
>> Where can I get perl-suid for step 10 in the guide??
Wish I knew. Sorry.
Also remember that you can always come back later and apply new patches afterwards. Even after you get everything up and running, you can always download the source again, apply the patches, and then run "make setup check" and it will overwrite your current setup with the new stuff. So applying patches later is very easy.
Looks like you are doing great! Sorry I wasn't here to answer your q's before, but I was out and about running errands today.
1. I've run the mysql commands, but I had to go in manually to give the two new users the appropriate permissions. The test still does not work (see my last post).
2. Also in the mysql commands, are we supposed to enter 'pass' and 'pass2k' literally, or are we supposed to enter real passwords?
3. In the actual installation part of the vpopmail section, it appears that I should be in the /home directory when I start, but it does not clearly say that.
And finally, what do the following mean:
apt-get install libmysqlclient10-dev If you are under debian, otherwise, you must have the mysql sources available
apt-get install zlib1g-dev If you are under debian, otherwise, you must have these sources available [quote]
I'm using SuSe 9.1, so where do I find the "source" code and how do I make it available??
from the vpopmail section of the qmailrocks.org guide:
Which option is best for me?
First of all, don't feel that a vpopmail installation without mysql is somehow inferior or inadequate. It's not. The choice of whether or not to use mysql with vpopmail, in my opinion, is a personal preference and basically comes down to 2 things:
1. How large is you mail server going to be?
If you are only planning on hosting a handful of domains on your mail server, I don't think it's really worth integrating mysql into it. I have a server that hosts about 50 domains on it right now and it does NOT have mysql integrated into vpopmail. It works perfectly fine. The qmailrocks.org mail server also does NOT have mysql built into it. It runs great. However, if you plan to host more than 50 domains or so, I'd say go with mysql. It makes it easier to manage a lot of domains and also makes porting the mail server to new equipment and locations easier. Of course, the decision is up to you. If you really want to use vpopmail with mysql on a server that hosts only 1 domain, knock yourself out. My opinion though, is that unless you are hosting a ton of domains, integrating mysql into vpopmail is simply making your mail server more complex than it needs to be. And as we all know, the more complex the plumbing, the easier it is to stop up the drain.
2. How comfortable are you with mysql?
If you're a newbie and you don't know jack shit about mysql, don't be a jackass. Just use the default vpopmail installation and save yourself the aggravation. I can't hold you hand though installing and setting up mysql, and you'll be hard pressed to find someone else that will. In short, don't get in over your head.