Comment We are doing this already (Score 1) 484
We currently have a mail setup handling mail for about 50 000 users. We have a home-brewed solution which is unfortunately cannot handle imap at the moment. We have 3-4 P166 machines to handle the POPping, with the users spread over these machines. The mail spool is mounted from a netapp nfs machine. There are 2 or 3 dns-round-robined PIIs running sendmail.
The pop client and procmail replacement were coded in-house for speed, simplicity and remote authentication.
However, we are now working on a new solution, which would comprise the following:
3 HP NetServer LC3 machines running modified versions of cucipop and procmail, and sendmail. (This is for NFS safe file locking). cucipop is modified to authenticate off a radius server (via PAM). Procmail is modified to allow all mail boxes to be owned by one user. Sendmail user a virtuser table to accept and deliver mail. There are no extra users in the passwd file. These machines will sit behind a layer 4 switch (or failing that, use DNSRR)
We also have an exchange server (LC3) handling mail for about 400 users. It falls over all the time.
The pop client and procmail replacement were coded in-house for speed, simplicity and remote authentication.
However, we are now working on a new solution, which would comprise the following:
3 HP NetServer LC3 machines running modified versions of cucipop and procmail, and sendmail. (This is for NFS safe file locking). cucipop is modified to authenticate off a radius server (via PAM). Procmail is modified to allow all mail boxes to be owned by one user. Sendmail user a virtuser table to accept and deliver mail. There are no extra users in the passwd file. These machines will sit behind a layer 4 switch (or failing that, use DNSRR)
We also have an exchange server (LC3) handling mail for about 400 users. It falls over all the time.
