[Mimedefang] local socket name/var/spool/MIMEDefang/mimedefang.sock unsafe

[Darin Riedlinger]

You may want to look at the /etc/rc.d/init.d/mimedefang start up script
(if you are using it start up mimedefang).  I received a few errors
similar to yours, I then uncommented the lines dealing with the sock
files.  It seemed to do the trick. 


SOCKET=$SPOOLDIR/mimedefang.sock
MX_SOCKET=$SPOOLDIR/mimedefang-multiplexor.sock

Darin


-----Original Message-----
From: mimedefang-bounces at lists.roaringpenguin.com
[mailto:mimedefang-bounces at lists.roaringpenguin.com] On Behalf Of Kayne
Kruse
Sent: Tuesday, November 11, 2003 5:27 PM
To: mimedefang at lists.roaringpenguin.com
Subject: RE: [Mimedefang] local socket
name/var/spool/MIMEDefang/mimedefang.sock unsafe

I got these if I restarted sendmail without restarting mimedefang after
fully shutting sendmail down.  In some cases, I've had to wait 15
seconds before MD was *safe* for sendmail to open those .sock's.
Perhaps this may help.

Kayne

> I'm still receiving these errors. The directories exist 
> and they have
> the correct permissions.
> 
> 
> Nov 11 15:14:05 rhlx01 sendmail[19753]: hABLE50V019753: 
> Milter (mimedefang):
> local socket name /var/spool/MIMEDefang/mimedefang.sock unsafe
> Nov 11 15:14:05 rhlx01 sendmail[19753]: hABLE50V019753: 
> Milter (mimedefang):
> to error state
> 

_______________________________________________
MIMEDefang mailing list
MIMEDefang at lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang