summaryrefslogtreecommitdiffstats
path: root/roles/IMAP-proxy/templates/etc
Commit message (Collapse)AuthorAgeFiles
* Remove the IMAP caching proxy.Guilhem Moulin2016-05-282
| | | | | | | | | Dovecot imapc requires two authentication rounds to the IMAP backend for each connection. It seems suboptimal that Roundcube keeps connecting to the IMAP server for each new connection, but benchmarks shows little advantage in caching the IMAP sessions with imapproxy: http://www.dovecot.org/list/dovecot/2012-February/133544.html
* Dovecot imapc: use the version from jessie-backports.Guilhem Moulin2016-05-231
| | | | | Since many bug have been fixed since 2.2.13, and we really want passthrough search on the caching proxy.
* Dovecot imapc: don't hardcode the master IMAP server's IP.Guilhem Moulin2016-05-232
|
* Assume a DNS entry for each role.Guilhem Moulin2015-06-072
| | | | | | E.g., ldap.fripost.org, ntp.fripost.org, etc. (Ideally the DNS zone would be provisioned by ansible, too.) It's a bit unclear how to index the subdomains (mx{1,2,3}, etc), though.
* Use a local IMAP caching proxy under the webmail.Guilhem Moulin2015-06-072
(Unless the webmail is itself a full IMAP server.) It replaces RoundCube's own IMAP and message caches. Dovecot's IMAPC storage backend is not very documented, but provides smart IMAP proxying. References include: http://dovecot.org/pipermail/dovecot/2011-January/056975.html http://wiki2.dovecot.org/HowTo/ImapcProxy http://wiki2.dovecot.org/Migration/Dsync