On Fri, Nov 19, 2010 at 09:55:28PM +0100, Jeroen Geilman wrote:
> On 11/19/2010 05:56 PM, Len Conrad wrote:
>> I did say "fixed by running postfix-install", wasn't clear that
>> postfix-install fixed postfix fail-to-run problem.
>>
>> fsck or whatever Linux RH does to fix filesystems apparently converted
>> "private/scan=" socket to "private/scan" dir, into which we got 2176
>> Maildir files as orphans.
>>
>
> "private/scan" is not a socket that belongs to a stock postfix
> distribution, so presumably this is a custom transport of some sort, maybe
> for a content_filter.
Fsck linked a directory into the wrong part of the file-system tree.
There used to a unix-domain socket there, but now a directory teleported
to that location. Their inode numbers got out of sync.
> If you simply rename the "private/scan" directory to something else,
> restarting postfix will re-create the socket if master.cf says it should.
>
Those messages were delivered to the maildir prior to it becoming
/var/spool/postfix/private/scan. I don't see why they need to be
"redelivered". Rather, some mailstore needs to be recovered,
or perhaps the directory contains files that were in the process
of being scanned by some filter...
--
Viktor.
