> On Mar 12, 2025, at 19:06, Viktor Dukhovni via Postfix-users > <postfix-users@postfix.org> wrote: > > On Wed, Mar 12, 2025 at 06:42:48PM -0700, Doug Hardie via Postfix-users wrote: > >> Then I went to find what's in /var/run/postfix. > > Normally, messages are in /var/spool/postfix, is this not the case on > your system?
Typo - they are in /var/spool/postfix. > >> There are 4 messages in defer/* and they match the mailq entries. > > The defer/ directory does not hold messages, it holds "bounce logs" for > messages whose delivery tempfailed. I'll have to check the contents then. I only checked the queue id in the file names. > >> However, there are 1179 messages in deferred/*. > > The deferred/ directory holds message queue files, they are well-formed, > and available for future delivery attempts, provided: > > - The queue filename is consistent with its inode number, encoded > as part of the name. > > - The "execute" bit is set in the owner permissions of the file > (mode 0700, not 0600). > > - The file modification time is not in the far future. > > You can examine these with "postcat -q <queueId>". > >> Most are dated in 2017, ... Why would there be 1175 messages in >> deferred with no defer entry? > > They probably don't have the execute bit set, and were put there > manually in ~2017 by someone who did not understand the queue > directory structure. Yes - no execute bit on any of them. They were not manually put there. I am the only one with access to the machine and I didn't do it. Since they are all quite old, I am not concerned about retaining them. This is the first time I have looked into the storage area. -- Doug _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
