"Max" <[EMAIL PROTECTED]> wrote:
>Primary box -
> accept incoming e-mail's for organization, users will be connecting via
>Pop only. All e-mail will be removed from the server and downloaded onto the
>users PC.
Maildir+qmail-pop3d.
>I do not need console/telnet mail for my users, only the root
>account for convenience (I am flexible what program I will use).
mutt is good.
>This box
>needs to selectively relay e-mail based on network address. (or if possible
>authenticate the sending user).
Selective relaying is no problem. There's limited add-on
authentication support available (see www.qmail.org), and various
pop-before-smtp mechanisms.
>I have 50 local users, and 40 remote users
>(these numbers grow quickly). We maintain mailing lists for the different
>office locations as well as the different departments.
No problem. ezmlm is great for lists, but if you're already using
something else, it can probably be made to work pretty easily.
>Secondary box -
> just in case the primary is down. This box needs to accept e-mail and
>relay to the primary, as well as selectively relaying based on network
>address. This machine will also host some announcement mailing lists. The
>lists have a large amount of users but are low volume.
Backup MX's are falling out of favor, at least among the vocal members
of this list. Why not just let mail queue up at the sending site?
>Mailstats from the current Linux/Sendmail machine (no office or external
>mailing lists are running on this box) are in the attached file.
They indicate a pretty light load for the hardware/software you're
considering.
>I need to provide LDAP to my users as well. I have been reading from
>http://www.openldap.org but will take a while for me to understand the
>config. This is not a big concern.
There is an ldap add-on for qmail.
>I intend to install a web interface to the mail system in the future, again
>I have not done an evaluation yet so I am really flexible to the
>configuration.
Haven't used one with qmail, but they're available.
-Dave
