This may be a red herring, but I notice you have hashimapspool
on, there are some new hash options available in some later
releases, it might be worth reviewing the various options in case
the default changed. I don't know much about hashing because I
leave it off, but when I first attempted to create a new server
hashing was on by default and I was scratching my head over how to
copy the directories from the current spool to it (I reconfigured
with hashing off). Anyway, my point is if the hashing has changed,
your spool directory structure will be different.
On 08/09/2021 12:36, bsh@xxxxxxxxxxx
wrote:
Here's the imad.conf:unixhierarchysep: 1 sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5 syslog_prefix: cyrus popminpoll: 1 sieveusehomedir: false partition-default: /var/spool/cyrus/mail partition-servername: /mnt/data/cyrus/mail tls_versions: tls1_0 tls1_1 tls1_2 tls_client_ca_dir: /etc/ssl/certs reject8bit: no tls_ciphers: TLSv1+HIGH:!aNULL: @STRENGTH mboxname_lockpath: /run/cyrus/lock sasl_auto_transition: no defaultpartition: default configdirectory: /var/lib/cyrus sievedir: /var/spool/sieve umask: 077 lmtpsocket: /var/run/cyrus/socket/lmtp sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux idlesocket: /var/run/cyrus/socket/idle tls_server_key: /etc/ssl/private/servername.key hashimapspool: 1 notifysocket: /var/run/cyrus/socket/notify tls_session_timeout: 1440 proc_path: /run/cyrus/proc tls_server_cert: /etc/ssl/certs/servername.crt admins: cyrus myusername lmtp_downcase_rcpt: yes allowplaintext: yes munge8bit: no imap_admins: cyrus myusername tls_client_ca_file: /etc/ssl/certs/servername.crt #autocreatequota_units: 1048576 autocreate_quota: 102400 sasl_pwcheck_method: saslauthd
