Hi,
is there a problem with proxying POP3 connection from a frontend to a backend in v2.1.12? I've a test setup with two frontends, two backends and a mupdate master. While proxying of IMAP connection works fine and while I can connect to a backend using POP3 without problems any attempt to connect to a frontend using POP3 ends up with this: whottgen@ddev2:/prod/cimap2/current/bin$ telnet ddev1.eng.emea.uu.net 110 Trying 213.68.123.72... Connected to ddev1.eng.emea.uu.net (213.68.123.72). Escape character is '^]'. +OK ddev1.eng.emea.uu.net Cyrus POP3 Murder v2.1.10 server ready +<[EMAIL PROTECTED]> user testuser2 +OK Name is a valid mailbox pass test123 -ERR Authentication to backend server failed Connection closed by foreign host. whottgen@ddev2:/prod/cimap2/current/bin$ In auth.log I always get such a line: Feb 20 13:11:28 ddev1.eng.emea.uu.net pop3d[3663]: No worthy mechs found The imapd.conf on the frontend is this: configdirectory: /prod/cimap2/var/imap partition-default: /prod/cimap2/var/spool admins: cyradm proxy_authname: proxy-ddev1 ddev4_password: xxx ddev5_password: xxx mupdate_username: frontend-mupdate-ddev1 mupdate_authname: frontend-mupdate-ddev1 mupdate_password: xxx mupdate_server: ddev2.eng.emea.uu.net sasl_pwcheck_method: saslauthd sasl_sasldb_path: /prod/cimap2/var/sasldb The imapd.conf on the backend is this: configdirectory: /prod/cimap2/var/imap partition-default: /prod/cimap2/var/spool admins: backend-ddev5 cyradm proxy_authname: backend-ddev4 ddev4_password: xxx ddev5_password: xxx mupdate_username: backend-mupdate-ddev4 mupdate_authname: backend-mupdate-ddev4 mupdate_password: xxx mupdate_server: ddev2.eng.emea.uu.net proxyservers: proxy-ddev1 proxy-ddev3 sasl_pwcheck_method: saslauthd sasl_sasldb_path: /prod/cimap2/var/sasldb If you're wondering why there is a proxy_authname in the imapd.conf of the backend: I found that backend-to-backend moving of mailboxes seems to require this. Is this intentionally? Any hints? Thanks, Wolfgang
