Multiple Front-End Solutions for Email and Calendaring?
USSJoin asks: "I am looking for a solution which I can install on my servers, that will allow me to run my email, calendars, to-do lists, and other groupware-ish functions. Specifically, I want a solution which allows equal access through the web and over an SSH session -- so that everything I do on one is accessible through the other. After extensive googling, I found Zimbra, which is nice and AJAX-ified, but doesn't include a to-do, and doesn't seem to have any way to deal with calendar access that is not made through the web front-end. I also found Citadel, but it seems like while it's a cute solution, it's quite cobbled-together and filled with hacks. This is especially true with its major Telnet interface, which seems dangerous to me. Has anyone on Slashdot had the same problem? What solutions have you found? Are Citadel or Zimbra really great and I just don't see their true possibilities? Are there other things I should be looking at, or different ways to approach this problem?"
I'm guessing that you need it available via SSH because it's behind a firewall somewhere. Have you considered using a good web-based tool, and then using SSH to tunnel in?
Zimbra has a host of REST API's. These would allow you to access all your Zimbra data via SSH when needed. You could also just set up an SSH tunnel to get to the web UI, unless by SSH you mean command line only.
What you're looking for is the same as a whole lot of other people are.
There are a few open source kits out there that are decent, but none of them are really done. Kolab and OpenGroupware look nice, but they have extremely limited client support. Kolab doesn't even have a fully functional web interface, instead relying on KDE's Kontact. They will both play well with Outlook on Windows through a for-money connector. Citadel has many of the features, but lacks *any* real client. I would love if the OSS kits worked, but people are much more interested in adding toys than finishing the project in good stages.
Sometimes the right answer is to spend money. Exchange, Notes/Domino, and GroupWise will do very close to what you want. There are a number of similar kits, like Kerio's mail server, Scalix (commerical OpenGroupware), OpenExchange, and whatever OpenMail became called.
As much as people think web apps are so wonderful, they really need to understand that they are not a panacea. Working in a web app for major use is quite a total pain; they just don't work as nicely as a native application. The interfaces are slow and there is no capability for offline operation. If the only fully-functional interface to something like this is a web app, then you have to largely discount it as an option. Users will hate you for forcing them to it.
If Evolution ran on Windows, you would be fairly done with the search. The devs haven't gotten around to making this a reality, so you are stuck in an annoying place. If you are looking for only yourself, then any of these solutions is probably sufficient. If you are looking for a product normal users will have to deal with, then look to spend money on software.
The Horde web site seems disorganized. There seems to be no demo.
I wish Open Source software authors were more careful about naming their software. Horde means crowd, with a negative connotation. Generally a horde is a group of poorly educated people, often savages.
Hi,
I've been looking at the free calendaring disaster for a while now - and it is; there are
perhaps 5-10 different packages, none of which interoperate; some very nice clients that
only talk to really crap servers and some very nice servers with poor clients.
Lets get some convergence here - please can we actually lock the
Zimbra, Open Exchange, Sunbird, Open Groupware, Kolab
(I must have missed some....)
guys in a cave without food for a while until they actually agree to work together?
For a concession I'll let caffeinated beverages in and a few computers with a copy
of all known calendaring specs.
(please toss in a couple of guys with MS programming experience so we can get Outlook
to talk to the servers).
OP: "This is especially true with its major Telnet interface, which seems dangerous to me."
P: "Dangerous? No it ain't,"
Telnet is inherently dangerous because it requires sending passwords in clear text across the wire. If you want to argue that this telnet based interface is not dangerous, you need to explain why it doesn't require sending passwords in clear text. I.e. why authentication is not important or how it encrypts the authentication (which would have to run on top of the telnet connection).
This can certainly be true in some cases. For example, the common day timer application does not require authentication to return the system time. However, if you are talking about making edits over telnet, that does in fact require authentication. How do you verify identity? You can't use the options telnet gives you, as they are not secure; you have to build your own.
There is also the question of whether or not the data needs to be encrypted. I can think of a number of situations where I would not want my email/scheduling info available in clear text.