Slashdot Mirror

obligatory Dilbert comic http://nakedape.cc/~wcooley/images/dilbert-unix-guru.gif

Cyrus IMAP is designed for this size of installation. You can split the backends up with Murder on the front-ends to distribute load; divide mailboxes on each host between filesystems (which, you'd presumably spread over multiple disks); use a SAN and GFS or other shared-storage cluster filesystems and share the spool among servers; use the new pre-release 2.3 code with mailbox replication and use more discrete, commodity components. Lots of other features that are designed for large-scale implementations.

For authentication, of course you have choices among LDAP, Kerberos (both of which are usable even if you're stuck with a Windows domain for authentication), PAM and other things. Very flexible; too flexible for some and it can be a bit confusing.

I've been working on rewriting the HOWTO, although I haven't made a ton of progress, it may still be useful to you: http://nakedape.cc/info/Cyrus-IMAP-HOWTO and here's a presentation I put together for Linuxfest Northwest: http://nakedape.cc/info/Cyrus-IMAP-Intro.

You mention a million mailboxes, but that doesn't really mean much--that is just an estimate of storage requirements. What is more important to determine is how many concurrent users you will have and how much actual traffic--storage is cheap, memory not so much.

Cyrus IMAP is designed for this size of installation. You can split the backends up with Murder on the front-ends to distribute load; divide mailboxes on each host between filesystems (which, you'd presumably spread over multiple disks); use a SAN and GFS or other shared-storage cluster filesystems and share the spool among servers; use the new pre-release 2.3 code with mailbox replication and use more discrete, commodity components. Lots of other features that are designed for large-scale implementations.

For authentication, of course you have choices among LDAP, Kerberos (both of which are usable even if you're stuck with a Windows domain for authentication), PAM and other things. Very flexible; too flexible for some and it can be a bit confusing.

I've been working on rewriting the HOWTO, although I haven't made a ton of progress, it may still be useful to you: http://nakedape.cc/info/Cyrus-IMAP-HOWTO and here's a presentation I put together for Linuxfest Northwest: http://nakedape.cc/info/Cyrus-IMAP-Intro.

You mention a million mailboxes, but that doesn't really mean much--that is just an estimate of storage requirements. What is more important to determine is how many concurrent users you will have and how much actual traffic--storage is cheap, memory not so much.

I've been wishing for better LDAP support in Evolution (and MUAs in general), and wrote up a page on my Wiki about Writable LDAP Addressbooks. Looks like they've got at least on covered.

I use Cyrus in a number of my packaged configurations, but for ease of migration and security Dovecot seems promising, although it lacks many of the advanced features that Cyrus has. It would probably be helpful to know exactly how many users you'll be serving and what your mail volume is. You might drop by #cyrus on irc.freenode.net and chat with people there.

You could, of course, look around and hire a Linux consultant to set it up for you.

I use Cyrus in a number of my packaged configurations, but for ease of migration and security Dovecot seems promising, although it lacks many of the advanced features that Cyrus has. It would probably be helpful to know exactly how many users you'll be serving and what your mail volume is. You might drop by #cyrus on irc.freenode.net and chat with people there.

You could, of course, look around and hire a Linux consultant to set it up for you.

If you look in your local computer monthly (most cities have at least one) or newspapers, you're almost certainly going to find a handful of local consultants, who will be happy to build a system for you and install it just as you want it.

I do this, although I generally work locally (in the Portland, Oregon area). I'd be glad to help if you'd like to pay the extra shipping (there's usually shipping to get the parts to me, then I deliver the system myself). I can do post-installation customization if you want to allow an incoming external connection via SSH or FreeS/WAN. I'm building a mail server for a client just this week; cost with on-site installation, local admin training, and integration with their existing systems is going to be around $3000.

I'd even be glad to give you hands-on training and on-site installation if you want to pick up the cost for the flight. (Most don't, which is why I mostly work locally.)

See Naked Ape Consutling.

Is it common for stock to be given out as compensation, directly rather than options? I am under the impression that I am being awarded $X in addition to my salary, and I will not be required to actually pay for these when the time comes; rather, they are a direct form of pay. Is this at all plausible or likely, or have I just been misled?

Okay, I see the output. Now, where'd you get this? I didn't see it in the HTML, in the first letters of the sections, etc. Was this supposed to reveal the "cookie" or was this it?

I don't think I'll even ask about what this code does. It's far beyond what I'll ever understand. Okay, I see what the 'substr' does. Okay, it exec's perl. (Where the heck does 'perl' come from?) Jeez, stuff I've never seen before.

JAPF, Just Another Perl Flunkie


Wil
--
Internet Meta-Resources:

"who" refers to people, i.e., kids. "what would refer to keyboards.

ID-10T Error: Are you sure it's plugged in?


Wil
--
Internet Meta-Resources:

Nope, I'm too stupid to see it. Pointers?


Wil
--
Internet Meta-Resources:

I think you mean "r474rd00d"


Wil
--
Internet Meta-Resources:

Hey, don't you know Kellog's has (tm)'d the phrase "Seize the Day"? I saw it on an ad for cereal on the blood-pressure machine at Safeway.


Wil
--
Internet Meta-Resources: