On 23.3.2012, at 20.24, Gedalya wrote:
On 03/23/2012 02:12 PM, Luca Lesinigo wrote:
Il giorno 23/mar/2012, alle ore 11:50, Timo Sirainen ha scritto:
Are you thinking about actual "dummy" proxying (which is normally what Dovecot proxying is about) or about the "imapc" backend (http://www.dovecot.fi/products/105-dovecot-imap-adaptor.html)? If you're using Dovecot as backend servers, there's really no reason to use imapc proxying. I actually didn't know about the two different modes. I guess I would need imapc to support the older Courier-IMAP server until I migrated everything away from it, and that I could use "dummy" proxying for the newer dovecot backends. I don't know if the two can be used at the same time (eg. imapc to the older backend and dummy to the newer) and/or if there is any drawback in running everything on imapc (old and new dovecot server). I'll be investigating this.... I'm using the dummy proxying with a very different backend, certainly not dovecot, and it works great. For your needs (as I understand them) It's a much simpler and robust solution than imapc. Try it out. The main potential source of trouble is possible differences in the CAPABILITY string, but it hasn't caused me any actual problems.
Right, a lot of people have done migration from Courier -> Dovecot using the dummy proxying. Since v2.0 the proxying automatically handles any CAPABILITY string issues.