SCS E-mail Infrastructure

1. SCS E-mail Infrastructure Upcoming Changes2005

2. Topics • Why we’re doing this • Existing architecture • Sendmail architecture • LDAP and mail addressing • Mail routing issues • Anti-spam and other services • Long(er) range plans

3. Why we’re doing this • Existing architecture is many years old • Many components are no longer popular • Lack of support for modern needs (good anti-spam, anti-virus, etc) • Volume of mail has greatly increased since current architecture was designed

4. Existing architecture • MMDF running on all UNIX hosts • White pages (static tables) used for name lookup and routing • 4 MX machines for incoming mail • Outgoing mail can go through any host • Mail spool on UX, IMAP and other hosts

5. Sendmail architecture • Sendmail will be the new MTA • Incoming mail will route through MX machines • Most edge machines will not directly deliver mail to external hosts • Most mailers will use smtp.srv as outgoing SMTP server

6. LDAP and mail addressing • LDAP will replace white pages • CS will maintain local LDAP information, but tied to campus • LDAP used both for mail addressing and routing information • “Fuzzy matching” rules will change to a static set of preloaded acceptable addresses: userid+, firstname.lastname, possibly others

7. Mail routing issues • Instead of individual hosts delivering directly to non-local addresses, mail will go through central hubs • Users will still be able to control mail delivery actions if mail is delivered to a private machine • SMTPauth service will be offered, eliminating need for VPN in most cases

8. Anti-spam and other services • Anti-spam will run on all incoming mail (will run on MX machines) • Same for anti-virus • Improvements to webmail (better hardware, different software posssible) • SMTPauth will be offered

9. Long(er) range plans • Web services to allow users to edit LDAP information • Web services for many “jeeves” functions such as changing mail forwarding

10. Questions?