thanks Brian for your suggestion:
* we're under a constraint that the webmail boxes cannot be altered.
sadly this
means we can't use the obvious solution as suggested by yourself.
* the users are already sticky loadbalanced to the webmail servers. the
problem
is between the webmail servers and the imap servers and any lb or
proxies in between.
tariq
> (user) ----- [webmail] -- -- -- [IMAP Proxy] -------- <lb> ------ [IMAP
> server]
>
> \- no resilience -/
Alternatively:
(user) ------ <lb> ----- [webmail] - [IMAP Proxy] ---- <lb> ---- [IMAP server]
\---- [webmail] - [IMAP Proxy] -/ \--- [IMAP server]
\---- [webmail] - [IMAP Proxy] -/ \--- [IMAP server]
That is, use 'sticky' loadbalancing to ensure a particular user's HTTP
requests always hit the same webmail frontend. Each webmail frontend has its
own IMAP proxy (running on the same box).
Regards,
Brian.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
