Re: Mailbox directory structure
Quoting Artur Kaminski my.home.my.cas...@gmail.com: Hey all, I installed imapd server successfully, and moved configuration from old one, but then accidentally loaded another server's configuration from puppet. Now Cyrus looks for user mailboxes in User Mailbox /var/spool/imap/a/ user. /var/spool/imap/u/user^ (checked using cyradmin, with creating the mailboxes above) Actual mailbox for hypothetical user is in /var/spool/imap/a/users/ (moved from old server). In effect Postfix gets response 5.1.1 Mailbox not found to all requests, including root. The option unixhierarchysep changes the hierarchy seperatror from . to / The . is representet as ^ in filesystem. I can log in using IMAP. I can't increase Cyrus logging. Cyrus logs everything to Syslog, you have to change your syslog config to change the loglevel. Michael M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen smime.p7s Description: S/MIME Signatur Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Mailbox directory structure
Date: Wed, 15 Sep 2010 14:02:38 +0200
From: Michael Menge michael.me...@zdv.uni-tuebingen.de
Subject: Re: Mailbox directory structure
To: info-cyrus@lists.andrew.cmu.edu
Message-ID: 20100915140238.18471f8lfaaqs...@webmail.uni-tuebingen.de
Content-Type: text/plain; charset=utf-8
Quoting Artur Kaminski my.home.my.cas...@gmail.com:
Hey all,
I installed imapd server successfully, and moved configuration from old
one,
but then accidentally loaded another server's configuration from puppet.
Now
Cyrus looks for user mailboxes in
User Mailbox
/var/spool/imap/a/
user. /var/spool/imap/u/user^
(checked using cyradmin, with creating the mailboxes above)
Actual mailbox for hypothetical user is in /var/spool/imap/a/users/
(moved from old server).
In effect Postfix gets response 5.1.1 Mailbox not found to all
requests,
including root.
The option unixhierarchysep changes the hierarchy seperatror from . to /
The . is representet as ^ in filesystem.
I can log in using IMAP.
I can't increase Cyrus logging.
Cyrus logs everything to Syslog, you have to change your syslog config
to change the loglevel.
Thank you Michael for quick reply.
So unixhierarchysep = yes in my imapd.conf should change the dot vel caret
to slash?
Unfortunately it doesn't, but indeed it would solve my problem. Can it be
covered by the same variable set to no in another file?
I receive a lot of logs from all Cyrus daemons, but I actually wanted to
turn on some kind of debugging (to find why it doesn't search in user
subdirectory). Dr Google told me about CYRUS_VERBOSE=1, but placed in
/etc/init.d/cyrus-master changed nothing.
Your advise about unixhierarchysep probably makes me happy with the current
level of logging.
Thank you
Artur
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Mailbox directory structure
On 26 Nov 2002, John Lederer writes: When I looked at the mailbox structure of our test group I found some disconcerting variance. Some users had a directory named INBOX, some did not. ... In any event we want a consistent mailbox structure that supports Moxilla's special Sent, Drafts, and Templates diretcories. We want to standardize, but we are not sure what to standardize on. Can someone tell me what the preferred structure is, particularly for Mozilla? A mailbox called INBOX visible as a file in your filesystem on your Cyrus IMAP server is probably a mistake of some sort, often (based on experience here at least) relating to either the choice of hierarchy separator or default folder prefix. We use the following cyradm commands (for a user named fred and with unixhiersep set to yes): cm user/fred cm user/fred/Drafts cm user/fred/Sent cm user/fred/Templates or their equivalent IMAP commands. The INBOX is created by the first of these commands. If you have altnamespace turned on, Outlook users will be happier, because they will see a folder structure that is closer to the Outlook norms when used with Exchange Server. Jonathan
