From falon at ruparpiemonte.it Fri Aug 7 09:51:54 2020 From: falon at ruparpiemonte.it (Marco) Date: Fri, 7 Aug 2020 15:51:54 +0200 Subject: Event notifications question Message-ID: Hello, I'm trying event notifications. I would like to see if there are some methods to track all messages moved on a folder named "Spam", for instance. First, I see that event filters in imapd.conf don't allow to specify a folder name... so the notifications produced are very large. A way to emit only a kind of event, such as "vnd.cmu.MessageMove" could be appreciated. My question is about "event_extra_params". It seems that I can add extra parameters. For instance, as you can see in https://www.cyrusimap.org/imap/concepts/features/event-notifications.html#imap-features-event-notifications-messagemove messageMove doesn't report the "messageContent" field. So in imapd.conf I added: event_extra_params: timestamp messages messageContent I restarted the server, but messageMove events still exclude messageContent. Do I have misunderstood something? This is my config: # Notify event_notifier: log event_exclude_specialuse: \Drafts event_extra_params: timestamp messages messageContent event_groups: message Thank you very much Cheers Marco From ruprechtsberger at volkshilfe-ooe.at Wed Aug 12 05:16:48 2020 From: ruprechtsberger at volkshilfe-ooe.at (Rainer Ruprechtsberger) Date: Wed, 12 Aug 2020 11:16:48 +0200 Subject: Cryus 3.2.2: Remote does not support ANNOTATEMORE Message-ID: <01c871f1-177c-b36e-290c-2b0b8195692f@volkshilfe-ooe.at> Hi, not sure if it is only after the upgrade to 3.2.2 since the features are not that much in use. But I did set 'expire' and 'sharedseen' before. Now I get 'Remote does not support ANNOTATEMORE' using 'mboxconfig .. expire' or 'sharedseen' or even 'info'. My admin account seems to be admin still (no problem creating, removing mailboxes or set acls). Any idea what could have happend there? Thanks, -- Rainer Ruprechtsberger Volkshilfe Ober?sterreich IT 4020 Linz, Glimpfingerstrasse 48 Tel.: +43 732 3405 123 Mobil.: +43 676 8734 1123 ZVR Zahl: 064371505 Volkshilfe. Wir sind f?r die Menschen da. From falon at ruparpiemonte.it Wed Aug 12 05:59:50 2020 From: falon at ruparpiemonte.it (Marco) Date: Wed, 12 Aug 2020 11:59:50 +0200 Subject: Cryus 3.2.2: Remote does not support ANNOTATEMORE In-Reply-To: <01c871f1-177c-b36e-290c-2b0b8195692f@volkshilfe-ooe.at> References: <01c871f1-177c-b36e-290c-2b0b8195692f@volkshilfe-ooe.at> Message-ID: <7d11c570-08e2-cd5a-4ebd-8cbac720de4b@ruparpiemonte.it> Il 12/08/2020 11:16, Rainer Ruprechtsberger ha scritto: > Hi, > not sure if it is only after the upgrade to 3.2.2 since the features are > not that much in use. But I did set 'expire' and 'sharedseen' before. > > Now I get 'Remote does not support ANNOTATEMORE' using 'mboxconfig .. > expire' or 'sharedseen' or even 'info'. [...] Hello Rainer, if I well remember, from 3.2 version Cyrus IMAP does not support the ANNOTATEMORE experimental extension by default no more. It provides now the support for METADATA only. Sharedseen, comment, expire, etc are all annotations. I have a lot of problems using Cyrus::IMAP::Admin between different Cyrus IMAP server versions. I suggest to use the Cyrus::IMAP::Admin version provided by the Cyrus IMAP server. So, when you upgrade Cyrus IMAP, upgrade the Perl admin utility too and use that. Alternatively, you can try to configure your Cyrus IMAP 3.2 with annotation_enable_legacy_commands: 1 but I never verified this chance. Upgrade the client to use METADATA could be the better and definitive choice. Cheers Marco From ruprechtsberger at volkshilfe-ooe.at Wed Aug 12 06:14:05 2020 From: ruprechtsberger at volkshilfe-ooe.at (Rainer Ruprechtsberger) Date: Wed, 12 Aug 2020 12:14:05 +0200 Subject: Cryus 3.2.2: Remote does not support ANNOTATEMORE In-Reply-To: <7d11c570-08e2-cd5a-4ebd-8cbac720de4b@ruparpiemonte.it> References: <01c871f1-177c-b36e-290c-2b0b8195692f@volkshilfe-ooe.at> <7d11c570-08e2-cd5a-4ebd-8cbac720de4b@ruparpiemonte.it> Message-ID: On 8/12/20 11:59 AM, Marco wrote: [...] > I suggest to use the Cyrus::IMAP::Admin version provided by the Cyrus > IMAP server. So, when you upgrade Cyrus IMAP, upgrade the Perl admin > utility too and use that. Thanks a lot. My problem came from installing cyrus from the debian backports repository and I indeed forgot to pull the cyrus-admin package from there as well. /r From ellie at fastmail.com Wed Aug 19 02:43:42 2020 From: ellie at fastmail.com (ellie timoney) Date: Wed, 19 Aug 2020 16:43:42 +1000 Subject: Cyrus IMAP 2.4.21, 2.5.16 and 3.0.14 released Message-ID: <0aefd78d-2ef3-42dc-b65a-49561cb03614@www.fastmail.com> The Cyrus team is proud to announce the immediate availability of new legacy versions of Cyrus IMAP. The primary motivator for these releases is to allow XFER to correctly recognise newer Cyrus backends. If you run a legacy Cyrus installation in a murder configuration, and ever wish to upgrade your backends to 3.1, 3.2 or 3.3, you will need these fixes. Details and discussion of this issue are available at https://github.com/cyrusimap/cyrus-imapd/issues/3123 If your legacy Cyrus installation is not in a murder configuration, please check the release notes to see if any of the other changes are things you care about. 2.4.21 release notes: https://www.cyrusimap.org/imap/download/release-notes/2.4/x/2.4.21.html 2.4.21 download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-2.4.21/cyrus-imapd-2.4.21.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-2.4.21/cyrus-imapd-2.4.21.tar.gz.sig 2.5.16 release notes: https://www.cyrusimap.org/imap/download/release-notes/2.5/x/2.5.16.html 2.5.16 download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-2.5.16/cyrus-imapd-2.5.16.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-2.5.16/cyrus-imapd-2.5.16.tar.gz.sig 3.0.14 release notes: https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.14.html 3.0.14 download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.14/cyrus-imapd-3.0.14.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.0.14/cyrus-imapd-3.0.14.tar.gz.sig There should also be a new stable 3.2 release in the next week or so, so keep an eye out for the announcement! On behalf of the Cyrus team, ellie timoney From frederik at frehi.be Mon Aug 24 04:22:56 2020 From: frederik at frehi.be (Frederik Himpe) Date: Mon, 24 Aug 2020 10:22:56 +0200 Subject: IOERROR: conversations_audit on store Message-ID: <6929e89103927fc1f24cb5cb5e2af117e03917b7.camel@frehi.be> I am using Cyrus 3.2.2 on Debian Buster 10 (package from buster- backports). I am having lots of errors similar to these in the logs: cyrus/imaps[24052]: IOERROR: conversations_audit on store: /var/lib/cyrus/user/e/example.conversations Bff62cd0852db22e1 0 (1452110 1 0 0 () ((1 1452109 1 1 0)) () foobar. 0 () 1452109) The same problem happend with Cyrus 3.0.x and seems to happen often for specific users, usually with big mailboxes (one of them 40GB+). When upgrading to 3.2.2, I ran reconstruct -V max ctl_conversationsdb -b -r quota -f dav_reconstruct -a as per the instructions given in the documentation. /var/lib/cyrus and /var/spool/cyrus are on ext4, Linux kernel at this moment is 5.4.48 (also happend with different kernels). imapd.conf: configdirectory: /var/lib/cyrus proc_path: /run/cyrus/proc mboxname_lockpath: /run/cyrus/lock defaultpartition: default partition-default: /var/spool/cyrus/mail partition-news: /var/spool/cyrus/news altnamespace: yes unixhierarchysep: yes lmtp_downcase_rcpt: yes admins: cyradm allowanonymouslogin: no popminpoll: 1 autocreate_quota: 5000000 umask: 077 sieveusehomedir: false sievedir: /var/spool/sieve httpmodules: caldav carddav hashimapspool: true allowplaintext: yes sasl_mech_list: PLAIN sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux sasl_minimum_layer: 128 sasl_pwcheck_method: saslauthd sasl_auto_transition: no tls_server_cert: /etc/letsencrypt/live/ai.vub.ac.be/fullchain.pem tls_server_key: /etc/letsencrypt/live/ai.vub.ac.be/privkey.pem tls_client_ca_dir: /etc/ssl/certs tls_session_timeout: 1440 tls_ciphers: TLSv1.2:+TLSv1:+HIGH:!aNULL:@STRENGTH tls_versions: tls1_0 tls1_1 tls1_2 lmtpsocket: /run/cyrus/socket/lmtp idlesocket: /run/cyrus/socket/idle notifysocket: /run/cyrus/socket/notify syslog_prefix: cyrus delete_mode: delayed expunge_mode: delayed sync_log: on sync_log_channels: squatter conversations: 1 cyrus.conf: START { recover cmd="/usr/sbin/cyrus ctl_cyrusdb -r" idled cmd="idled" } SERVICES { imap cmd="imapd -U 30" listen="imap" prefork=0 maxchild=100 imaps cmd="imapd -s -U 30" listen="imaps" prefork=0 maxchild=100 pop3 cmd="pop3d -U 30" listen="pop3" prefork=0 maxchild=50 pop3s cmd="pop3d -s -U 30" listen="pop3s" prefork=0 maxchild=50 http cmd="httpd -U 30 -p 256" listen="localhost:8008" prefork=0 maxchild=100 lmtpunix cmd="lmtpd" listen="/var/spool/postfix/var/run/cyrus/socket/lmtp" prefork=0 maxchild=20 sieve cmd="timsieved" listen="sieve" prefork=0 maxchild=100 notify cmd="notifyd" listen="/run/cyrus/socket/notify" proto="udp" prefork=1 } EVENTS { checkpoint cmd="/usr/sbin/cyrus ctl_cyrusdb -c" period=30 delprune cmd="/usr/sbin/cyrus expire -E 3" at=0401 tlsprune cmd="/usr/sbin/cyrus tls_prune" at=0415 deleteprune cmd="/usr/sbin/cyrus expire -E 4 -D 28" at=0430 expungeprune cmd="/usr/sbin/cyrus expire -E 4 -X 28" at=0445 squatter1 cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" period=120 squattera cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" at=0517 } Any idea what is going wrong? -- Frederik Himpe From ellie at fastmail.com Thu Aug 27 22:59:52 2020 From: ellie at fastmail.com (ellie timoney) Date: Fri, 28 Aug 2020 12:59:52 +1000 Subject: IOERROR: conversations_audit on store In-Reply-To: <6929e89103927fc1f24cb5cb5e2af117e03917b7.camel@frehi.be> References: <6929e89103927fc1f24cb5cb5e2af117e03917b7.camel@frehi.be> Message-ID: <5921af7e-a6e9-477e-a239-8f334b3ceae4@www.fastmail.com> Hi Frederik, >From the source, it looks like this error is reported when the internal counts in the conversations data are out of sync. I don't have any insight as to what might cause this, but I think you should be able to run "ctl_conversationsdb" with the "-R" argument for the affected users, to recalculate their counts. Cheers, ellie On Mon, 24 Aug 2020, at 6:22 PM, Frederik Himpe via Info-cyrus wrote: > I am using Cyrus 3.2.2 on Debian Buster 10 (package from buster- > backports). > > I am having lots of errors similar to these in the logs: > > cyrus/imaps[24052]: IOERROR: conversations_audit on store: > /var/lib/cyrus/user/e/example.conversations Bff62cd0852db22e1 0 > (1452110 1 0 0 () ((1 1452109 1 1 0)) () foobar. 0 () 1452109) > > The same problem happend with Cyrus 3.0.x and seems to happen often for > specific users, usually with big mailboxes (one of them 40GB+). When > upgrading to 3.2.2, I ran > > reconstruct -V max > ctl_conversationsdb -b -r > quota -f > dav_reconstruct -a > > as per the instructions given in the documentation. > > > /var/lib/cyrus and /var/spool/cyrus are on ext4, Linux kernel at this > moment is 5.4.48 (also happend with different kernels). > > imapd.conf: > configdirectory: /var/lib/cyrus > proc_path: /run/cyrus/proc > mboxname_lockpath: /run/cyrus/lock > defaultpartition: default > partition-default: /var/spool/cyrus/mail > partition-news: /var/spool/cyrus/news > altnamespace: yes > unixhierarchysep: yes > lmtp_downcase_rcpt: yes > admins: cyradm > allowanonymouslogin: no > popminpoll: 1 > autocreate_quota: 5000000 > umask: 077 > sieveusehomedir: false > sievedir: /var/spool/sieve > httpmodules: caldav carddav > hashimapspool: true > allowplaintext: yes > sasl_mech_list: PLAIN > sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux > sasl_minimum_layer: 128 > sasl_pwcheck_method: saslauthd > sasl_auto_transition: no > tls_server_cert: /etc/letsencrypt/live/ai.vub.ac.be/fullchain.pem > tls_server_key: /etc/letsencrypt/live/ai.vub.ac.be/privkey.pem > tls_client_ca_dir: /etc/ssl/certs > tls_session_timeout: 1440 > tls_ciphers: TLSv1.2:+TLSv1:+HIGH:!aNULL:@STRENGTH > tls_versions: tls1_0 tls1_1 tls1_2 > lmtpsocket: /run/cyrus/socket/lmtp > idlesocket: /run/cyrus/socket/idle > notifysocket: /run/cyrus/socket/notify > syslog_prefix: cyrus > delete_mode: delayed > expunge_mode: delayed > sync_log: on > sync_log_channels: squatter > conversations: 1 > > cyrus.conf: > START { > recover cmd="/usr/sbin/cyrus ctl_cyrusdb -r" > > idled cmd="idled" > } > SERVICES { > imap cmd="imapd -U 30" listen="imap" prefork=0 maxchild=100 > imaps cmd="imapd -s -U 30" listen="imaps" prefork=0 maxchild=100 > pop3 cmd="pop3d -U 30" listen="pop3" prefork=0 maxchild=50 > pop3s cmd="pop3d -s -U 30" listen="pop3s" prefork=0 maxchild=50 > http cmd="httpd -U 30 -p 256" listen="localhost:8008" prefork=0 > maxchild=100 > lmtpunix cmd="lmtpd" > listen="/var/spool/postfix/var/run/cyrus/socket/lmtp" prefork=0 > maxchild=20 > sieve cmd="timsieved" listen="sieve" prefork=0 maxchild=100 > notify cmd="notifyd" listen="/run/cyrus/socket/notify" proto="udp" > prefork=1 > } > EVENTS { > checkpoint cmd="/usr/sbin/cyrus ctl_cyrusdb -c" period=30 > delprune cmd="/usr/sbin/cyrus expire -E 3" at=0401 > tlsprune cmd="/usr/sbin/cyrus tls_prune" at=0415 > deleteprune cmd="/usr/sbin/cyrus expire -E 4 -D 28" at=0430 > expungeprune cmd="/usr/sbin/cyrus expire -E 4 -X 28" at=0445 > squatter1 cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" > period=120 > squattera cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" at=0517 > } > > Any idea what is going wrong? > > -- > Frederik Himpe > > ---- > 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 > From ellie at fastmail.com Fri Aug 28 00:23:57 2020 From: ellie at fastmail.com (ellie timoney) Date: Fri, 28 Aug 2020 14:23:57 +1000 Subject: Cyrus IMAP 3.2.3 released Message-ID: The Cyrus team is proud to announce the immediate availability of a new version of Cyrus IMAP: 3.2.3 Download URLs: https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.3/cyrus-imapd-3.2.3.tar.gz https://github.com/cyrusimap/cyrus-imapd/releases/download/cyrus-imapd-3.2.3/cyrus-imapd-3.2.3.tar.gz.sig Please consult the release notes and upgrade documentation before upgrading to 3.2.3: https://www.cyrusimap.org/imap/download/release-notes/3.2/x/3.2.3.html https://www.cyrusimap.org/imap/download/upgrade.html And join us on Github at https://github.com/cyrusimap/cyrus-imapd to report issues, join in the deliberations of new features for the next Cyrus IMAP release, and to contribute to the documentation. On behalf of the Cyrus team, Kind regards, ellie timoney