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?

Overview

After upgrading to Plesk Obsidian v18.0.76, the Dovecot mail server may experience repeated crashes when processing IMAP requests involving message movement or deletion. This issue is associated with a specific assertion failure in the Sieve plugin storage component.

Symptoms

The system logs will display the following panic 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 behavior is caused by a known defect in dovecot-pigeonhole v2.4.2, which was included with Plesk 18.0.76. The issue occurs when certain IMAP clients (including mobile applications and desktop clients such as Thunderbird) move or delete messages while the Sieve plugin is active. A conflict arises during the internal handling of the source mailbox reference, triggering an assertion failure. This defect has been documented in both the Dovecot community archives and Plesk support forums.

Resolution

The issue has been permanently resolved in Plesk Obsidian 18.0.76 Update 2. Applying the latest update is strongly recommended. If updating is not immediately feasible, apply the following configuration workaround to disable the problematic attachment detection option:

  1. Create a new Dovecot configuration file by executing the following command:
    // apply the fix
    echo 'mail_attachment_detection_options =' > /etc/dovecot/conf.d/999_fix_crash.conf
  2. Restart the Dovecot service to apply the changes:
    // restart dovecot
    systemctl restart dovecot

Troubleshooting & Verification

  • Verify that the Dovecot service is running without errors by executing: systemctl status dovecot.
  • Monitor /var/log/maillog for any recurring panic messages after applying the workaround.
  • If crashes persist, ensure no conflicting configuration files exist in /etc/dovecot/conf.d/ and schedule an upgrade to Plesk 18.0.76 Update 2 or later at the earliest opportunity.
  • dovecot, backtrace, Plesk 18.076, panic, imap-sieve-storage.c
  • 0 Người dùng thấy hữu ích
Câu trả lời này có hữu ích không?

Bài viết liên quan

How can I fix the error: Host '127.0.0.1' is not allowed to connect to this MariaDB server?

Overview This article provides resolution steps for the MariaDB connection error Host...

How can I fix the error: Parse error at /etc/clamav/clamd.conf Unknown option ScanImage?

Overview The clamav-daemon.service may fail to start due to unrecognized configuration...

How can I fix the error: The domain limit of this license key has been reached?

Overview The Admin and Pro editions of Danami products enforce a maximum domain limit within the...

After upgrading from Centos 7 to AlmaLinux 8 Amavis is treating mail with low scores as spam. How can I fix this?

Overview Following an upgrade from CentOS 7 to AlmaLinux 8, Amavis may incorrectly classify...

How can I fix empty mail log information in Warden?

Overview Warden relies on the systemd-journal to retrieve and display mail log information. If...