Sorry again for my long silence. So, if you read this email, then my
mail delivery problem are fixed. Though I fear that I am still unable to
send emails to the debian mailinglists. I sent an email to
[email protected], but they too didn’t respond. Anyway, here
is what I would like to tell you:
It’s Andy Smith who found the explanation, less than 24 hours after my
post. His second post in the thread
<https://lists.debian.org/debian-user/2026/05/msg00044.html> gave the
correct explanation, which now helped me to find the solution.
The problem came because Systemd runs the monit service with
|ProtectSystem| set to |strict| and without adding |/var/spool/postfix/|
to |ReadWritePaths|.
Here is what I had in my |/usr/lib/systemd/system/monit.service|:
ProtectSystem=strict
ReadWritePaths=/run/ /var/lib/monit/ /var/log/
I just added |/var/spool/postfix/| to the list of read-write paths:
ReadWritePaths=/run/ /var/lib/monit/ /var/log/ /var/spool/postfix/
How did I know that it’s |/var/spool/postfix| where maildrop tries to
write to? Because the error message unfortunately specifies only the
relative path. I guessed that this path is specified somewhere in the
postfix configs, so I said:
# postconf | grep queue
Which returned a few settings, and one of them was:
queue_directory = /var/spool/postfix
My congratulations to the members of the debian-users list who found
this explanation without any further information from me!
Luc
On 5/4/26 15:34, Luc Saffre wrote:
(Sorry that you get my answer only now, I'm having delivery problems
with my [email protected] address, probably caused by DNS changes)
On 5/3/26 03:58, Andy Smith wrote:
Hi,
On Sun, May 03, 2026 at 02:50:47AM +0300, Luc Saffre wrote:
Soon after rebooting, I have the following message in my journal:
apr 28 08:07:30 lumi postfix/postdrop[992]: warning: mail_queue_enter: create
file maildrop/870989.992: Read-only file system
For some reason your filesystem has gone read-only. If I were you I'd be
looking further back in the logs to see if there is anything about that,
as I would expect there to be.
Yes, I could have attached this immediately, because indeed during
boot there are a lot of messages that I don't understand.
Here now a file made with "journalctl -b --no-pager > journal.txt".
But from the terminal as root I *can* write to the
/var/spool/postfix/maildrop directory:
# touch /var/spool/postfix/maildrop/x
# rm /var/spool/postfix/maildrop/x
Did I mention that this is a virtual private server?
Luc
