On 2013-06-08 5:01 PM, wie...@porcupine.org (Wietse Venema)
<wie...@porcupine.org (Wietse Venema)> wrote:
Charles Marcus:
On 2013-06-08 8:26 AM, Wietse Venema wrote:
[the same error on the virtual socket disappeared after a while]
The Postfix warranty does not cover file system corruption, so
I can only provide generic system repair suggestions.
If Solaris or *BSD, boot single-user mode and fsck the file system.
If Linux, do whatever your distro requires to force a full fsck.
If fsck does not resolve the issue, then the file system repair
program messed up the UNIX-domain sockets. Stop Postfix, remove the
'private' and 'public' queue directories, and restart Postfix.
If that doesn't help look for a spare computer system.
Thanks Wietse... but just to confirm...
If I delete these two directories, postfix will recreate them
automatically when I start it back up?
Yes. The "postfix start" command invokes "postfix check"
which creates missing directories.
This is good to know for future reference, but alas it didn't work for
me (same problem), however, I've determined that the problem only
manifests under very specific conditions, the main one being when I send
to a list that has only other lists as members (ie multiple nested
lists, using mailman, been working fine for years).
If I send to a list with only individual recipients, even dozens,
everything works fine and those warnings are not evident.
Also, if any of the list members have their vacation message enabled,
they will get the original message, but the vacation message gets stuck
with the 'mail transport unavailable'...
Otherwise, vacation messages are working properly (confirmed multiple
times, from both local and external senders).
I'm working on the mailman list to see if they can help.
Any other ideas welcome...
--
Best regards,
Charles
