Hello,
I hope that you are well, good to get away from Exchange. Implementing
the backend means that you have a stmp, pop, webmail and imap server to
look for as well, not just the calendering/contacts bit.
Courier is a whole solution for that sort of situation. You can get the
calendaring bit, imap, pop, webmail there and then for contacts you
could consider something from Seyman's list or use LDAP, unless they do
all that.
I prefer to do the following, build a mail server with Maildir support
to do the smtp, its highly flexible so you can really which the living
daylights out of it, secondly you can use the Courier-Imap package from
the makers of Courier-MTA. You could use Imp or one of those software's
from Seyman's list to cover webmail and calendaring/contacts. You can
use LDAP (like exchange does) to hold authentication and global address
and contact information, heck its so flexible you could prolly write a
schema to implement some of the things you want to be stored in an LDAP
backend.
Its many components but very inter-operable. Highly scalable and
maintainable without breaking anything else. My CDN $ 0.02 and HTH.
Cheers,
Aly.
On Thu, 2003-06-26 at 09:58, Timothy Stone wrote:
> ...snip all...
>
> Great thread! We are faced with a full on implementation of a Exchange
> backend. I am "injecting" the argument for open-source or Linux based
> alternatives. OpenExchange and Samsung's product sound promising. We
> will need the full capabilities of using Outlook|OWA or any alternative
> to Exchange will not be considered.
>
> Tim
--
Aly S.P Dharshi
[EMAIL PROTECTED]
Student and System Administrator ORS Servers
"A good speech is like a good dress
that's short enough to be interesting
and long enough to cover the subject"
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
