1412485
story
itwerx asks:
"A client of mine is wedded to Exchange 2000 for their email server but would like to move away from Outlook Web Access (OWA) for security reasons. There are several possibilities but I'm wondering what experience the Slashdot community has had with these (or other) options."
imp (Score:4, Informative)
IMP is the Internet Messaging Program. It is written in PHP and provides webmail access to IMAP and POP3 accounts.
Re:imp (Score:3, Informative)
Note that IMP (email) is only one module [horde.org] of Horde. Adding the modules together and it trumps what MS WebMail offers by quite a bit.
Re:imp (Score:3, Informative)
One other thing, though - as PHP doesn't support persistent IMAP connections, you'll find that it can be quite slow in some cases. The Horde project has recently released a Imap Proxy [horde.org], which speeds things up a fair amount, and reduces load on the servers. It works very nicely, and is extremely simple to set up.
Oh, and I have heard of people having bad experiences using a PHP accelerator with Horde, although I've had it running with no problems here. YMMV, etc....
Three cheers for IMP! (Score:2)
Re:Three cheers for IMP! (Score:1)
Re:imp (Score:1)
Your best bet is OWA in SSL mode on exchange 2000.
use a client certificate And HiPerExchange [hiperexchange.com] to fortify the speed with an excellent cache engine, and even let you mobilize it on an offline notebook.
It's like having your own slim and fast web based Exchange server on your machine that goes everywhere you go.
Exchange Server 2003 (Score:4, Funny)
Re:Exchange Server 2003 (Score:3, Insightful)
MS has not offered security up front. They have been pushed / shamed into it - kicking, screaming, and dragging their feet.
Microsoft's mission is to make as much money as possible. Their customer's needs and desires are secondary. Note that MS is not alone here. The standard business model of (most) commercial software is to sell upgrades. This is one of the main reasons that Open Source is taking off.
Re:Exchange Server 2003 (Score:1)
And yes, I REALLY believe that M$ is beginning to realize that poor security hurts their bottom line. And that means they will start to do something about it.
Re:Exchange Server 2003 (Score:2)
One of the reasons you buy commercial software is for support. Exchange is VERY EXPENSIVE. I expect (and customers should demand) that MS fix all security related issues in all current software without being forced to buy new software. MS has over 40 BILLION in cash. They can more than afford to fix their software, and they OWE their customers to do so.
Re:Exchange Server 2003 (Score:2)
And your point is? They already do that! Exchange 2000 was released in the summer of 2000, so you would assume that 5.5 had its last sale in mid 2000. And regarding your complaint about design flaws, if you didnt like the design then you shouldn't have bought the product, right?
Security updates will be available until the end of the Exchange 5.5 extended support period, December 31, 2005 [microsoft.com].
SquirrelMail - Webmail for nuts (Score:5, Informative)
We have used SquirrelMail [squirrelmail.org] for som time now, and our users are very happy. Stay with open standards (IMAP/SMTP/LDAP), and you can replace components in a system (eg. Exchange) without changing everything.
From http://www.squirrelmail.org/ [squirrelmail.org]:What is SquirrelMail?
SquirrelMail is a standards-based webmail package written in PHP4. It includes built-in pure PHP support for the IMAP and SMTP protocols, and all pages render in pure HTML 4.0 (with no Javascript) for maximum compatibility across browsers. It has very few requirements and is very easy to configure and install. SquirrelMail has a all the functionality you would want from an email client, including strong MIME support, address books, and folder manipulation.
Re:SquirrelMail - Webmail for nuts (Score:1)
Squirrelmail - You've gotta be nuts (Score:2)
Note: Even after mail filtering, I have some VERY large mailboxes. Many of my mailing list boxes have 1-2k or more messages, my main Inbox has over 6000 messages.
NOCC - Doesn't even split mailboxes into multiple pages. Utterly useless
Squirrelmail - Splits mailboxes into multiple pages but still barfs on large mailboxes on 50% of page loads. (To the point that apache must be killed and restarted.)
IMP - The only IMAP webmail system I've used that doesn't trip and fall flat on its face when dealing with large mailboxes.
Note: If anyone could point me to a webmail system that:
a) Uses very lightweight HTML. Preferably 3.2 or lower, for viewing on mobile devices.
b) Handles large IMAP mailboxes gracefully
I would really appreciate it. NOCC was the closest to a solution in category a), IMP is the only solution I've found in b) but it can't be viewed from my Kyocera 6035.
Re:Squirrelmail - You've gotta be nuts (Score:1)
Re:Squirrelmail - You've gotta be nuts (Score:2)
Re:Squirrelmail - You've gotta be nuts (Score:2)
> to install/upgrade/maintain too and its not
> totally standards based.
I'd be interested to know which 'standards' IMP breaks
Re:Squirrelmail - You've gotta be nuts (Score:2)
http://cvs.horde.org/cvs.php/mimp?login=2
Make it custom (Score:3, Informative)
I was looking around for a webmail, and all I could find was IMP and squirrelmail. Believe me theyre both not quite mature, although I saw IMP running for years at Plattsburgh State. Installation of either is a ROYAL pain and not standardized, so you have to design your server, OS and other settings for the webmail system. for eg, for Squirrelmail you have to use courier imap and either courier mta or qmail. For IMP, you need certain versions of PHP with certain compile flags plus install HORDE. Last year this was complicated dont know now..
I made my own webmail for the site Hazara.org and Changezi.info in PHP4. Took maybe a weeks worth part time work and I got it a perfect fit (except for downloading attachments). I tried to make a custom C-compiled CGI-based webmail system for qmail using XML, but had a tough time looking up docs for the c-client libs to be able to read Maildirs directly. Gave up on it after trying to use the IMAP method, still on the lookout for c-client docs now.
Please post any free solutions you come up with.
Re:Make it custom (Score:4, Funny)
all the functions you need to write a webmail app are already coded as modules and all you have to do is tie them together. the code from acmemail can probably be used to help one write a perl-based webmail application: http://www.astray.com/acmemail/
perl isn't as scary as some people make it out to be. and usually those people don't know perl, so they're talking through their arse.
Re:Make it custom (Score:2)
Re:Make it custom (Score:2)
Actually, the only time I ever had any problems with SquirrelMail was when I was using qmail -- but the problem was with the Debian package, not qmail. It worked fine after I installed the tarball from squirrelmail.org.
Re:Make it custom (Score:2)
Re:Make it custom (Score:1)
Re:Make it custom (Score:2)
Under debian, it was 90% apt-get install imp with a little tweaking afterwards.
In both cases, it's been solid to work with and I've never had any problems with it after initial configuration.
Re:Make it custom (Score:2)
Re:Make it custom (Score:2)
for eg, for Squirrelmail you have to use courier imap and either courier mta or qmail.
FYI, I have it running fine with Postfix as MTA. Installation was absolutely trivial on Gentoo Linux.
Re:Make it custom (Score:1)
I installed squirrelmail today inspired by this article and I must say that it was very simple indeed. Your observations about the imap servers required are not correct, the choices are:
cyrus = Cyrus IMAP server
uw = University of Washington's IMAP server
exchange = Microsoft Exchange IMAP server
courier = Courier IMAP server
macosx = Mac OS X Mailserver
other = Not one of the above servers
I see no real reason why it shouldn't work on others as long as they conform to the IMAP standard.
Your MTA requirement is obviously incorrect, since here the Squirrelmail choices are:
1. Sendmail
2. SMTP
The sendmail binary is provided by either qmail or sendmail and SMTP is supported by every MTA I ever heard of.
Custom writing a webmail client sounds like fun but do it for the right reasons...
Re:Make it custom (Score:1)
I've got several installations of SM using Sendmail + UW-IMAP, and several with Postfix + Courier-IMAP. Works great. I've used a few that used Sendmail + Cyrus as well.
.
Re:Make it custom (Score:2)
This is totally false. I use SM with UW IMAP and Sendmail.
Why would you say that you have to use courier and/or qmail?
From the config utilty:
SquirrelMail supports ANY mail server that offers a reasonable approximation of SMTP AND can use the sendmail binary that comes with most MTAs.
-Peter
Re:Make it custom (Score:2)
I use OpenWebMail [openwebmail.org] (used to be NeoMail) at home and it's not bad at all. I have a couple mailboxes with over 4000 messages it's only slow the very first time you open one (it builds an index). It has lots of features (multiple addresses on one account, text search, spell check, calendaring etc.)
If it talked to Exchange I'd be building a server for it for my client right now.
Re:Make it custom (Score:1)
It's not that bad. I've been running Squirrelmail for over a year on UW IMAP and Postfix. There's now an RPM install, and it's included with the latest versions of Redhat. After you've installed you have to run a Perl script to set which IMAP server you're using (choice of Courrier, UW, Cyrus), what your hostname and site names are, the default themes, where you want to save tmp files, LDAP support etc. Works fine with Sendmail and Qmail too. Not hard. If you want to customise there are a lot of plugins you can use, or write your own.
Just about anything will work (Score:1, Informative)
Most web-based mail front-ends use IMAP or POP to access the users' mailboxes. The hardest part will probably getting authentication to work properly. You'll need to pass the credentials back to the IMAP/POP virtual servers, but that should be easy to do, especially with some kind of forms-based logon.
Re:Samsung Contact (Score:1)
Re:Samsung Contact (Score:1)
could avoid webmail and use VPN instead. (Score:1)
What is web mail for? If it is for your own employees, then perhaps VPN for remote access is a more general answer to the question.
linux oriented solution would be to tunnel the necessary mail ports over an ssh. MS Win* solution would be a VPN client, like Nortel Extranet.
Re:could avoid webmail and use VPN instead. (Score:3, Informative)
It depends on what you're aiming at, to be honest; VPN is more secure, but you have to have the necessary software installed on the client.
Re:could avoid webmail and use VPN instead. (Score:1)
Yes, it depends what the person is trying to do. If your users travel with a laptop, then the VPN software will be there. In the next few years, everyone will have wireless ethernet, and just bring their laptops to the nearest open access point.
Calendaring (Score:2)
My thanks to all the posters, especially the persons who suggested SamsungContact and gave feedback on HiPerExchange.
Unfortunately the rest of the suggestions (so far) do not support calendar functions!!
The idea is to replace all of OWA, not just the email portion of it!
Re:Calendaring (Score:2)
Re:Lotus Notes (Score:2)
Re:Calendaring (Score:2)
Let the morons begin (Score:2, Interesting)
If you want users to be able to set up meetings, check their co workers schedules, send email, look up their contacts etc, and the repsository for this info is Exchange your pretty much stuck, or your going to spend serious time, integrating a lot of different solutions, into something much less slick.
You might want to look into ways you can lock up outlook with web acccess. First off run it on seperate computers of course from the Exchange server, place the OWAs in the DMZ, prefrably make ppl VPN into them, run Microsofts new proxy server as an added security meassure. Run really good firewalls, you might even want to look into running reverse proxies on a UNIX platform in order to "shield" the MS machines more.
SuSE Linux OpenExchange Server (Score:3, Interesting)
Re:SuSE Linux OpenExchange Server (Score:1)
twiggi is worth a look (Score:1)
JiCal does some of the calendaring.. (Score:1)
JiCal (Score:1)