Quoting Dave McMurtrie <dave64@xxxxxxxxxxxxxx>:
On 03/16/2011 09:12 AM, Michael Menge wrote:Hi, i have a problem configuring cyrus backend in a almost traditional murder setup. I have one master process which starts the forntend and backend services. The forntend services use /etc/imapd_fe.conf as config file and listen on the external network interface and the backend services listen to the internal network interfaces and use /etc/imapd_be.conf The lmtpdproxy delivers the mail to the backend using lmtp over tcp. The backend lmtpd asks the mupdate server where the mailbox is, which results in the "wrong" answer that the mailbox is remote. The backend tries to proxies the mail to an other lmtpd on the same backend. This results in an infinite loop. I tried this with 2.4.6 and 2.3.16. AFAIK the backend config must contain the mupdate_server because create mailbox, rename mailbox and delete mailbox information must be send to the mupdate master. But if mupdate_server is configured lmtpd will ask the mupdate_server where the mailbox is, which will always result in an "remote mailbox" as answer What do i need to change?If you're running 2.3.x on your frontends and 2.4.x on your backends, you need to upgrade your frontends.
Both frontend and backends where running 2.4.6 in the first try. But after the fist problems i suspected a bug, as this setup was working on a test system with an early 2.3.x some time ago. So i tried this setup with 2.3.16. but it has the same problems. -------------------------------------------------------------------------------- M.Menge Tel.: (49) 7071/29-70316 UniversitÃt TÃbingen Fax.: (49) 7071/29-5912Zentrum fÃr Datenverarbeitung mail: michael.menge@xxxxxxxxxxxxxxxxxxxx
WÃchterstraÃe 76 72074 TÃbingen
Attachment:
smime.p7s
Description: S/MIME Signatur
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
