Slashdot Mirror


Drop-In Replacement For Exchange Now Open Source

Fjan11 writes "Over 150 man-years of work were added to the Open Source community today when Zarafa decided to put their successful Exchange server replacement under GPLv3. This is not just the typical mail-server-that-works-with-Outlook, it is the whole package — including 100% MAPI, web access, tasks, iCal and Activesync. (The native syncing works great with my iPhone!) Binaries and source are available for all major Linux distros."

97 of 434 comments (clear)

  1. Hell yeah by cromar · · Score: 5, Funny

    That's right, Microsoft: open source software can gun for you too, motherfuckers!

    1. Re:Hell yeah by LibertineR · · Score: 2, Informative

      Sure you can, but Zarafa aint no gun.

    2. Re:Hell yeah by darkpixel2k · · Score: 5, Informative

      That's right, Microsoft: open source software can gun for you too, motherfuckers!

      I'm sure Microsoft is trembling.
      The site is so hammered I it took about 4 minutes to load, and the first thing I noticed? Two colums for downloading. The first one says "AGPL3 Only" and the second says "incl. 3 users Outlook support".

      Common--you know that that means. "We open sourced part of our software to try and suck you in--but you'll really find it limited until you fork over slightly less that you would have with Microsoft Exchange."

      --
      There's no place like ::1 (I've completed my transition to IPv6)
    3. Re:Hell yeah by mhall119 · · Score: 4, Informative

      That's exactly what they did: http://www.zarafa.com/content/versions

      --
      http://www.mhall119.com
    4. Re:Hell yeah by Anonymous Coward · · Score: 3, Informative

      This looks like cripleware to me. The "open source" version is limited to 3 outlook clients. That doesn't sound very open!

      (posting as AC because karma system sux).

    5. Re:Hell yeah by wisty · · Score: 3, Funny

      Globally find and replace '3' with '9999999'. What could possibly go wrong?

    6. Re:Hell yeah by Svartalf · · Score: 2, Informative

      If the source IS available under the GPL, one can correct it and provide a much more capable version, no?

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    7. Re:Hell yeah by Dolda2000 · · Score: 2, Insightful
      I don't see how they can do that. If the source is open, how could it possibly even be hard to remove that limit?

      That being said, though, I would guess that the greatest contribution isn't actually the program itself, but rather the fact that it lays open the protocols involved, so that other MAPI servers could be written. Maybe it could even be implemented as another protocol for Dovecot?

    8. Re:Hell yeah by miro+f · · Score: 5, Funny

      #define PI 9999999.14159265

      --
      being vague is almost as cool as doing that other thing...
    9. Re:Hell yeah by julesh · · Score: 2, Interesting

      If the source IS available under the GPL, one can correct it and provide a much more capable version, no?

      Given my experience with past "open source exchange replacements" (e.g. OpenExchange, HP OpenMail) you need an MAPI driver as a plugin to Outlook to enable the advanced features, and that part usually is not open source.

  2. Aren't there others like this? by jd · · Score: 4, Interesting

    I seem to remember ogo being a full replacement and that's been out for a while. Also, although you want to provide compatibility with Exchange, don't you want to provide additional capabilities so that Exchange systems are forced to upgrade to you, rather than the other way round? (Embrace-and-extend, but non-toxic.)

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Aren't there others like this? by gclef · · Score: 2, Informative

      Citadel also tries to be a full-featured e-mail/calendaring/task management/etc system.

    2. Re:Aren't there others like this? by Nom+du+Keyboard · · Score: 2, Insightful

      don't you want to provide additional capabilities so that Exchange systems are forced to upgrade to you,

      Actually you want to provide additional capacities so that going back to Exchange is a true downgrade.

      --
      "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
    3. Re:Aren't there others like this? by Eric+Smith · · Score: 4, Insightful

      Sure, but there's a lot of difference between offering a similar feature set, and being a drop-in replacement that is compatible with all the crufty MS protocols.

    4. Re:Aren't there others like this? by fishbowl · · Score: 5, Funny

      >[A]n open source alternative to Exchange would not have Exchange's arbitrary limitations

      Oops... if it's not bug-for-bug compatible, it's going to be a problem with some PHB.

      --
      -fb Everything not expressly forbidden is now mandatory.
    5. Re:Aren't there others like this? by hairyfeet · · Score: 5, Informative

      Xandros with Scalix also works as a drop in,with the added bonus of being able to be either a member or a domain controller in an AD forest. Really nice if you need to support a mixed environment. But as always this is my 02c,YMMV

      --
      ACs don't waste your time replying, your posts are never seen by me.
    6. Re:Aren't there others like this? by theshowmecanuck · · Score: 5, Insightful

      Jesus H. Fucking Christ. 99.9999999% of all companies just want to buy a tool that works. They don't want to build the fucking thing. They don't even want to fix it. That's why they buy the support license. This whole 'we can customize the code if we want' is a huge stinking load of specious crap. Companies of any size BUY their software because they don't want to customize software they don't have to. Like office software. Customizing a huge billing system is one thing (if you are a big enough company to warrant doing that), but why would an insurance company, or a local widget maker, or a medical clinic want to become an email server programming company???? Get a grip. They'll go out and buy exchange or lotus notes or whatever because they just want the frickin tool. And if it is buggy so what? It works for the most part and they don't have hire programmers or keep programmers around to fix bugs that said programmers introduced when they screwed around with the source code. It's cheaper to pay for the licence for a year than to pay for an unneeded programmer for a year.

      --
      -- I ignore anonymous replies to my comments and postings.
    7. Re:Aren't there others like this? by theshowmecanuck · · Score: 5, Funny

      OK ... I'm better now.

      --
      -- I ignore anonymous replies to my comments and postings.
    8. Re:Aren't there others like this? by DittoBox · · Score: 2, Interesting

      As a user I understand that most of the proprietary crap that MS dishes out for protocols is indeed "cruft" (Most slashdotter's could shit better protocols in their sleep). I've experienced more bizarre behavior than I care to admit, but what are some technical or design examples that could be cited as to why most of their protocols (exchange in particular) are so bad? I know their implementation of IMAP is very poor, I think it has to do with various connection and sync commands not being fully or at all implemented which can cause all sorts of weirdness on the client end and lost mail on the server.

      --
      Good. Cheap. Fast. Pick Two.
    9. Re:Aren't there others like this? by mistermocha · · Score: 5, Interesting

      Well, there are some of us who work at mom & pop software shops that do have a clatch of intelligent developers on site but don't have a huge budget to buy an email solution.... and we're a lot more than 0.0000001% of all companies.

    10. Re:Aren't there others like this? by jd · · Score: 3, Insightful

      Well, project maintainers tend to be very lazy when it comes to things like Freshmeat, which is why I maintain something like 120 project records and semi-regularly update 50+ others that I've subscribed to. (I should be paid full-time by Sourceforge or someone for the level of work I put in. Yeah, right.) If project maintainers were, oh, a little more forthcoming and not hiding releases, we'd all be a damn sight better off. Google should be a good source, but the problem there is that it's so hard to search for anything where all your keywords are common words. There's no good, juicy, unambiguous keyword to use, and search engines just aren't any good at semantics. They're only useful for syntax-based searches. The FSF's software page is excellent for projects the FSF knows about and is associated with in some way (even if just as an umbrella or as a webpage host), but you'd not get much done if you only used software they linked to. A pity, but they can't do everything, though they do try to do exactly that. Sourceforge's search engine seems to turn up everything Sourceforge hosts, and there are a million and one Sourceforge-like sites these days. Getting information, therefore, depends massively on volunteers trawling every imaginable report, rumour and hint of Open Source and indexing it somewhere. And there just aren't anything like enough volunteers to make anything close to a dent in what's out there. Which is a real problem, as projects that nobody knows about WILL die. Even when something IS known about, if updates aren't announced in a meaningful way, it will also die. Likewise, if people don't contribute, the project will die. Or if the maintainer doesn't release early and often, the project will die. And even after all that, if it's not in any of the major distributions, there won't be a sustainable userbase or a large enough supply of bug reports and the project will die. In this case, I think most of the above apply.

      --
      It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    11. Re:Aren't there others like this? by gbjbaanb · · Score: 3, Insightful

      there are a lot more copmpanies out there that barely know what a PC is. Software houses are a tiny minority compared to retailers, to name one. Think how many back office staff exist to serve them compare to the number of programmers. Then go to the next class of business, repeat a thousand times.

      I'd say 0.0000001% is a bit of an exaggeration, 0.1% is more like it.

    12. Re:Aren't there others like this? by Eric+Smith · · Score: 5, Insightful
      The MS protocols tend to be crufty because they are developed in secret, don't get any public review, and are allowed to evolve in a completely ad-hoc manner.

      That's not to say that all protocols developed by open processes are wonderful, but on average they seem to be better.

    13. Re:Aren't there others like this? by that+this+is+not+und · · Score: 5, Insightful

      The MS protocols are crufty because the direction of the design of them is left up to middle managers.

      That should explain it fully to anybody curious.

    14. Re:Aren't there others like this? by Metaphorically · · Score: 4, Funny

      Point of order: I'd like to believe that most slashdotters don't shit in their sleep. Or if they do, I'd like to never ever think about it again.

      --
      more of the same on Twitter.
    15. Re:Aren't there others like this? by vawarayer · · Score: 5, Interesting

      That's a nice long explanatory answer... for the first question! ;). Do you have an answer for the 2nd?

      I might even add... do you have suggestions?

      I have already checked out a few of 'em (not necessarily OSS):

      ...of which many of them have a great potential, but I always end up having some trouble somewhere or find 'em not user-friendly/admin-friendly enough.

    16. Re:Aren't there others like this? by sweet_petunias_full_ · · Score: 4, Insightful

      "...they can finally have something that works!"

      Hear, hear. And maybe they can finally have something that doesn't try to break protocol standards, introduce a non-interchangeable mail archival format, artificially create a need to have ten times as many server licenses as necessary... in short, businesses would do well to uh, swap it for something else.

      --
      You can't send a takedown notice to an already printed newspaper.
    17. Re:Aren't there others like this? by RAMMS+EIN · · Score: 3, Insightful

      ``Jesus H. Fucking Christ. 99.9999999% of all companies just want to buy a tool that works.''

      You are right about that (well, maybe not about the percentage, but the general point), but that doesn't contradict anything I said. They _would_ rather buy something that Just Works. They _would_ rather spend money on software licenses than spend more money on developing their own software. And all this makes perfect sense.

      ``They don't want to build the fucking thing. They don't even want to fix it. That's why they buy the support license. This whole 'we can customize the code if we want' is a huge stinking load of specious crap.''

      Now, I don't know where that comes from. Who said anything about having to "build the fucking thing"? Did you miss the part where Zarafa is called a "drop-in replacement for Exchange" and "binaries ... are available"? You don't have to build anything, and you don't have to fix anything. You seem to have confused what you _can_ do with what you _must_ do. Having to fix something is a Bad Thing. Being able to fix something is a Good Thing.

      The comparison is like this:

      On the one hand, you have Microsoft Exchange. There are various versions, each with their own bugs and limitations. If you need those bugs and limitations removed, you might be able to buy a different version, you might have to wait for a newer version to become available, or you might be simply out of luck. You pay for the software itself, and for client licenses - the more people use the software, the more you pay.

      On the other hand, there is Zarafa. There will be various versions, each with their own bugs and limitations. If you need those bugs and limitations removed, you might be able to obtain a different version, you could wait for a newer version to become available (possibly with a patch from some company in the same position as you), or you could remove the bugs and limitations yourself. You can get everything for free.

      Now, you tell me which seems to be the more attractive option.

      Finally, I would like to point out that open source software tends to get easy installation procedures and low maintenance cost once Linux distributions start packaging it. Also, if running a particular piece of software is too tedious for you, you can always get it hosted by someone else. There is Exchange server hosting, and I imagine there will be Zarafa server hosting, as well.

      --
      Please correct me if I got my facts wrong.
    18. Re:Aren't there others like this? by jimicus · · Score: 4, Interesting

      There are plenty, but most seem to miss the point of Exchange in some fashion.

      Point the First: Everything that you're likely to plug into Exchange must also work with whatever alternative or it isn't an Exchange alternative. That means things like Blackberries, other vendors' smartphones, seamless (yes seamless, not "install this plugin which sort-of works") Outlook integration, remote management of smartphones (including wiping them). Zimbra's pretty close here, but falls down on remote smartphone management and seamless Outlook integration.

      Point the Second (Scalix falls down here): Exchange is only a small proportion of the overall licensing costs. You've also got Active Directory (which implies a Windows Server infrastructure) and CALs for AD. There's not a lot of point in having AD without having your workstations on an AD domain, so you've got to factor in all the necessary licenses for this as well. If you demand I supply my own AD infrastructure and you price your product at [price for Exchange - 10%], I might as well just pay the extra 10% and eliminate the risk of being passed between vendors in a game of telephone tennis in the event of support issues.

      Point the Third: Whether you like it or not, the PHBs who like Exchange are often rather stuck in the Exchange way of thinking. I don't care how much better you think your solution is, if your argument is "it's cheaper but it's only better if you're prepared to accept a totally new way of thinking about groupware" then it's not better because the PHBs in question probably aren't. Citadel's a good example of this.

    19. Re:Aren't there others like this? by julesh · · Score: 2, Informative

      Xandros with Scalix also works as a drop in

      Except to get full features on Outlook, you need their MAPI Connector, which requires you to pay for "premium user" licenses.

    20. Re:Aren't there others like this? by hairyfeet · · Score: 2, Informative

      Which if you check the prices of licenses compared to Exchange is a WHOLE lot cheaper.(Disclaimer-I don't work for Xandros,I just enjoy the ease of use). Look,Xandros+Scalix isn't meant for Linux gurus that are the masters of the CLI game,it is designed for businesses that have primarily Windows admins and need something that just works,or for those that have to support a mixed environment.

      Thanks to a plugin you can manage your Xandros server from either your Windows server or your admin desktop,the Xandros XMC is so identical to the MMC that it takes almost no retraining at all to switch your Windows admins over,and with of 60 roles already to go with nice wizards it takes the CLI and guesswork out of setup and maintaining the server. I believe in the right tool for the job,and for the average SMB,or for those that don't have Linux admins on staff,Xandros takes a lot of the hair pulling out of switching. It even has both Xen and Vmware support built into the kernel so you can get virtual servers up and running in no time at all.

      They have a free 90 day trial on their website so if you have space for a VM or an old server sitting around unused why don't you give it a try and decide for yourself? That is always better than taking someone else's word for it anyway. And as always this is my 02c,YMMV

      --
      ACs don't waste your time replying, your posts are never seen by me.
  3. Hm, if this works as advertised by pembo13 · · Score: 5, Informative

    They better start hiring support personnel, because there will likely be profits to be had with service contracts. Maybe even a Redhat buyout/partnership

    Over the last few months, I've been forced to use Exchange/Outlook a lot, and for the life of me I don't get the big deal. But I know that people consider it a big deal, so I wish this company the best, and fair

    amount of profit.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
    1. Re:Hm, if this works as advertised by nine-times · · Score: 4, Insightful

      Over the last few months, I've been forced to use Exchange/Outlook a lot, and for the life of me I don't get the big deal.

      I don't think it is a very big deal. I've supported Exchange servers in companies of various size, and it's really not doing anything astoundingly complicated, and what it does it doesn't do all that well. But still it does a bunch of things that other solutions haven't done an even worse job at, and does them all together. Things like "I can send a meeting invitation to my boss and his assistant can check his mail, accept his invitation, and reply on his behalf without actually logging in as him."

      I know, it doesn't sound like that sort of thing would be all that important, and it's not even clear all the time that it makes a lot of sense, but there are companies that run on this sort of procedure. So there are a bunch of random things like shared calendars and push-email to phones that people don't want to live without, and unless you can provide a seamless replacement, you're stuck with Exchange.

      I, for one, am eager to see a suitable Exchange alternative. I have a real love/hate relationship with Exchange. There are some options out there, but none of the options I've tried have worked out.

    2. Re:Hm, if this works as advertised by xouumalperxe · · Score: 4, Interesting

      I know, it doesn't sound like that sort of thing would be all that important, and it's not even clear all the time that it makes a lot of sense, but there are companies that run on this sort of procedure.

      Hell, I read what you described and thought "damn, that's a really good idea, hope it's also a well thought out and implemented feature". The idea that I can easily give you permission to act on my behalf is probably the single best way to kill account promiscuity. Plus the example you gave is also a damned practical one too, and a good way to prove that this is a feature, and not a solution looking for a problem.

      So there are a bunch of random things like shared calendars and push-email to phones that people don't want to live without, and unless you can provide a seamless replacement, you're stuck with Exchange.

      In other news, when a piece of software is truly convenient, you use it, even if it's not perfect.

    3. Re:Hm, if this works as advertised by noc007 · · Score: 5, Informative

      To answer your question, IMHO the big deal is collaboration, productivity, integration, and a lot of features "just work"*. I'd wager to say that the majority of medium to large companies use MS Office and MS Outlook as their productivity suite and e-mail client respectively of choice.

      Collaboration
      Setting up meeting requests are simple. I can easily see other people's calendars so I can pick the best time and I can even set a meeting location which will automatically reserve something like the meeting room for example. Meetings automatically get put on my calendar as tentative and I'll receive a notification in case I forget to accept the invitation. Updated meeting change my calendar as well without intervention.

      Productivity
      I can set reminders, flag e-mails for follow-ups, create folders to organize, create processing rules to eliminate common tasks. A lot of rules will run on the Exchange server without the need of a client running and I don't get unnecessary e-mails on my phone. Outlook maintains a constant connection with Exchange so e-mails are sent and received nearly instantly.

      Integration and crap just working
      Obviously most MS products can seamlessly integrate well with one another. In the latest version of Outlook I can preview a number of attachments within Outlook without actually opening them up in their designated app, thus a new window. I can set a folder to actually open up a webpage within Outlook to "Integrate" a webapp or just be sly on reading Slashdot.

      Phone integration really is a big one for me. Using a WM5, WM6, or iPhone with Exchange ActiveSync is almost the best thing since sliced bread. I remember the days of having a PDA and the PITA it was to do a hard-reset or get a new one. Even getting a new phone and having to manually enter in each contact sucked (I've been a CDMA whore for eight years). All my contacts are kept on Exchange and this allows me to reference and edit them via the phone or Outlook. Having to do a hard-reset or get a new WM phone is no big deal; a three minute sync with Exchange over the air gets me all my contacts back and access to my e-mail. The rare third party apps I use are kept on an SD card. Life is easy getting the execs and lusers up and running as well.

      Integration with Active Directory (LDAP) makes my life as an admin easier with GPOs and groups to divvy out permissions. And for some reason all this stuff works without much hassle.

      The bad
      Exchange and Outlook truly do have their faults. If I were to have my own company, I can't honestly say that I would run them. I wont get too far into the bad since I'm running out of time with the wife waiting on me. If I were to have my own company, I can't honestly say that I would run them. Exchange works great with communication within itself and other Exchange servers. It does a decent job at SMTP transmissions most of the time. The big headache I have right now stems from a tech at MS telling me that "the RFCs for the SMTP protocol are merely suggestions." It's not like SMTP is overly complex; there are only a handful of commands that are exchanged within SMTP communication and Exchange even F's that up. And don't get me started with how Outlook is written in VB.

      I'm glad to see some open source Exchange clones out there. I'll eventually run one of them for my server at home just so I can keep my contacts synced when I leave my current company.

      To put things into perspective, I'm not a MS fanboy, but I'm not a MS hater either. I know their products well and is a part of my profession. My real passion is UNIX; specifically FreeBSD and OpenBSD. I try to introduce them where possible and applicable. Not to mention there is some stuff I can get done easier and faster with UNIX than I could with MS Windows. Other products out there are just as buggy and bloated as MS's; they just get more attention since they're more widely used.

      I hope that Zarafa and others continue to innovate and make a nice profit. Competition is good for innovation and lowering prices; both of which benefits us consumers.

      * Setup can be a RPITA. When something doesn't work as expected it can be an easy fix or cause suicide.

    4. Re:Hm, if this works as advertised by gander666 · · Score: 5, Insightful

      Well, the reality is that senior executives have always had personal assistants (used to be secretaries) who really opened all their mail, sorted it, and typed responses to the mundane, and took dictation for the serious ones.

      The executives typically have 100% trust in their admin's and this feature is absolutely necessary to the proper functioning of a senior management team. It may seem like a security risk, but in the cases that I am aware of, both users are aware of their status, and it rally operates like it did in the pen and paper days.

      --
      Suppose you were an idiot and suppose you were a member of Congress ... but I repeat myself. - Mark T
    5. Re:Hm, if this works as advertised by Martin+Blank · · Score: 4, Informative

      Messages sent by the assistant have a clear "Bob accepted on behalf of Alice" kind of structure. The logs also show that it was Bob accepting on behalf of Alice, IIRC. This is useful not only for the tracking perspective, but also so that the recipient knows that it was not necessarily directly handled by the person invited.

      --
      You can never go home again... but I guess you can shop there.
    6. Re:Hm, if this works as advertised by funkatron · · Score: 5, Insightful

      Having others able to act on your behalf without using your login simplifies the process of proving that you did/didn't actually do something. The information about who logged in and did what on whose behalf can easily be logged. If, on the other hand, you have a system where your login has to be used to act on your behalf then the logs can only show your username no matter who actually used your account.

      --
      "Welcome to our world. We are the wasted youth. And we are the future too." Yes, I know these are stupid lyrics.
    7. Re:Hm, if this works as advertised by Kaboom13 · · Score: 3, Insightful

      You have to have an account specifically granted the privilege to do what he is describing, and you can place restrictions on what they can do. In his example, the secretary has the authority to say "my boss will attend this meeting", and that authority translates to his electronic calendar, the same way it would in real life. Sure his secretary could have a breakdown and screw up his schedule, but she could do that anyways just by not doing her job, and how many office environments have you seen where the secretary didn't frequently have physical access to her boss's machine while it was logged in?

    8. Re:Hm, if this works as advertised by DragonWriter · · Score: 5, Insightful

      If others can act on your behalf without actually logging in as you, what proof is there that e-mails allegedly sent by you were actually sent by you?

      If others can be delegated permissions to act on your behalf in specifically designated manners without logging in to your account, then, if the system logs who did what under what account, there will be accountability.

      OTOH, if others can't act on your behalf without logging in as you, and you have a business need them to act on your behalf, you have no choice but to give them your access credentials (dongle, password, whatever) and then there really is no accountability, and no control over the manner in which they can act on your behalf.

      So, rather than destroying accountability, supporting delegation enhances accountability (and security).

    9. Re:Hm, if this works as advertised by mikiN · · Score: 4, Funny

      iPhone...Activesync...in one sentence? Related? Actually...working together?

      I'm sorry guys, but my head is spinning...gonna get me a Tylenol...quickly.
      Isn't it so that 'iPhone' goes with 'Apple' and 'Activesync' goes with Microsoft?

      Next they're going to tell me that you can run Windows XP on a MacBook. Oh well...

      --
      The Hacker's Guide To The Kernel: Don't panic()!
    10. Re:Hm, if this works as advertised by Scaba · · Score: 2, Funny

      Indeed! There's been a recent string of incidents reported of rogue, black-hat office admins maliciously filling their bosses' calendars with meetings HE NEVER AUTHORIZED, yet was forced to appear at, even if no one else was there! And some execs were reprimanded - even dismissed - because they couldn't provide sufficient evidence that they were not the person who authorized such meetings. It chills the spine to think of how much executive time is being wasted through an easily patched exploit such as this, and of how many lives are thrown into chaos in the aftermath.

  4. Re:EAT SHIT FAGGOTS!! by oahazmatt · · Score: 5, Funny

    Linux is for the garbage can!

    Sweet! What won't Linux run on these days?

    --
    Those who believe the Internet is private,
    find their privates are on the Internet.
  5. Re:EAT SHIT FAGGOTS!! by uassholes · · Score: 3, Funny

    If I had some mod points I would give you one for funny. Ignorant, but funny.

  6. Woohoo! by AmonTheMetalhead · · Score: 3, Informative

    Well, that's certainly nice, push-mail, activesync, mapi, all the things people like about Exchange in an open source variant, why the hell not?

    I've been running OpenGroupware myself as a cheap replacement for Exchange (using funambol to replace ActiveSync) and it works nicely, but the more alternatives to Exchange the better!

    I've yet to try this one, i hope it's atleast as "easy" to manage as an Exchange server tho, if you need 10 Rocket Scientists to install it, then open sourcing it won't make it magicly defeat Exchange, and sometimes i get the impression people tend to forget other people use their applications too.

    In short, the more the merrier! Long live FOSS!

    1. Re:Woohoo! by dbIII · · Score: 2, Informative

      i hope it's atleast as "easy" to manage as an Exchange server tho

      I shouldn't have read that one while drinking coffee.

      Inexperienced admins think MS Exchange is easy because they don't have disaster recovery plans and they do not test them. The problem of needing another licence just to be able to effectively learn this is one thing that keeps them inexperienced, as is a lack of exposure to other systems that manage email effectively. Now MS Exchange does all kinds of other odd things as well as running email which makes it just about the only thing of it's kind, but if you compare it to purpose built email systems it is a difficult beast to wrangle. Want a company wide email disclaimer to go on messages? It's just an easy hack of the registry but how on earth is somebody going to find it later without incredibly good documentation? Proper backups that will actually work without shutting down the entire system are now possible in MS Exchange but it should have had it from day one!

  7. not vetted/tried and true by Anonymous Coward · · Score: 4, Insightful

    I've not looked at this software, but Exchange is one hell of a piece of machinery. Say what you want about MS, but I've seen an Exchange server with terabytes of email, gigabytes per day, keeping up fine. It's a pain in the ass sometimes to be sure, but I wouldn't trust my production network to this today anyway.

    1. Re:not vetted/tried and true by Just+Some+Guy · · Score: 4, Insightful

      Say what you want about MS, but I've seen an Exchange server with terabytes of email, gigabytes per day, keeping up fine.

      BS. I've seen Exchange servers with gigabytes of mail and megabytes per day roll over and cry until we put a FreeBSD/Postfix/Amavis/ClamAV server in front to lighten the workload by 95%. If this is built on top of FOSS components, I don't doubt for a second that it'll run rings around Exchange.

      Exchange has traditionally had exactly one reason for its popularity: vendor lock-in. If this really is a drop-in replacement without annoying CALs, we'll be Microsoft-free on our servers by Monday.

      --
      Dewey, what part of this looks like authorities should be involved?
    2. Re:not vetted/tried and true by Just+Some+Guy · · Score: 2, Informative

      Exactly. And I'd much trust something like Cyrus IMAP over Exchange for data integrity any day of the week.

      --
      Dewey, what part of this looks like authorities should be involved?
    3. Re:not vetted/tried and true by OrangeTide · · Score: 3, Interesting

      after working the storage industry I have come to the conclusion that exchange is not very effective at handling heavy email load or large message database. How many of us get annoying emails when we have more than a few hundred MB of messages in our mailbox? Did you know that Exchange performs like crap when you run low on local disk space to keep the data. CIFS won't save your ass either, you end up having to go to using SAN (which looks like local disk from Exchange's point of view).

      Some bullshit scripts with postfix, exim or qmail can spool and forward terabytes of email an hour. With the added advantage that you can cluster your IMAP services out to deal with the space and load in an incredibly simple yet scalable manner. You can use a SAN, but you can just as easily setup a new box for every 100 employees and still have a very usable system.

      Exchange is inflexible and can only scale if you use on particular (and very expensive) setup. Microsoft only focuses on the operating modes of Exchange server that they use at corporate HQ. The inferior modes are just there so they can sucker companies into buying it at the low end, when in a short while the company will have to invest an exponential rate of money to scale the system.

      The TCO of Exchange is very high. And Microsoft's way is not the only way to manage messages, events, meetings and users.

      --
      “Common sense is not so common.” — Voltaire
    4. Re:not vetted/tried and true by LibertineR · · Score: 4, Insightful
      Sorry, that is just bullshit.

      Exchange inflexible?

      What do you say to the Hundreds of Thousands of clients who get their Exchange via SBS (Small Business Server)? And that's just the 2003 version.

      How many Enterprise apps do you know of by ANY vendor that dont degrade with low disk space? Come on, dude, that aint fair and you know it.

      Exchange is one of those apps that can look bad if installed by an idiot. You would think a proper architect would have worked out space and usage requirements early on.

      How do you reach a low space condition ANYWAY, if you are making proper use of quotas? No product takes more abuse due to stupid administration than Exchange server.

      But please, inflexible? When you have dozens of 100K+ client installations of Exchange humming along at places like Chevron and others, while the very same product can keep 20 people happy on a $500 box, you cant call it inflexible. Thats just wrong, pal.

    5. Re:not vetted/tried and true by wasabii · · Score: 3, Informative

      Exchange does not use PSTs. Migrating off Exchange is fine. You canc onnect to Exchange with IMAP and dump data. Just like you can with every other open source server. Problem is that Exchange has features which these other servers do not, and thus it's not really going to work out: Calendars/Contacts. And yes. I do juggle backups, patches, etc. I run Exchange on a set of clustered boxes sharing storage. I can fail over a machine, patch one, and bring it back up. Pretty freaking easy. I honestly never touch the thing except to apply patches. Once every 6 months. Ever tried to migrate a user's mailbox from one site to another? One button. It moves it on it's own. Authentication is integrated into AD. One password. All communication uses Kerberos. It's lovely.

    6. Re:not vetted/tried and true by GoodNicksAreTaken · · Score: 2, Informative

      I've seen dozens and the only ones that have that kind of load and keep up without tons of maintenance are ones that are running as POP and not true Exchange servers.

    7. Re:not vetted/tried and true by OrangeTide · · Score: 3, Insightful

      You are limited in the amount of diskspace you can put in a server without switching to a SAN. There are only two useful configurations for Exchange in this respect (and they are identical in configuration, just different in cost). Quotas don't solve the problem if they are too small or you hire more people than you expected (merges for instance).

      Exim, postfix, qmail, sendmail, etc are capable of operating when you have low disk space because you can give it more diskspace by either moving parts of your mail server into a cluster (exchange does not do this in a way that is easy or transparent). or you can use an inexpensive NAS to provide the additional spool space without horrible performance issues. Exchange really can't use NAS in a useful way, you are stuck jumping directly to SAN.

      The lack of options for configuration is why I call it inflexible. It's a reasonable usage of the word "inflexible".

      Now you might use Exchange anyways because of the other features it offers that are not available in other products. And it might be flexible in ways other than scalability. Also, I'm not saying that anyone should use my evaluation as a complete coverage of all the issues used to make these sorts of decisions. I only want to point out that for cost and flexible scalability, Exchange is not the top dog.

      When you have dozens of 100K+ client installations of Exchange humming along at places like Chevron and others, while the very same product can keep 20 people happy on a $500 box, you cant call it inflexible

      That's essentially my point. Exchange offers no middle ground. You either have a crappy small office mail server on a spare Windows box, or you have an enterprise environment with SAN. Perhaps it's just evil to change your messaging infrastructure in mid-step, but companies grow.

      I think I would recommend that everyone just start with a standard SMTP/IMAP solution, hire a Unix admin if you have to. And hold off on switching over to Exchange until they can afford a SAN.

      --
      “Common sense is not so common.” — Voltaire
    8. Re:not vetted/tried and true by rickb928 · · Score: 2, Interesting

      ...which is why I turn down admin/AD/Windows consulting jobs. I'm tired of being the angel of death, declaring death and data loss, due to past decisions and previous admins/mercenaries who did bad things.

      Yeah, I hear ya. After 17 years, I finally told my boss it wasn't worth it. He really didn't understand. Then again, he never really understood what we did.

      I do miss GroupWise, though. It just plain worked. But that's another story...

      --
      deleting the extra space after periods so i can stay relevant, yeah.
    9. Re:not vetted/tried and true by LibertineR · · Score: 4, Insightful
      So tell me; did you present your management with a cost/benefit analysis, supporting your request for additional hardware? Did you point out what a catastrophic failure of the Exchange infrastructure would cost them in lost man-hours and productivity? If everyone in your company is getting "mailbox -full" notices, it would seem to me an easy argument to make in DOLLARS, as to the amount of time spent by staff just to find items to delete each week. Am I wrong?

      Have you looked into tools like GFI's Mail Archiver or the Mimosa tools to get you some disk space back, and bump up overall performance?

      See, it is very easy to just say, "management sucks, exchange sucks, yada, yada", but until or unless you have done all you can do to make your case, I repeat: IN DOLLARS, you have to bear some responsibility. This is what is wrong with IT these days. I'm guessing you didnt do a cost analysis, and you would not be alone in that regard, but someday, IT folks are going to have to prove that we are REAL professionals, or management has no good reason to pay any attention to us. IT is not just about technology, you have to sometimes be a teacher and a salesman to be effective, even when Management makes you not want to really give a shit.

      Personally, if you had done what I suggested, and gotten the response you described, were I you, I would have walked out of there, before I let anyone put my name on a fucked up server.

      But, that's me. (climbing down from my soapbox)

    10. Re:not vetted/tried and true by LibertineR · · Score: 2, Interesting
      True, but Microsoft bares some blame too (GASP). Initially, Microsoft marketed their tools as easier to maintain than the competition, which was true up to a point. However, beyond a 30 person shop, it is a good idea to have someone on staff who really knows what they are doing, not just the CEO's nephew who likes to tinker with shit.

      Microsoft is also to blame for the ease of passing the MCSE exams, resulting in a lot of people thinking they knew a lot more then they really did. A guy shows up with his shiny certification, and proceeds to fuck up your servers, and then it is EASY to blame the software, rather than the "genius" with the cert.

    11. Re:not vetted/tried and true by WhiteHorse-The+Origi · · Score: 3, Informative

      I disagree! With just a few simple apps you can do everything exchange does and more.
      Email-Postfix
      Calendar-iCal + LDAP
      Meeting requests-iCal
      Tasks-iCal
      Synchronization-Webdav or SyncML
      Publishing Calendars-Webdav(Caldav) or SyncML
      Sharing/Editing the same calendar-Webdav(GroupDav) or SyncML
      Webmail-Many choices, some with calendars, AJAX, etc
      Blackberry-Funambol, SyncML I mean seriously, what else do you need? Encryption? Got it. There are tons of more features with clients like Evolution and Thunderbird including desktop integration.

  8. GPL'd community edition has limited MAPI clients? by Anonymous Coward · · Score: 5, Informative

    Last time I looked on the Zarafa website, it looked like the free community (GPL) edition had a limited number of MAPI clients. I guess this is still the case? If so, it's not really a practical replacement for Exchange unless you pay for the commercial edition.

  9. If it works as advertised... by pak9rabid · · Score: 3, Insightful

    ..I'll DEFINATELY be installing this for our company's mail server. I currently have Zimbra setup, which is very nice, but the bosses don't like it because it doesn't integrate into Outlook very well (iCalendar, contacts, etc), without the outlook connector that you have to pay for. No hate on Zimbra though...I absolutely love it's capabilities and ease-of-use, but it's a deal-breaker w/the management types if won't support the 'advanced' features in Outlook.

    1. Re:If it works as advertised... by JohnFluxx · · Score: 5, Funny

      DEFINITELY

      (If you're gonna write a word in all caps, spell it right :-) )

    2. Re:If it works as advertised... by ColaMan · · Score: 3, Funny

      Aha, but it's not in ALL CAPS, is it?

      --

      You are in a twisty maze of processor lines, all alike.
      There is a lot of hype here.
  10. Re:GPL'd community edition has limited MAPI client by Hatta · · Score: 3, Insightful

    The nice thing about GPL software is that it's easy to go in and change arbitrary limitations like that.

    --
    Give me Classic Slashdot or give me death!
  11. Patent encumbered? by timotten · · Score: 4, Interesting

    I did a quick test with this product a few weeks ago, and it sync'd well with my phone. My only concern was that Microsoft appears to assert patent claims relating to ActiveSync. Anyone have thoughts or experiences on using this product in the US market?

  12. "successful" is ambigous by bogaboga · · Score: 4, Insightful

    ...Zarafa decided to put their successful Exchange server replacement under GPLv3. This is not just the typical mail-server-that-works-with-Outlook, it is the whole package including 100% MAPI, web access, tasks, iCal and Activesync...

    While I hail this development, I wonder what "successful" means in this story. Here are questions I might want answered:

    Was it "successful" at sales? If so where are the figures? I would not really praise them that much if the original goal - to make money, could not be reached making these fellas to opensource everything...much like what Netscape did years ago.

    Was it "successful" at actually replacing Exchange with no [significant] trouble for Systems Administrators? I need to know. How come it is not that known in IT circles? What's going on?

    1. Re:"successful" is ambigous by shaitand · · Score: 2, Interesting

      'Was it "successful" at actually replacing Exchange with no [significant] trouble for Systems Administrators? I need to know. How come it is not that known in IT circles? What's going on?'

      Probably because there are six to a dozen functional drop in replacements for exchange on the market that work fine. None of them are free as in beer or free as in speech though. Or if they are, they require an 'outlook connector' that is not.

    2. Re:"successful" is ambigous by Joe+Enduser · · Score: 4, Insightful

      Let me enlighten you a bit on the "success" factor for the sysadmin. I implemented this at a very small organization. While it does integrate nicely with Outlook, and handles the calendar and contacts stuff very nicely, it is the first time I am trying to manage a mailserver which blatantly has dropped mail regularly and silently, at least in a previous version. In the current stable version, an imap client cannot delete a mail from any folder. This is fun when a client does not actually move mails between folders or the trash, but copies first and then deletes, such as Apple Mail. Also, an update of the server version to a new main version, i.e. from 5.xx to 6.xx does not only involve a new version of the Outlook plugin on the clients, but also mandates a new user profile in Outlook. That is a lot of work. I hope that opensourcing this stuff eventually makes it more maintainable, but I have not been able to find out about access to the actual source repositories which might enable actual collaboration on the product.

  13. In other news . . . by UnknowingFool · · Score: 4, Funny

    Office Depot, Office Max, and Staples reported a shortage of office chairs in the supply chain. When asked, representatives were unsure to the exact nature of the shortage.

    "According to our suppliers, someone in Redmond, Washington has decided to corner the market on office chairs," one company spokesman said.

    ----------BREAKING NEWS-----------

    This just in! According to NORAD, the nation's defense system went on alert after controllers detected a large number of unknown flying objects coming from the Pacific Northwest. While the status has not entered DEFCON 1, a spokesman for the Defense Department assured the public that this was a precautionary measure as the objects themselves do not appear to be very large and that they originated from the Northwest rules out an nuclear attack from either China or the former Soviet Union.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  14. Also by Icarus1919 · · Score: 3, Funny

    can be measured to be 1050 dog-years of work.

  15. Sounds Great for SMB by joelleo · · Score: 2, Interesting

    Big things missing though - No public folders, which allow automated, customized workflow processes, no single instance store (each attachment is a separate file within the message store,) limited support (enterprise class support 24x7 is > 15,000 euros and their business hours aren't conducive to US business support - GMT+1) and it runs on linux instead of bsd *grin*

    With that being said, I can see where a LOT of businesses will be able to make extensive use of this. Best of luck to them!

    --
    "In the end, there is simply no weapon more devastating than the truth, delivered in just the right way." - tnk1
  16. Re:EAT SHIT FAGGOTS!! by _Sprocket_ · · Score: 4, Funny

    Can you imagine a Beowolf cluster of those? Take THAT, big iron.

  17. Re:In other news . . .MOD PARENT UP! by Nom+du+Keyboard · · Score: 2, Informative

    Parent was obviously modded down by some newbie to moderation who didn't get the joke, doesn't understand throwing chairs in Redmond, and modded it off-topic because he didn't understand it. This is a lousy excuse for moderation!

    --
    "It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
  18. Re:EAT SHIT HOMOPHOBES!! by roaddemon · · Score: 4, Funny

    Only because the people with Linux experience and the people with condom experience are disjoint sets.

  19. Oh, not this shit again? Come on.... by LibertineR · · Score: 4, Informative
    Quotas anyone? OWA?

    Drop in replacement, you say? Will MOSS or CRM play with it? Will it pick up AD rules and GPOs? What about BCM and Project Server?

    OR, is it just another glorified POP/IMAP box?

    I read the feature set from the web site.

    I know Exchange, I was in the original product group way back when. This AINT no DROP IN REPLACEMENT.

    That said, for what it does, good for them!

    But people should watch their words. Side by side against Exchange 2007, it would not be a fair fight.

    1. Re:Oh, not this shit again? Come on.... by shaitand · · Score: 2, Funny

      'OWA?

      Drop in replacement, you say? Will MOSS or CRM play with it? Will it pick up AD rules and GPOs? What about BCM and Project Server? '

      Can you say bloat, bloat, and more bloat?

  20. Re:Blackberry Enterprise Server by joelleo · · Score: 2, Insightful

    Not until Q4 2008

    From the features pdf

    http://download.zarafa.com/zarafa/en/Featureslist620.pdf

    "Integration with the Blackberry Enterprise Server to get email, calendar items, contacts and tasks real-time on your Blackberry. Available Q4 2008"

    --
    "In the end, there is simply no weapon more devastating than the truth, delivered in just the right way." - tnk1
  21. Re:Not GPL, maybe not Free Software by gamanimatron · · Score: 5, Informative

    Hey, look! FUD!

    --
    cogito ergo dubito
  22. Outlook support = pay to play by Ritz_Just_Ritz · · Score: 4, Informative

    From their FAQ:

    If I build Zarafa from source, can I still buy a license for Outlook access?

    Technically this is possible, but you always need to have the Zarafa-professional package for Outlook support. This package is available for the default supported distributions.

  23. Re:GPL'd community edition has limited MAPI client by Peeet · · Score: 2, Informative

    From the F.A.Q.:
    "The first three users that connect to the community versions with Outlook can only use Outlook. All other users can only connect via webaccess, imap/pop3 or Z-Push."

  24. No different than all the others... by shaitand · · Score: 4, Insightful

    Yet another open source exchange replacement that didn't open source everything required to interact with outlook.

    Without that, whats the point?

  25. anyone actually have the source ? by johnjones · · Score: 2, Interesting

    I just get bad checksum so there is a way to advertise... say its (A)GPL and then not provide the source !

    links anyone ?

  26. Re:Oh Really? by Just+Some+Guy · · Score: 2, Insightful

    Google for the debate on debian-legal about whether it complies with the DFSG. Anyway, the crux of the matter is that authors can embed unmodifiable sections in their code, and you are not allowed to alter that code even if you will not be giving copies of it away. The theory is that you're distributing the output of the program, which is part of the program itself - or some nonsense like that. This goes against decades of precedent for the idea of usage versus distribution.

    For example, if you VNC to a machine on my home LAN, you could potentially run Quickbooks. It would be executed on my machine and exporting its display to yours, but no one would ever consider this to be distribution. However, if I were running an AGPL'ed equivalent of Quickbooks on my home web server and you accessed it, the authors of the AGPL would claim that I distributed a copy of that application to you. That's their legal theory behind restricting my usage of it.

    Another poster said I was spreading FUD. Yeah, I am, and with good reason. I fear that some project I depend on may adopt the AGPL. I'm uncertain that I'd be able to use it given the additional restrictions that it piles on top of the GPL, to the point that I actually doubt it.

    --
    Dewey, what part of this looks like authorities should be involved?
  27. Re:Web app by Constantine+XVI · · Score: 2, Informative

    I think you mis-understand. This isn't meant to replace Outlook, the Windows-only desktop mail/groupware client. This is meant to replace Exchange, the Windows-only mail/groupware SERVER that Outlook is built to connect to, complete with cloning the MAPI protocol Outlook speaks. We won't have a drop-in Outlook replacement until Evolution finishes their MAPI code (IIRC in the next release).

    Of course, this is all moot in a lot of businesses if it can't connect to BES, which you (currently) need a Windows box for anyway.

    --
    "I think an etch-a-sketch with an ethernet port would beat IE7 in web standards compliance."
  28. Isn't Exchange the last big reason by rrohbeck · · Score: 2, Insightful

    why enterprises run Windows?
    Does anybody have links to success stories of large(-ish) corporations converting to Zarafa?

  29. Re:Not GPL, maybe not Free Software by zx-15 · · Score: 3, Informative

    Somebody mod parent down.

    http://www.fsf.org/licensing/licenses/agpl-3.0.html
    "Preamble

    The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software."

    http://en.wikipedia.org/wiki/Affero_General_Public_License
    "The Affero General Public License, often abbreviated as Affero GPL and AGPL (and sometimes informally called the Affero license) refers to two distinct, though historically related, free software licenses: (1) the Affero General Public License, version 1 (published by Affero, Inc. in March 2002, and based closely on the GNU General Public License, version 2 (GPLv2)), and (2) the GNU Affero General Public License, version 3 (published by the Free Software Foundation in November 2007, and closely resembling the GNU General Public License, version 3 (GPLv3))."

    If FSF considers it to be free software, how it is not free software, and by a lot of people you mean who?

  30. 150 man-years of work by nsayer · · Score: 4, Funny

    Quick! I need a baby in a month! Find me 9 women!

  31. this is not progress by Qrlx · · Score: 3, Funny

    What sort of misguided geek thinks it's a good idea to work on a project which facilitates the rest of us getting invited to meetings?

  32. Umm... and why does this matter? by Anonymous Coward · · Score: 5, Insightful

    As a former MAPI programmer (don't worry - I've largely recovered) I have to point out that this is utterly irrelevant.

    The only compelling reason to use an Exchange compatible server is to support Outlook. The issue is that Zarafa charges for the Outlook connector. This is not a new business model, people, and truth be told its been a fairly common paradigm of 'Exchange-killers' for quite awhile now. Nothing is killed until the connector is free. Full stop.

    So why doesn't anyone offer a free connector? Because it is ridiculous amount of work to build and it is something corporations are willing to pay for. It's not that replicating the server functionality is difficult, it's that Microsoft twisted and violated open standards into something utterly unholy known as Exchange to ensure that nobody but Microsoft could communicate with it. MAPI is Microsoft's obfuscation of traditional messaging protocols and is infamously poorly documented.

    I wrote about this issue for Redmond magazine about 2 years ago and nothing's changed. The connector is still the kicker and, regardless of how nifty the back-end is, until an open-source Outlook connector appears Exchange will remain one of MS's top 5 products.

    Nothing but PR to see here. Move along...

  33. Re:Not GPL, maybe not Free Software by Just+Some+Guy · · Score: 4, Informative

    If FSF considers it to be free software, how it is not free software

    One of the requirements of Free Software is "[t]he freedom to study how the program works, and adapt it to your needs (freedom 1)." The Affero GPL explicitly denies this freedom:

    If the Program as you received it is intended to interact with users through a computer network and if, in the version you received, any user interacting with the Program was given the opportunity to request transmission to that user of the Program's complete source code, you must not remove that facility from your modified version of the Program or work based on the Program, and must offer an equivalent opportunity for all users interacting with your Program through a computer network to request immediate transmission by HTTP of the complete source code of your modified version or other derivative work.

    I don't care who endorses the AGPL; by the FSF's own definitions, it is not Free Software. Get pissed off and mod me down all you want, but that doesn't change the fact that the AGPL is a EULA in that it governs the behavior of people who merely run the software, even if they do not distribute it (by any reasonable definition of the word "distribute" that has been in common usage during the history of computing).

    --
    Dewey, what part of this looks like authorities should be involved?
  34. Re:Not GPL, maybe not Free Software by Kjella · · Score: 2, Insightful

    FUD? Well, I'll let others be the judge of that but the difference between GPLv3 and Affero GPLv3 are HUGE:

    "Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network an opportunity to receive the Corresponding Source (...)"

    This is the FSF on steroids, it's the anti-ASP license and it's also unsuitable for any software you want to improve internally and not share if it in any way interacts with externals. It's still not an EULA as creating derivates is one of the copyright holder's exclusive rights (except fair use) but it's definately stretching copyright law to the absolute limit in order to force the release of code.

    --
    Live today, because you never know what tomorrow brings
  35. MORE than that by way2trivial · · Score: 4, Interesting

    I can give a meeting room, or a projector, or any other resource-- it's own exchange account- and set it to !automatically accept! some peoples meeting request, and other people's requests will have to be approved.. and when I send a meeting request to my boss, and two co-workers, and conference room B-- then conference room B will automatically show that it is 'busy' for my meeting.. and if I need a projector later-- I can send an invite to the 'projector' and reserve it as well..

    I can de-invite individual attendees....

    --
    every day http://en.wikipedia.org/wiki/Special:Random
  36. Do you use anything but Exchange? by Anonymous Coward · · Score: 2, Interesting

    > What do you say to the Hundreds of Thousands of clients who get their Exchange via SBS (Small Business Server)? And that's just the 2003 version.

    That they require too many administrators and cause more downtime.

    > How many Enterprise apps do you know of by ANY vendor that dont degrade with low disk space? Come on, dude, that aint fair and you know it.

    He also mentioned it degrading due to *large mailbox size* That's the big PITA. And you have to buy crapware to shovel messages around, whereas with normal mail spools, you can shuffle mail around pretty easily with a few quick scripts.

    > Exchange is one of those apps that can look bad if installed by an idiot. You would think a proper architect would have worked out space and usage requirements early on.

    Yeah, but it's also one of those apps that's usually installed by an idiot.

    > How do you reach a low space condition ANYWAY, if you are making proper use of quotas? No product takes more abuse due to stupid administration than Exchange server.

    No product needs as much administration as Exchange server.

    > How do you reach a low space condition ANYWAY, if you are making proper use of quotas? No product takes more abuse due to stupid administration than Exchange server.

    Powerpoint with #$#%ing embedded videos. But that's another story entirely.

    > But please, inflexible? When you have dozens of 100K+ client installations of Exchange humming along at places like Chevron and others, while the very same product can keep 20 people happy on a $500 box, you cant call it inflexible. Thats just wrong, pal.

    Everyone else can do that too. But they do it better. The main advantage of Exchange is all that integration so they can send polls or schedule meetings or whatever else. But as far as simple email goes, Exchange is more trouble than its worth.

    Which is why this project is important.

  37. Nice crippleware slashvertisement by Linux_ho · · Score: 4, Informative
    The community version doesn't support using Outlook if you need to use more than 3 clients, according to the installation document:

    The proven Zarafa groupware solution (ha) is now also available as an open source community version licensed under the Affero GPLv3. This version includes:

    AJAX based web access
    Mobile webaccess
    IMAP/POP3 gateway
    iCal gateway
    Z-Push - ActiveSync compatibility (licensed under GPLv2)

    Additionally you can use this version with the closed source Zarafa Outlook clients up to 3 Outlook users.
    Important: To use Outlook support in the community version, you need to run the zarafa-licensed daemon.

    --
    include $sig;
    1;
  38. A week??? You need new employees by baileydau · · Score: 5, Insightful

    it's around 2,400-- but then you also require 25 outlook licenses.

    once again, the price of the software is negligable compared to the cost of 25 employee's salaries...

    go ahead, waste a week of each one's time teaching them whats different about the new program.

    This is server software we are talking about here. The end users don't change their software (that's the entire point). So there is no cost for retraining end users.

    You would obviously have to train the server administration staff, but even if you did put in a "Genuine Microsoft" Exchange server, you would probably still have to do this.

    Besides, even if the front end did change, a week of training is a LOT. As it would be replacement software, the concepts are the same, it's only which button you push to do it that changes. So if you can't train them in a matter of hours, if not minutes, you really do need new employees.

    Where I work, we use a non-MS stand alone calendaring solution. Our end user training takes a couple of hours.

    How long do you think it would take to train users to use the new version of MS Office?

    --
    Ever stop to think ... and forget to start again?
  39. What about Outlook itself? by VirtualSquid · · Score: 4, Interesting

    I'm happy for the server-side people if this is progress on replacing Exchange, but what about replacing Outlook itself?
    It's one of the 3-4 missing apps that prevent me from moving to Linux. I mean, how hard can it be, to implement an email client with integrated calendar and contacts? It doesn't need every single bell and whistle - just the few features i depend on (rich text in contact memo fields, savable contact searches). I'd happily buy such an app for Linux (at, say, the same price as Outlook.) Outlook's been around for what, 11 years? And in all that time, nobody's thought to make a viable Linux alternative?

  40. Re:Not GPL, maybe not Free Software by Just+Some+Guy · · Score: 2, Informative

    Crud, I quoted an older version (that Google listed higher than the one you linked at that moment, go figure). The current version is:

    Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.

    The principle is the same: you are not allowed to modify it in certain ways, even if you do not plan to distribute copies of it.

    --
    Dewey, what part of this looks like authorities should be involved?
  41. Re:Not GPL, maybe not Free Software by AnyoneEB · · Score: 2, Informative

    The difference is who has the right to ask for the source. The GPL says anyone who gets the binaries can ask for the source. The Affero GPL says that anyone who connects to the program running on a server can ask for the source.

    --
    Centralization breaks the internet.