As far as directories go.. the "x" bit simply means you can get a directory
listing if you have privledges. For files it turns on execute allowing the
file to be run as a program. I do not believe that should affect the operation
of MimeDefang in any way as MD does not need the x bit on the directory as it
already knows what the files are called and it only needs read write on the
sockets.
For some reason you are not getting the mimedefang.sock created. I would double check your config files and make sure you dont have MD trying to create it elsewhere. You might also want to double check your /var/spool file system and make sure its not an underlying issue like bad inode, out of space, out of inodes, etc.
Jim
I just encountered this same problem on a system that has been running flawlessly until today.
I was seeing a bunch of
Mar 24 09:44:04 mail mimedefang-multiplexor[21236]: Killing busy slave 17 (pid 10445): Busy timeout
Mar 24 09:44:04 mail mimedefang[21249]: Error from multiplexor: ERR Filter timed out - system may be overloaded (consider increasing busy timeout)
and
Mar 24 09:44:24 mail mimedefang[21249]: mfconnect: No free slaves
errors in my mail log.
after trying to restart sendmail and mimedefang I was getting the /var/spool/MIMEDefang/mimedefang.sock unsafe! error message and after doing some research realized that the file is not being created.
my /var/spool/MIMEDefang directory is a 2GB tmpfs with proper permissions and the mimedefang-multiplexor.sock file is properly being created.
I'm a little perplexed at this moment as to what could cause it to fail seemingly suddenly.
any insight would be extremely useful.
alan _______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
