Messages stuck in Exim queue after update to cpanel-exim-4.100 when MailScanner is enabled

Symptoms

After updating to cpanel-exim-4.100, messages are stuck in the Exim queue, and errors similar to the following are present in the Exim log.

# 2026-09-11 10:26:27 1x4y0b-0000000H6J0-2x5y Spool file 1x4y0b-0000000H6J0-2x5y-D not found

Cause

The messages are failing to send because they have been moved to a different spool directory than MailScanner expects. It was discovered that the MailScanner Exim version check is failing to detect the correct Exim version. Since the version check fails to match the correct Exim version, the messages in the queue are not found, and MailScanner then tries to use the old-style queue used by an older Exim version.

Resolution

cPanel does not provide MailScanner or MailScanner Front-End (MSFE) tools, and ConfigServer has been shut down. MailScanner and MSFE should be uninstalled.

There are two main options to resolve the issue.

• Remove MailScanner and fix the Exim Queue ( Tab 1 )
• Update MailScanner manually to resume processing emails ( Tab 2 )

Note: It may be necessary to work with your system administrator to fully uninstall the software and restore emails.

After removing MailScanner, the emails in the queue need to be moved so Exim can deliver them.

# Update:

The community has found a way to workaround this problem by editing the MailScanner version check ( Tab 2 ).