How can I fix dovecot crashing with the Error: Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event) since upgrading to Plesk v18.0.76?

After upgrading to Plesk v18.0.76 dovecot keep crashing with the error:

Feb 19 11:59:29 plesk01 dovecot: service=imap, user=redacted@redacted.tld, ip=[1.2.3.4]. Panic: file imap-sieve-storage.c: line 216 (imap_sieve_add_mailbox_event): assertion failed: (ismt->src_box == NULL || ismt->src_box == src_box)

Cause

This is a known issue in the dovecot-pigeonhole v2.4.2 shipped with Plesk 18.0.76 related to how certain email clients handle message movement, particularly when the Sieve plugin is involved. The panic is often triggered by specific IMAP client behaviors, such as moving or deleting emails, especially from mobile devices like iPads or Android phones using apps like Thunderbird. The issue seems to stem from a conflict within the internal handling of the source mailbox during the Sieve-related operations. It has been widely discussed on the Dovecot mailing list and Plesk forums.

Workaround

A temp fix is to run the commands below until Plesk can get this issue fixed:

// apply the fix
echo 'mail_attachment_detection_options =' > /etc/dovecot/conf.d/999_fix_crash.conf

// restart dovecot
systemctl restart dovecot
  • dovecot, backtrace, Plesk 18.076, panic, imap-sieve-storage.c
  • 0 Utilisateurs l'ont trouvée utile
Cette réponse était-elle pertinente?

Articles connexes

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on ::1 [Cannot assign requested address] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...

How can I fix the error: Error [Contentfilter_Settings_Contentfilter]. Message [[QUARANTINEDIR] must be a valid directory?

This error means that Amavis was not installed correctly. Try running the Warden from the command...

How can I fix the error: host 127.0.0.1[127.0.0.1] said: 552 5.3.4 Declared message size (1208029 B) exceeds size limit for recipient?

You can set the message size limit for Amavis under Settings -> Policy Settings -> Misc...

How can I fix the error: milter-reject: DATA 451 4.7.1 Service unavailable - try again later?

Reject log In the Warden reject log you see the message: Service unavailable - try again later....