[EMAIL PROTECTED] 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.
Sometime even on totally different locations.
That's what load-balancing is for.
For example, if you have a local system providing intranet services, but 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).The 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 them.
And where the mail ends up to be, then that's where you want to get the mail 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? Complexity and stability always have an inverse relationship. As the saying goes: the more you overthink the plumbing, the easier it is to clog up the drain.
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.
-------------------------------------------------------
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
