Hello, I have deployed a Cyrus IMAP Murder environment using Cyrus-Imapd on Debian/Linux with the following servers and versions:
cyrmaster.domain - version 3.10.2-1 (master) frontend.domain - version 3.10.2-1 (frontend) backend1.domain - version 3.10.2-1 (backend) oldbackend.domain - version 3.0.8-6 (legacy backend, currently disconnected for troubleshooting) Description of the Problem Accessing mailboxes via IMAP through the frontend works perfectly; users can login and read messages. The base MUPDATE database on the master is fully synchronized and contains all mailbox entries from all backend servers, verified by exporting and inspecting mailboxes.db. When logged into the frontend console (via cyradm or equivalent) with administrative privileges, the command `lm` lists all accounts correctly. However, commands like `lm user.account` to view specific mailbox details return nothing — no information is shown. Similarly, listing permissions, granting rights, or attempting mailbox migration fail with messages that the account/mailbox does not exist. Testing the same commands (lm user.account) directly on the backend works correctly, confirming backend functionality. All servers authenticate properly with the master mupdate service (verified by logs), and communication is confirmed stable. Debug logging at both frontend and backend levels with debug_params: imap mupdate yields no meaningful errors. Network connectivity between frontend, backend, and master is verified. All related ports and sockets are accessible and correctly configured. What Has Been Verified Without Resolution. Consistent identical Cyrus-Imapd version (3.10.2-1) on master, frontend, and backend. Removed legacy backend to rule out version mismatch conflicts. Proper synchronization of mailbox list via ctl_mboxlist -m across all backends. Correct configuration of proxy authorization (proxy_authname on frontend and proxyservers on backend). No network blocks or access permission errors in system logs. No SASL or authentication failures during proxy or mupdate operations. Frontend and backend can fully authenticate to the master mupdate service (cyrmupdate user). Verified configuration against examples from official Cyrus-Imapd documentation repository. Summary The system behaves correctly for normal IMAP operations (message access, login via frontend). The master clearly owns a complete and up-to-date mailbox database. However, administrative commands on frontend console targeting specific accounts fail due to the frontend returning "Mailbox does not exist," despite those mailboxes existing and being accessible directly on backend servers. Any guidance or suggestions for advanced diagnosis, debugging techniques, or known issues related to this symptom in Cyrus-IMAP Murder would be greatly appreciated. Thank you in advance for your help. Jarosław Danielski ------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/T9464474cb66a6f4a-M05979eadbd0364582b70ecca Delivery options: https://cyrus.topicbox.com/groups/info/subscription
