Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 have been searching LQ.org and Google for a few days now, trying to find some guidance. We're moving all web services from windows to linux (some have already been on linux for some time). I've got just about everything moved over, except mail.
This mail transition has been an interesting one. After searching, I cannot find a "how-to" that is more than 25% relevant to my situation. I figure if I can get a push one way or another that I will be able to get this figured out. I've never done mail on linux before.
My mail server has to be virtual (meaning, I don't want to create console users), and I have to have IMAP. I get the impression that postfix is a good choice for a MTA, and I'm not sure what is the best IMAP daemon. From what I hear, There's Cyrus, Courier and UW IMAP.
I hear that Cyrus has good virtual support, but then you have to configure and install sasl. I am running MDK 9.2, so installed the imap package on the cd, and tried to get it to work. I'm not sure which IMAP server it is. There's no cyrus.conf and the imapd man page says "4.2 Berkeley Distribution" ... so I have no idea what is installed...
Do I have to create users on both the imap and the postfix side to make this work? How do I integrate the two? I'm really lost.
Personally I like SquirrelMail as an IMAP front end. I also use postfix. 99% of the mail servers I install are MS 5.5 Replacements. I usually configure the box to use the "console" users you refer to. Its easy and pretty streight forward. I myself came from an Isp that used sendmail and had 13000 hardcoded users. It ran fine. I suppose that the virtual users that you refer to would be easier but I'm not so sure. I am in the midst of setting up a server with virtual users in the maildirs directory instead of in the spool/mail directory. I'll let you know. One good thing about currier imap is the ability to use a mysql address database. thats cool!!. Currier uses the maildirs system of set up though so go to postfix'es home page and get the instructions. They are pretty strait forward.
Thats correct, Squirrelmail is the imap client thats what makes it a front end. For the Imap server I don't think you will go wrong with Currier Imap. It uses the maildirs type of delivery so you should be good to go.
Well, I'd rather not have system users, but I'd rather have email than none at all. How does this all work if postfix supports virtual users, and imap supports its users. It's supposed to act as one system...a "mail server" -- I'm a little lost. Do I have to create users on both sides, both the imap and the smtp (postfix) side? Is courier hard to install?
Here's my other dilemma, and why I want virtual domains (if possible):
We host two newspaper domains (our paper, and our child paper). Both have the same accounts, but they're managed entirely by different people. Both have to have an editor account, for example. If the email is based on console users, how is that supposed to work? I can't have two seperate editor accounts. I'm not really stuck on anything, so long as it does what I need it to. But multiple domain support is essential.
As you can see, I'm a bit lost! I've never set up a mail server on linux before.
You don't need to use anything other than the Imap that comes with mandrake. What you need tocreat is a virtual domain and point it at regular users. Thats what it sounds like anyway. Have you checked the Postfix site there are tons of ways you can solve your problem. Once you get there read some of the solutions and pick the one that sounds right. As is the case in most things linux.... There are several correct ways of doning things.
Hope this helps. I'm actually putting together a website to answer these questions. It took me a long time to gather the info needed to build servers that we need. Stuff like Samba, mail, web and others. For someone that has never done it, It can be a daunting task.
You should look for Courier and Postfix
I have configured a
Courier IMAP+Postfix+Virtual Users+Antivirus+Antispam+Squirrelmail
all on redhat but since I have being using Mandrake more frequently I know it the same. Just open google and search for courier and postfix. You will get complete howto. You may try the Postfix site for virtual users. If you still have problems you can ask me.
Manpreetnehra, my impression of your message is that courier + postfix is capable of virtual users. I thought courier was incapable of such a thing. I was under the impression that cyrus was the only one.
Will write back after I get some more time to work with this, on a less busy day at work.