[Mimedefang] Re: mimedefang error mimedefang.sock unsafe??

James Ebright jebright at esisnet.com
Tue Mar 22 09:47:42 EST 2005


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

On Tue, 22 Mar 2005 06:19:46 -0800, Johann wrote
> Troy R. LeBouef wrote:
> <snip>
> 
> > [root at ns1 spool]# ls -all MIMEDefang/
> > total 36
> > drwx------   2 defang defang 4096 Mar 21 18:21 .
> > drwxr-xr-x  17 root   root   4096 Mar 21 12:14 ..
> > -rw-r-----   1 defang defang    6 Mar 21 18:21
> > mimedefang-multiplexor.pid
> > srw-------   1 defang defang    0 Mar 21 18:21
> > mimedefang-multiplexor.sock
> > -rw-r-----   1 defang defang    6 Mar 21 18:21 mimedefang.pid
> 
> My directories have the same files ... but all have the x bit set.
> 
> -Johann
> _______________________________________________
> Visit http://www.mimedefang.org and http://www.canit.ca
> MIMEDefang mailing list
> MIMEDefang at lists.roaringpenguin.com
> http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


--
EsisNet.com Webmail Client




More information about the MIMEDefang mailing list