I've been managing Exchange Servers for the last few years and I'm finally tired of the uphill battle. I'm looking for a strategic "career" product replacement, not only for myself, but for my customers as well.
Not entirely unfamiliar with messaging concepts, I have to confess I've never waded into the UNIX environment in the messaging arena. I have some basic questions, each of which can be broken down into distinct threads if responders wish to do so. Furthermore, this is not an attempt to receive an education via the maillist. If I can be pointed to specific documentation that directly addresses my questions that would be the biggest help of all. The only thing that doesn't work for me is if someone consideratly replies with an RTFM comment. I'm not looking for how to assistance in installing the mail server product. I come to the maillist for help and direction. Any amount being offered to help me flip my career over and away from Exchange Server to Courier would be useful: 1. I'm looking for full featured messaging and not just email. Exchange Server offered (for a dear price both financially and professionally) facilities for handling contacts, tasks, calendaring, public folders and many other features. These are implemented in a collaborative manner so that user can access the information assets of other users. Can Courier be implemented in such way so that the messaging repository accomodates diverse messaging objects and formats? How is this done? Is a database repository implemented to store to persist these objects external to the mail server? 2. Exchange Server offers OWA (Outlook Web Access). A very handy feature. For my part, I'm committing to Apache and Zope as well as PostgreSQL. Courier seems to offer SqWebmail as an integrated product. I used it briefly and, although it was certainly functional, I wasn't impressed with the interface. Can alternative products be easily introduced to replace SqWebmail. I've looked at TWIG, a PHP implementation, and I'm still interested in the experiences of others, either those of success or failure, with other web front ends that support diverse message formats. 3. Exchange Server is utterly dependant on IIS and will not work without it. As I mentioned above, I've committed to Apache, etc. Are there any problems with Courier's interaction with Apache, or any other webserver? I can't always impose Apache on a customer so it would help to know if Courier is in some way picky, as is Exchange Server. 4. With respect to volume, Can Courier and it's related products take advantage of SMP if the OS is supporting it? On a single CPU system, at what point does Courier begin to brake? I have other questions that I'll work to better formulate and which I'll submit in a future email. Thanks so much for being there, being free and being open and thanks in advance for any help you're willing to provide. I look forward to doing what I can to support the community in return. Tamir ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
