Sam Varshavchik writes:
Well, there are quite a few installations where there are different servers hosting mail services and web services.
That's what NFS is for.
Only if you have access to those servers directly. See below.
Sometime even on totally different locations.That's what load-balancing is for.
Same here. Only if you have access to the servers where email is stored.
For example, if you have a local system providing intranet services, butThe mail has to be somewhere. If it's not on server A, then on server B. However you want to label your servers, the mail has to be on one of
you don't want to have a local mail server, you allow people to access their IMAP mail on some external service provider. I don't see, where a
different approach than IMAP would work in this scenario. (Please correct
me if I am wrong).
them.
The mail server is different for most of the people working on the Intranet. They have their mails stored on freemail providers outside of the local network. IMAP is IMHO the only way to access such systems.
from. What's the benefit of sticking an extra server somewhere, whose only
reason for existence is to translate one form of mail access to another?
You only add additional overhead, and additional components that may break?
The reason for example is a project planning and organisation software, hosting among other things a central contact list. So, people are able to use the foreign freemail providers, while still utilizing the contact etc. within the intranet system.
Complexity and stability always have an inverse relationship.
ACK.
I am sure you will have tested this out. One more reason to try to implement a caching system.The speed difference between SQWebmail (which directly reads the directory), and a PHP/IMAP based system (at least on a very little used
system) is not noticable.
Multiply that by several hundred concurrent users, then see how well things work now.
One more point to utilize IMAP as the access protocol for webmail systems is the backend flexibility. I might start with an Exchange server providing IMAP services, move over to the default IMAP system that comes with my linux distribution (mostly UW-IMAP), before ending up with, IMO the most advanced in terms of ease-of-administer, authentication possibilities etc.. courier. :-)
So, I could have in the first place, utilize the Exchange server built-in WebMail system. Cool. People would need to learn something new to work with UW-IMAP via the web, and in the end, would need an introduction to yet another system. Not very TCO friendly. Right now, as speed is not really issue, but just a "Nice Thing To Have", it really doesn't matter whether or not, courier is caching some information. Down the road, there are two solutions that I see: Throw bigger hardware onto the problem, or have caching implemented.
rgds
pos
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
