Nic Bernstein
2018-03-09 00:45:46 UTC
Please re-read the upgrade documentation:
   https://www.cyrusimap.org/imap/download/upgrade.html
In particular, please consult section 5, which includes this warning:
To check your entire systemâs configuration you can use the conf-all
action. This command takes all the system defaults, along with
anything you have provided overrides for in your config files:
cyr_info conf-all -C <path to imapd.conf> -M <path to cyrus.conf>
*Important config* options: |unixhierarchysep:| and |altnamespace:|
defaults have changed in imapd.conf(5)
<https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf%285%29>.
Implications are outlined in the Note in User Namespace Mode
<https://www.cyrusimap.org/imap/concepts/features/namespaces.html#imap-admin-namespaces-mode>
and Switching the Alternative Namespace
<https://www.cyrusimap.org/imap/reference/admin/sop/altnamespace.html#imap-switching-alt-namespace-mode>.
Please also see âSieve Scripts,â below.
* unixhierarchysep: on
* altnamespace: on
Cheers,
   -nic
   https://www.cyrusimap.org/imap/download/upgrade.html
In particular, please consult section 5, which includes this warning:
To check your entire systemâs configuration you can use the conf-all
action. This command takes all the system defaults, along with
anything you have provided overrides for in your config files:
cyr_info conf-all -C <path to imapd.conf> -M <path to cyrus.conf>
*Important config* options: |unixhierarchysep:| and |altnamespace:|
defaults have changed in imapd.conf(5)
<https://www.cyrusimap.org/imap/reference/manpages/configs/imapd.conf.html#std:cyrusman-imapd.conf%285%29>.
Implications are outlined in the Note in User Namespace Mode
<https://www.cyrusimap.org/imap/concepts/features/namespaces.html#imap-admin-namespaces-mode>
and Switching the Alternative Namespace
<https://www.cyrusimap.org/imap/reference/admin/sop/altnamespace.html#imap-switching-alt-namespace-mode>.
Please also see âSieve Scripts,â below.
* unixhierarchysep: on
* altnamespace: on
Cheers,
   -nic
Using imapsync we are attempting to move our mail store from an
Cyrus-IMAPd-2.3.16 running under CentOS-6.9 to a Cyrus-IMAPD-3.0.4
running under FreeBSD-11.1p6. In all instances we are using software
as packaged by the respective distribution.
On our existing system our user mailboxes are referenced using
user.mailbox. On the new system we can create mailboxes with the same
nomenclature (user.mailbox). However, when we try to transfer an
existing mailbox to the new server via imapsync it does not use the
existing mailbox given by user.mailbox. Instead, it seems to create
on the target host a new mailbox called user/mailbox distinct from
user.mailbox.
My question is: What configuration issue is causing this discrepancy
between expected (user.mailbox --> user.mailbox) and observed
behaviour (user.mailbox --> user/mailbox)?
syslog_prefix: CYRUS
syslog_facility: MAIL
admins: cyrus admin
configdirectory: /var/imap
partition-default: /var/spool/imap
sieveusehomedir: false
sievedir: /var/imap/sieve
allowplaintext: true
anyoneuseracl: true
autocreate_inbox_folders: delivery|\
delivery.forwarding|\
delivery.imports|\
delivery.private|\
Drafts|\
Intray|\
Sent|\
Spamyes|\
Spamno|\
Trash
autocreate_quota: 102400
autocreatequota_units: 1048576
autocreate_subscribe_folders: delivery|\
delivery.forwarding|\
delivery.imports|\
delivery.private|\
Drafts|\
Intray|\
Sent|\
Spamyes|\
Spamno|\
Trash
client_timeout: 10
hashimapspool: 1
lmtp_downcase_rcpt: true
lmtp_fuzzy_mailbox_match: true
quotawarn: 5
sasl_mech_list: PLAIN
sasl_pwcheck_method: saslauthd
sendmail: /usr/sbin/sendmail
tls_client_ca_file: /usr/local/etc/pki/tls/certs/ca-bundle.crt
tls_server_cert: /usr/local/etc/pki/imapd/20160039.pem
tls_server_key: /usr/local/etc/pki/imapd/20160039.key
Cyrus-IMAPd-2.3.16 running under CentOS-6.9 to a Cyrus-IMAPD-3.0.4
running under FreeBSD-11.1p6. In all instances we are using software
as packaged by the respective distribution.
On our existing system our user mailboxes are referenced using
user.mailbox. On the new system we can create mailboxes with the same
nomenclature (user.mailbox). However, when we try to transfer an
existing mailbox to the new server via imapsync it does not use the
existing mailbox given by user.mailbox. Instead, it seems to create
on the target host a new mailbox called user/mailbox distinct from
user.mailbox.
My question is: What configuration issue is causing this discrepancy
between expected (user.mailbox --> user.mailbox) and observed
behaviour (user.mailbox --> user/mailbox)?
syslog_prefix: CYRUS
syslog_facility: MAIL
admins: cyrus admin
configdirectory: /var/imap
partition-default: /var/spool/imap
sieveusehomedir: false
sievedir: /var/imap/sieve
allowplaintext: true
anyoneuseracl: true
autocreate_inbox_folders: delivery|\
delivery.forwarding|\
delivery.imports|\
delivery.private|\
Drafts|\
Intray|\
Sent|\
Spamyes|\
Spamno|\
Trash
autocreate_quota: 102400
autocreatequota_units: 1048576
autocreate_subscribe_folders: delivery|\
delivery.forwarding|\
delivery.imports|\
delivery.private|\
Drafts|\
Intray|\
Sent|\
Spamyes|\
Spamno|\
Trash
client_timeout: 10
hashimapspool: 1
lmtp_downcase_rcpt: true
lmtp_fuzzy_mailbox_match: true
quotawarn: 5
sasl_mech_list: PLAIN
sasl_pwcheck_method: saslauthd
sendmail: /usr/sbin/sendmail
tls_client_ca_file: /usr/local/etc/pki/tls/certs/ca-bundle.crt
tls_server_cert: /usr/local/etc/pki/imapd/20160039.pem
tls_server_key: /usr/local/etc/pki/imapd/20160039.key
--
Nic Bernstein ***@onlight.com
Onlight Inc. www.onlight.com
6525 W Bluemound Rd., Ste 24 v. 414.272.4477
Milwaukee, Wisconsin 53213-4073 f. 414.290.0335
Nic Bernstein ***@onlight.com
Onlight Inc. www.onlight.com
6525 W Bluemound Rd., Ste 24 v. 414.272.4477
Milwaukee, Wisconsin 53213-4073 f. 414.290.0335