User mail spool partitioning mystery

[Patrick Goetz]

That's it! Thanks for the heads up!  I assumed that all the spool hash 
options only applied when you actually have more than one partition, 
which I don't.

Unfortunately this is going to complicate my ability to use the 
excellent migration plan outlined by Nic Berstein on 2014-12-19. 
mailboxes.db will know about the spool files in their old, hashed 
location, which I'd like to get rid of, since all the mail resides on 
one physical partition anyway, so having it set up this way just adds 
unnecessary directory structures.  I might end up having to use imapsync 
after all.


On 01/16/2015 03:04 PM, Patrick Boutilier wrote:
> On 01/16/2015 04:57 PM, Patrick Goetz wrote:
>> I have a couple of existing cyrus 2.3.16 installs with this partitioning
>> configuration in imapd.conf:
>>
>>     defaultpartition: default
>>     partition-default: /home/cyrus/mail
>>
>> I create users using cyradm:  cm user.myuser
>>
>> and the user mail spool folder has this heirarchy:
>>
>>     mail
>>       |
>>         a
>>         |---- user
>>                 |---- auser1
>>                 |---- auser2
>>                 |---- auser3
>>                ...
>>         b
>>         |---- user
>>                 |---- buser1
>>                 |---- buser2
>>                ...
>>         c
>>         d
>>        ...
>>         x
>>         y
>>         z
>>         stage.
>>
>>
>> I just assumed that this structure was built in to cyrus; however on my
>> new 2.4.17 install the partition settings in imapd.conf are similar:
>>
>>     defaultpartition: default
>>     partition-default: /srv/cyrus
>>     unixhierarchysep: yes   <--- (now using this)
>>
>>
>> however all newly created users (cyradm:  cm user/myuser) are dumped
>> into a single folder:
>>
>>     cyrus
>>       |
>>         user
>>           |---- myuser
>>           |---- otheruser
>>           |---- thirduser
>>          ...
>>
>>
>> I simply can't find any difference in the configuration files that
>> result in this discrepancy.  Was the [a-z] partitioning in the 2.3.16
>> install baked in to the Debian cyrus package I used, say in cyradm?
>>
>
> Sounds like you have hashimapspool enabled in the 2.3.16 installs.
>
>
>
> hashimapspool: 0
>              If  enabled,  the partitions will also be hashed, in
> addition to the hashing done on configuration directories.  This is
> recommended if one partition has a very bushy mailbox tree.
>
>
>
>> ----
>> Cyrus Home Page: http://www.cyrusimap.org/
>> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>> To Unsubscribe:
>> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>>
>
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>