Package: cyrus-imapd Version: 3.0.8-6 Severity: grave Tags: upstream Dear Maintainer,
After upgrading a cyrus-imapd system from 2.4.17 (jessie-era) to 3.0.8 (buster), I discovered many missing messages. It appears that index records with MODSEQ set to zero (e.g., records for messages which predated the addition of the MODSEQ field) are being ignored. The data is still there, but not served to IMAP clients. Unfortunately, if the 3.0.8 cyrus "reconstruct" is executed to naively try to fix the missing messages, those index records (and the metadata they contain, e.g., seen flags) are lost for good! I tagged this report as "grave" because of the potential for irreversible data loss. There may be a one-line fix for this; I have filed an upstream bug report with more details: https://github.com/cyrusimap/cyrus-imapd/issues/2839 Fortunately, I have backups of the original cyrus.index files and didn't permanently lose any state, but I don't know of any way to safely upgrade to v3.x.x until this issue is fixed. -m -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-imapd depends on: ii cyrus-common 3.0.8-6 ii dpkg 1.19.7 ii libc6 2.28-10 ii libcom-err2 1.44.5-1 ii libsasl2-2 2.1.27+dfsg-1 ii libssl1.1 1.1.1c-1 ii libwrap0 7.6.q-28 ii zlib1g 1:1.2.11.dfsg-1 cyrus-imapd recommends no packages. cyrus-imapd suggests no packages. -- Configuration Files: /etc/pam.d/imap changed [not included] -- no debconf information