1 / 12

IMAP at FNAL

IMAP at FNAL. Jack Schmidt FNAL Disgruntled Postmaster Hepix April, 1999. Initial Design (low cost). Software Netscape Messenger for NT Hardware Dual 200MHz Pentium Pro with 192Mb of memory Server software and mail files located on a 20GB Software RAID 5 disk array

alden
Download Presentation

IMAP at FNAL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IMAP at FNAL Jack Schmidt FNAL Disgruntled Postmaster Hepix April, 1999

  2. Initial Design (low cost) • Software • Netscape Messenger for NT • Hardware • Dual 200MHz Pentium Pro with 192Mb of memory • Server software and mail files located on a 20GB Software RAID 5 disk array • Identical computer system available as hot backup

  3. Problems • Performance • Delays accessing user’s Inbox • Delays foldering mail • Delays in mail delivery • Quotas • shared messages • problems restoring after disk loss • no warning mechanisms

  4. Problems (cont) • Misc- • Corrupted spool area • Only on high activity days • Forwarding • No tools for diagnosing problems • Poor support from Netscape

  5. Solutions (?) • Performance • Brought 2nd server on line • faster controllers and disks • RAID 1 instead of RAID 5 • still software RAID • separate User storage from Mail server software • Disk Defragmentation • Balance users across disks. • Limit users to ~ 600 per current server configuration • Stop and Restart service nightly

  6. Solutions (?) • Quotas • disable shared messages • wrote warning program • modified user WEB interface to reflect quota information • Misc • Applied NT4 SP4 • Removed user’s ability to set forwarding

  7. Tools • Perl scripts for: • adding users • moving users • quota management • warning messages • qouta available on User web page • connected users • user activity (who gets all that mail?) • Freeware program examines threads • PMDF software for moving users between servers • mailstone program for load testing • Just started working with this!

  8. Client Issues • Early versions of Netscape poorly written • User education • keep folders and Inbox small • stick with one client • Different errors for same problem. • Netscape problems with corrupted mail. • Outgoing SMTP server incorrectly set. • Cache corruption. Need to cleanup in both Netscape and Outlook Express

  9. Sharing the Blame • Us • Initial system design • Should have spoke with other sites • Tried being cutting edge • Assumed it would be as easy to manage as our pop server • Netscape • poor support • poor design- separate file for each message • poor documentation • some things work differently than expected

  10. Immediate Future • IMAPserver1 652 users, 318 active • IMAPserver2 388 users, 167 active • 24% of mail inbound through our gateway is for IMAP! • 36% of data transferred through our gateway is for IMAP! • Need to shut off VAXes at D0 & CDF • Begin move in June, done by September • Finish moving Quickmail users

  11. Immediate Future • Continue with Netscape software • Buy true NT server: • 4 processors • 2GB memory • multiple busses • high-speed RAID controllers • Use RAID 0+1 • high-speed disks

  12. Central Mail Server • Central mail systems for all users to read mail • Cluster technology -allows system maintenance with no/little effect to the user • Waiting to see what Sun/Netscape offers • SIMS looks promising • Possible blackbox solution? • www.mirapoint.com

More Related