Re: competing with exchange (and losing)



On Wed, 26 Jul 2006 12:25:23 -0400
"Eric S. Johansson" <esj@xxxxxxxxxx> wrote:

I had a customer using a Linux based e-mail solution when the
issue of calendars, contact lists, and task lists came up.
They also wanted the ability to connect with remote devices
and connect to their VoIP switch as supplied by their VoIP
vendor. Can you tell they are using Outlook for the e-mail
client? :-)

So they commissioned me to start a search of Linux based
replacements for exchange. after looking at a bunch of them,
we tried out a couple (open exchange, and can't remember
(sorry)).

The primary failing was that they couldn't provide the same
functionality as exchange. Depending on the vendor, there
were different limitations with regards to shared calendars,
task lists, reminders, remote device synchronization, etc.
Most of these systems use plug-ins which has their own
shortcomings with regards to stability and cost of rollout and
none of them integrated with the VoIP vendor[1].

so, I am disappointed but I must fully support my customer's
decision to go to exchange. The Linux exchange replacement
market is far too fragmented and is in need of consolidation
and funding. I think it probably two vendors and at least $20
million or $30 million each could get us to a viable exchange
replacement in a couple of years.

the only reason I'm raising this now is because Microsoft has
released a new version of exchange which is even easier to
manage. If you're using just e-mail, Linux is fine. But as
soon as you add all of the other features, open source
solutions are literally years away from being business ready.

Just be aware and remember, it's not just about the e-mail.

I fully agree. However, if people want exchange (features), they
should use exchange. Even within a microsoft world there is no
substitute for the "real thing" and of course, exchange
monoculture installations do also have certain disadvantages. ;-)

And:
You did not mention the great and absolutely seamless integration
of exchange into active directory.

While Linux is indeed years away from a solution like this, I
strongly doubt that it makes sense to compete on a microsoft
level.

regards
Eberhard

---eric



[1] VoIP vendor was desktop to switch solution so asterisk is
not an option. They were willing to just pay money and get
the job done.


--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



--
Eberhard Roloff
roloff it-services Midrange - Linux - VoIP

Am Fronhof 51 53639 Königswinter
Tel.: 02244 877 878 3 Fax: 02244 90 32 52
mail:eberhard@xxxxxxxxxxxx www.roloff-it.de

--
ubuntu-users mailing list
ubuntu-users@xxxxxxxxxxxxxxxx
https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



Relevant Pages

  • Re: Exchange reformatting NDR mssgs -- how to prevent this?
    ... How about creating a distribution list in Exchange that has all the different destination users separated, (perhaps syncing the Linux list with something like ADAM) or something of the sort? ... It is also used to run a bunch of mailing lists vis the ... the standard Exchange NDR format. ...
    (microsoft.public.exchange.admin)
  • Re: competing with exchange (and losing)
    ... you can consider using Lotus Notes instead of exchange. ... Lotus Notes is better and I think it is compatible with any Linux ... > and connect to their VoIP switch as supplied by their VoIP ...
    (Ubuntu)
  • RE: Public Folders and OUs
    ... this is feasible in Exchange Server. ... Restart the Microsoft Exchange information store service. ... How to Manage Address Lists When You Host Virtual Organizations ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange working with externally hosted mail - and VoIP?
    ... We run an analog phone switch with five lines in a rolling ... Our existing dsl service is 3mbps/768kbps. ... I'm testing the MS POP3 connector for exchange 2000 with an isp based ... We are going to set up a voip trial and see how it works. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: IS MY SERVER A RELAY?
    ... Most Exchange users mostly MAPI clients so the need to relay is generally ... into programs for the smtp server. ... this lists the same two accounts described above. ...
    (microsoft.public.exchange.admin)