Solved URGENT "spool file exim not found"

MisterM

Verified User
Joined
Jul 31, 2022
Messages
350
Hello
I use MailScanner to scan my messages.
Today I updated Exim and everything went more or less smoothly.
Since then I've had this message:
2023-11-23 21:16:18 1r6G7R-0000000H80h-3dZI Spool file 1r6G7R-0000000H80h-3dZI-D not found
I did this via @Richard G's topic
Link
But nothing happens, all my external messages don't go through and I'm at a total impasse.
Is this due to the update?
Kind regards
Mz
 
Response from DA support

Hello Michel,There are some problems with Message IDs after EXIM , because they changed their structure.So, you need to do the following:1. Run this command:exim_id_update -u2. Stop EXIM service:systemctl stop exim3. Set proper ownerships here:chown -R mail.mail /var/spool/exim4. Start EXIM service:systemctl start exim5. Check if you can do anything with your letters (Message ID), like removing one of them:exim -Mrm [MESSAGE_ID]or check headers:exim -Mvh [MESSAGE_ID]6. If you also use MailSCanner on your server, then pleas refer to this article: https://blog.configserver.com/?p=4028Thank you.
 
Let me reformat your message for the sake of clarity :

1. Run this command: exim_id_update -u
2. Stop EXIM service: systemctl stop exim
3. Set proper ownerships here: chown -R mail.mail /var/spool/exim
4. Start EXIM service: systemctl start exim
5. Check if you can do anything with your letters (Message ID), like removing one of them: exim -Mrm [MESSAGE_ID]or check headers: exim -Mvh [MESSAGE_ID]
6. If you also use MailSCanner on your server, then pleas refer to this article: https://blog.configserver.com/?p=4028Thank you.

So I assume this was the problem that me an other visitors had with EXIM here :

Weird that DA staff doesn't mentioned this anywhere @fln @DirectAdmin Support why is not any announcement made about this ?
 
Exim itself is fine with old and new message IDs, so migrating them to new format is entirely optional.

For external systems exim_id_update -u fixes message IDs.

Old message IDs can cause transient problems in DA GUI, but old format message IDs are being replaced by new ones as the time goes (messages are being delivered or removed due to old age). So the problem is really transient and not worth worrying about.

This only causes trouble for MailScanner.
 
This only causes trouble for MailScanner.
And for PFQueue as seen in another thread. But that's a very old app, don't know if the creator still will support it. But at least we now know what exactly is causing the issue.
 
If anyone is facing this issue, try updating MailScanner and MailScanner Front End, then run this command, which will re-queue emails from Exim

An automatic upgrade script is available at https://forum.directadmin.com/threads/automatically-update-configserver-products-for-da.69534/ Then run the re-queue script:

# Update MailScanner
cd /usr/src rm -fv msinstall* wget https://download.configserver.com/msinstall.tar.gz tar -xzf msinstall.tar.gz cd msinstall/ sh install.sh

# Update MSFE
cd /usr/src/ rm -fv msfe* wget https://download.configserver.com/msfeinstaller.tgz tar -xzf msfeinstaller.tgz perl msfeinstaller.pl ipv4 rm -fv msfeinstaller* /usr/mscpanel/mscheck.pl /usr/mscpanel/msrules.pl -i

# Requeue Emails Into Exim
/usr/msfe/msreq.pl
 
Last edited:
Let me reformat your message for the sake of clarity :



So I assume this was the problem that me an other visitors had with EXIM here :

Weird that DA staff doesn't mentioned this anywhere @fln @DirectAdmin Support why is not any announcement made about this ?
Active8 I had a huge problem, that's why I asked DA support.

Another response from support, which does not answer your concerns, but

There are some problems with Message IDs after EXIM , because they changed their structure.
 
Last edited:
Exim itself is fine with old and new message IDs, so migrating them to new format is entirely optional.

For external systems exim_id_update -u fixes message IDs.

Old message IDs can cause transient problems in DA GUI, but old format message IDs are being replaced by new ones as the time goes (messages are being delivered or removed due to old age). So the problem is really transient and not worth worrying about.

This only causes trouble for MailScanner.

@fln , Here is the answer from mailscanner support:

You need to upgrade MailScanner and MSFE (you can do this via the MSFE plugin) and then click the new "Force Requeue" button in the DA MSFE plugin.

This also affects their application, so update to be done.
 
Back
Top