Maildir

[Justin Bennett]

I'm loading my test box now. I'm going to go the route you mentioned, It 
involves less custom config, do you install courier from source? How 
often do you update it? Just wondering about security/bug fixes, or has 
this not been an issue. I will be allowing IMAP connections from outside 
the company (remote salesmen), so this may be a larger concern for me 
than it is for you.

Justin


John Seth wrote:

>Ok, flame me for being as opinionated as the next linux/unix guy who
>prefers qmail, exim, etc.
>
>RH comes with it's preferences sendmail and UW.  I help admin an all
>cisco /RedHat shop, with no problems.  I do use sendmail. Standard
>sendmail, with the sendmail.mc file configured to use virtualhosts,
>access db, with no problems.
>
>For mail delivery using maildir, we use standard procmail like so:
>Open /etc/procmailrc (if it doesn't exist, create it), and in it, put:
>
>MAILDIR=/$HOME/Maildir/
>DEFAULT=$MAILDIR
>
>I use Courier IMAP as a standalone server. I would strongly suggest not
>trying to use xinetd/inetd.  Courier IMAP has the ability to use
>wrappers, and ACL's. I use it for both POP3 and IMAP, and it runs
>beautifully.  You can set in the imap config file how many connections
>from one IP if you want to tighten things down, among many other config
>options.  This was a big change for my system, as I previously ran UW. 
>It was good, but Courier is better... IMHO.
>
>If you like Pine to go along with your maildir, no problem. There's
>patches.  You may find you'll need to custom install that, as you will
>need to compile in a patch to have Pine utilize Maildir.  I use Pine
>4.50 with a maildir patch and another.  Download Pine4.50.Z from UW,
>visit: http://hico.fphil.uniba.sk/pine-patches.html, and get the maildir
>patch at least.  Recompile, and Pine now reads maildir fine.  For
>Slackware 8.1, I used the following (I have no need for ssl in pine):
>
>cd pine4.50/
>patch -p1 <../pine4.50.maildir.patch
>./build DEBUG= NOSSL slx
>
>
>RedHat 8.0:
>
>cd /root/pine4.50
>patch -p1 <../pine4.50.maildir.patch
>./build DEBUG= lrh
>
>qmail is, again IMHO, way too complicated.  I attempted it once with an
>old box I had, and ended up having more problems since I am/was a newbie
>to using qmail.  I prefer sendmail's "everythings in /etc/mail" approach
>(with the exception of redhat which puts the sendmail.cf and
>aliases(.db) in /etc/).
>
>Being an ISP, I don't allow Outlook to connect to my IMAP server,
>instead I let our webserver only, since we use mod'd SquirrelMail for
>webmail.  You can also look into an OpenSource project called IMAPProxy,
>which I also use, and can be found at http://www.imapproxy.org/
>
>Happy mailing...
>
>
>  
>

-- 
Justin Bennett
Network Administrator
RHCE (Redhat Certified Linux Engineer)
Dynabrade, Inc.
8989 Sheridan Dr.
Clarence, NY 14031