Re: Cyrus IMAP-3.0.7 - listmailbox user/* does not report all mailboxes

2018-07-16 Thread ellie timoney
Starting with the obvious, but did the user you login to cyradm as have admin privileges? Are they listed in "admins:" in your imapd.conf? If you logged into cyradm as a regular user, you would only see mailboxes that your user had been granted access to... ;) On Tue, Jul 17, 2018, at 2:09

Re: Moving from single to multi-domain. Mailboxes from default domain not being the same as before

2018-07-16 Thread ellie timoney
On Tue, Jul 17, 2018, at 3:37 AM, Heiler Bemerguy wrote: > Em 06/07/2018 00:10, ellie timoney escreveu: > >> Hi, >> >> The "defaultdomain" is the domain that's assumed by Cyrus for users >> that are uid only. Any other domain needs to be explicitly specified >> in the user (this applies to

Re: Moving from single to multi-domain. Mailboxes from default domain not being the same as before

2018-07-16 Thread Heiler Bemerguy via Info-cyrus
Em 06/07/2018 00:10, ellie timoney escreveu: Hi, The "defaultdomain" is the domain that's assumed by Cyrus for users that are uid only.  Any other domain needs to be explicitly specified in the user (this applies

Cyrus IMAP-3.0.7 - listmailbox user/* does not report all mailboxes

2018-07-16 Thread James B. Byrne via Info-cyrus
I We recently moved our imap service from CentOS and IMAP-2.11 to FreeBSD and IMAP 3.0.7. At the time we followed the upgrade path and at the same time updated our mailboxes to the latest version: sudo -u cyrus /usr/local/cyrus/sbin/reconstruct -f -r -G -V max user/* # Reconstruct and upgrade the

Help! Cyrus 2.5.11 segmentation fault

2018-07-16 Thread Marco Chesi
Hello, we have a Cyrus 2.5.11 on Debian 7 using murder (2 frontends, 3 backends, 1 mupdate, about  5000 mailboxes) in production environment, hosted by a VMware cluster 6.5. Suddenly, ALL mailboxes have becomed inaccessible. In the log, we found many messages like this:    master[5965]: