Slashdot Mirror
Choosing a Replacement Email System For a University?
SmarkWoW writes "The university I attend is currently looking to change the way in which is provides its students with an email service. In the past they used a legacy mail system which can no longer fit their needs. A committee has narrowed the possibilities down to three vendors: Google, Microsoft, and Yahoo. Representatives from these three vendors will be coming to our college and giving a presentation on the advantages of their systems. We're looking at other services these companies provide such as calendaring and integration with existing software that our university runs. What questions would Slashdot readers ask during these Q&A sessions? Which of these three companies would you recommend? Why? What advantages would each have that college-level students would take advantage of? What other aspects should we consider when making our decision?"
Are you from Microsoft? Yes? Well thank you for your time.
~ Ron Fitzgerald
Hi there
first how do I backup the system ?
( what your really asking is if your software system fails and it will all systems fail (e.g. gmail outage for a day) how quickly can I recover?)
we get attacked by a certain type of worm can I insert a rule into everyones policy to get rid of that ?
(its been delivered the filters did not catch it I want to reach in and take it away)
how do i get a log and bodies of the email sent out of the system for legal ?
how do I control the sending policy ?
(I dont want just anyone sending mail on behalf of my domain some people i want to restrict to only email inside the domain )
how can I add all the address's before people arrive ?
how does it work with mobiles ?
there's a start
regards
john jones
http://www.johnjones.me.uk
disclaimer : I work in groupware but for a different vender my blog reflects this
I work for a small-ish university in Canada and we run our own mail systems. With the proper software and expertise it's not that difficult to do.
Is there some reason that you're looking at external vendors? Not enough staff? Not enough internal expertise with email? Cost? Something else?
If you did decide to host it yourself, you could go the traditional route with a Unix-based mailserver, and something like Horde's IMP for Webmail. Or you could look at something like Zimbra, which has all your mail basics plus extra goodness like calendaring built-in.
As for who I would go with from Google, Yahoo and Microsoft - as a former sysadmin I would avoid Microsoft. This isn't because I'm some kind of Unix bigot - it's because in my experience they tend to oversell the capabilities of their products ... the true limitations of which you discover after the deal has been signed.
That may have just been the reps we had back in Ottawa, but YMMV.
I would be be asking either of these rep's is what service integrates best with your existing student directory service(AD, OpenLDAP eDirectory etc), and how do they go about managing mass account creation, recipient policies, group membership.
Its one thing to bring in a new mail service, but ongoing management and maintenance of users and mailboxes, it and how it interacts with other internal systems would be the most important thing to me from an administrative point of view.
I would be concerned about the privacy implications of using Yahoo Mail, Hotmail, or GMail for your student and faculty email. Now, granted, a lot of college students will be using one of those three for their personal email accounts *anyhow*, but for faculty in particular, and even some students, there could be some real downsides to using a third-party email provider.
For example, I don't know what Uni you're from, but a lot of Universities have faculty and students who are involved in research which might be of a nature where it might not be good to have them sending emails through a third-party. For example, professors and/or students working on Defense dept, Energy department, or CIA/NSA research (although, it might be that in such a situation, they would be using a more secure email system run by the government agency they are collaborating with, instead of the University email, anyhow, so maybe that's not such a concern).
Still, in general, I don't like the privacy implications of using Yahoo, Microsoft, or GMail for university email systems.
You might ask the representatives what guarantees of privacy they are willing to make to the University and it's students, faculty, and staff. I think I would hold them to a higher standard than what the normal Yahoo, MSN, or Gmail privacy statements offer.
My university switched to Google last year, and it's been amazing. Each student's course schedule is automatically added to their course calendar, and profs can add due dates, special events, etc. in a few clicks. Your point about Google Apps is a good one as well - I've found it much easier to do group projects or test reviews when I can create a Google Doc and share it out to classmates. At my job with the university IT deparment, we use Google Sites to keep our information coordinated. The whole system has proven amazingly useful.
I looked over a contract between Google and a large university and found it to be very dangerous to the intellectual property rights of the university and to the privacy rights of students, faculty, and staff.
For example, because email is being disclosed to a third party, such as Google, it could affect the dates of disclosure (publication) of information and could, thus, cause a patent application to fail because of an excessive time lapse between publication and the application. It is necessary to bring the provider into the tent of protection so that patent rights are not harmed.
And in these days of litigation, consider who will get subpoenas, the university or the provider, and who will get notice in time to go to court to contest the delivery of the materials.
The terms in some of these contracts make the provider the copyright owner, or at least give a perpetual non-revocable license to the provider, even beyond the lifetime of the agreement. That can lead to some rather unhappy faculty who find that their publications, and their notes and discussions, have been licensed away, forever.
Also consider whether the university can get the email back at the end of the contract. There is a good chance that it will not be able to do so.
And consider whether you think it is a good idea for students, who tend to experiment with life's options, to begin to build a lifelong dossier that contains their university life emails.
The number of issues of this type is huge and most university lawyers are either not equipped to comprehend them or don't care to do so.
Most people I know who have deeply considered these things tend to find it a really bad idea to outsource university email without very, very strong contractual protections that think through the issues of now and the issues that might arise in the future, particularly when the university wants to terminate the agreement or move to another provider.
If they don't give you a blank stare, you might have a viable vendor. It's like a tech vendor selling to a hospital needs to know what HIPAA is.
I work at the ITEE school at my uni, and our tech section was running Horde for our email server. It was superb. Alas, orders came from above that they wished to centralise the email servers and we got stuck on Exchange. It's crap compared to what we had. The web client is rubbish, and the mail server is dog slow.
I'd go with the above suggestion if you have the choice. Second choice, I'd probably recommend Google.
I intend to live forever, or die trying. - Groucho Marx
Until this fall, our university was maintaining one of, if not the largest, Cyrus mail system in the world. Over 50,000 mailboxes generating an average of 4,000,000 transactions a day (peaking at 5,000,000), hosted on a cluster of SunFire servers and StorEdge/StorageTek SAN. In-house, open-source...sounds great, right?
This year we estimated the cost of increasing our default inbox quota from a paltry 60 MB to 1 GB (a long-overdue upgrade). The total came in at about US$500,000, which is fiscally untenable at this point.
Then we were hit by a previously unknown ZFS bug that crippled mail delivery for almost a week while we worked with Carnegie Mellon, Sun and consultants trying to figure out why our system wasn't scaling properly.
We realized that sometimes outsourcing is the best alternative, no matter what in-house resources or requirements exist.
We just launched Google-hosted email for all students, which is projected to save $250,000 annually (or more if TCO is considered).
It was fun being the guinea-pig for scaling up Cyrus, but by partnering with Google we can deliver more reliable, larger inboxes and save money instead of spending it. DIY "let the CS department handle it" philosophies are great, but not always the best plan. Even for email, outsourcing can sometimes be the best option, not a cop out.
Don't. The CS department is interested in education and research. They may come up with an innovative solution and write a few papers about it - then abandon it, leaving it with poor documentation, a bad interface, hundreds of bugs, and idiosyncratic and non-standard elements.
IT is not CS. IT is a service.CS is a discipline. Asking the CS department to run the academic IT systems is like asking the English department to run the library. It's a non-starter.