 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
8 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Last thing needed...| From | Sent On | Attachments |
|---|---|---|
| John Straiton | Sep 10, 2001 1:02 pm | |
| John Straiton | Sep 12, 2001 9:32 am | |
| Roland Schneider | Sep 12, 2001 10:35 am | |
| John Straiton | Sep 12, 2001 11:32 am | |
| John Madden | Sep 12, 2001 11:41 am | |
| John Straiton | Sep 12, 2001 12:12 pm | |
| Roland Schneider | Sep 12, 2001 12:37 pm | |
| Chris Meadors | Sep 12, 2001 12:44 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | RE: [courier-users] Last thing needed to get a working model | Actions... |
|---|---|---|
| From: | Roland Schneider (rol...@serv.ch) | |
| Date: | Sep 12, 2001 12:37:40 pm | |
| List: | net.sourceforge.lists.courier-users | |
--John Straiton wrote on 12.09.2001 14:32 -0400:
Well our current sendmail server is set up using sendmail/procmail. While any way we go is going to be alot of work, sticking with sendmail / procmail meant that at least we were working with an MTA/LDA that we've worked with before. Procmail was chosen I guess because it was the first LDA that we found that supported .forwards and autoresponders. Sendmail was kept just because it's the default on a FreeBSD installation and gets upgraded with every buildworld.
in /etc/make.conf:
NO_SENDMAIL= true # do not build sendmail and related programs
Should be default imho, my qmail was not upgraded for two years because it simply works and there are no new versions :)
I wouldn't be opposed to using another MTA/LDA, assuming that the user-controlled forwards and autoresponders would still be available, but we just had not traveled that path. I have heard of qmail and postfix, but I'm not familar with postfix and I've never heard of maildrop.
maildrop is just a filter like procmail, included in the courier-distribution and supported on this list.
But if you use qmail you dont need any mailfilters, qmail delivers mail efficiently into maildirs if you dont need quotas there.
.forward wont work out of the box, now you have to name the file .qmail-default and add any command there: forward the mail, reply autoresponse, check quota, call maildrop (or even procmail), play some sound and do whatever you want.
Checkout the qmail-page for dot-qmail, or the courier-page for dot-courier. They are both similar
The only thing I'd like to know before undertaking that large task though, is if it would handle the 1 user per domain with many email addresses task at hand. The solution I have right now works fine for 1 to 1 mapping, and I was only currently needing help configuring the 1 to many. Can your qmail/postfix/maildrop solution handle the 1 to many? (3 @abc-domain.com addresses all in MailDirs under 1 /home directory)
Name the domains, directories and uid's and it works :) There are some documents about toasters at the qmail-site, but if you want instructions on this list you have to switch to courier.
My concern is scalability. Our server isn't in full production right now and with only 425 domains on it right now, it's got over 1200 user accounts on it. At same-scale, when we put another 1500 domains on it, we'll have ~5000 user accounts. ( ls /home will be useless ). Clearly, converting to the 1->many idea would help that alot.
Scalability: stay away from patched monsters like sendmail and dont use procmail (not even maildrop) until absolutely necessary. But your server should have enough cpu and ram for imap already, dont forget to set softupdates on the spool-partition and sync the time with nfs.
Roland