[Mimedefang] mimedefang.sock error

[Mail Administrator]

Stephen Smoogen wrote:
> Could you send the following extra info to the list just so that people 
> can help:
> 
> ls -lad /var/spool/MIMEDefang
> ls -lad /var/spool/MIMEDefang/*

[root at meow root]# ls -lad /var/spool/MIMEDefang
drwx------    2 defang   root         4096 Jan 26 16:30 
/var/spool/MIMEDefang
[root at meow root]# ls -lad /var/spool/MIMEDefang/*
-rw-rw-rw-    1 defang   defang      59258 Jan 26 16:30 
/var/spool/MIMEDefang/bayes_journal
-rw-rw-rw-    1 defang   defang      90112 Jan 26 16:29 
/var/spool/MIMEDefang/bayes_seen
-rw-rw-rw-    1 defang   defang   41705472 Jan 26 16:29 
/var/spool/MIMEDefang/bayes_toks
-rw-------    1 defang   defang          5 Jan 26 13:51 
/var/spool/MIMEDefang/mimedefang-multiplexor.pid
srw-------    1 defang   defang          0 Jan 26 13:51 
/var/spool/MIMEDefang/mimedefang-multiplexor.sock
-rw-------    1 defang   defang          5 Jan 26 13:51 
/var/spool/MIMEDefang/mimedefang.pid
srwx------    1 defang   defang          0 Jan 26 13:51 
/var/spool/MIMEDefang/mimedefang.sock

> 
> also what is the OS and what is the perl
Fedora Core 1
[root at meow root]# uname -a
Linux meow.srar.com 2.4.22-1.2149.nptlsmp SMP i686 athlon i386 GNU/Linux

[root at meow root]# perl -v
This is perl, v5.8.1 built for i386-linux-thread-multi

At this point, it is back to working. I shutdown sendmail and let it sit 
for a couple minutes (after Googling and finding a relevant entry in the 
comp.mail.sendmail archives) and when sendmail restarted it magically 
started working again.

Now, the only question is, "Why did it fall down in the first place?".

-Loren

> 
> 
> On Mon, 26 Jan 2004, Mail Administrator wrote:
> 
> 
>>Hi All,
>>
>>I came back from lunch today to hear people saying they can't send mail. 
>>Looking in the /var/log/maillog, I see two Bad Things(tm)
>>
>>#1:
>>Jan 26 13:42:12 meow sendmail[8791]: i0QLgCFl008791: Milter 
>>(mimedefang): local socket name /var/spool/MIMEDefang/mimedefang.sock unsafe
>>
>>In the archives, I see that the generic response is "make sure /var & 
>>/var/spool are owned by root and not group/world writable. Already been 
>>there and checked that.
>>
>>#2: (which I find no reference to in the Archives):
>>Milter (mimedefang): write(Q) returned -1, expected 5: Broken pipe
>>
>>Mimedefang.sock does not exist, I assume because mimedefang isn't really 
>>running. I further assume that is the reason for #2.
>>
>>MimeDefang is 2.39. Sendmail is 8.12.11. SA is 2.63. I'm using Sophos 
>>for antivirus.
>>
>>I'm now going to recompile sendmail.cf from an .mc file with no milter 
>>line, just so I can get mail flowing again. This system has been up for 
>>a week, working flawlessly. It just replaced a system that was in use 
>>for over one year, and in the end was MD 2.37/SM 8.12.10/SA 2.60/Sophos.
>>
>>Any help most certainly be appreciated.
>>
>>-Loren
>>
>>_______________________________________________
>>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
>>
> 
>