[Mimedefang] Start order for sendmail, MD and Clam
Is there a particular order in which I should start sendmail, MD and Clam? That is, are there any dependencies, or reason that one should be running before the other (seems that sendmail will gripe about a missing socket if MD is not running, so I start MD first, but what about Clam?) Sendmail v8.13.4 MIMEDefang v2.51 Clam v0.85 Dirk ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] Re: [Resolved}: Adding clamd *after* install
Hello, all. I asked:
>Date: Mon, 6 Jun 2005 13:24:41 -0400 (EDT)
>
>Running configuration:
> Novell SUSE Linux Enterprise Server 9
> Sendmail v8.13.4
> MIMEDefang v2.51
>
> For various reasons, I was not able to build and install ClamAV
>until MD was already up and running. ClamAV v0.85 has been built and
>installed. I've edited clamd.conf to use the MD socket directory and
>
>
> If I use "perl mimedefang.pl -features", ClamD shows as disabled. How
>do I get MD to recognize and use clamd? Do I have to rebuild and
>reinstall MIMEDefang?
Thanks to everyone who replied. I ended up adding some lines to
mimedefang-filter as suggested by the replies below. I felt this was a
better idea than hacking the mimedefang.pl script - that if, add the
function via a configuration file change as opposed to altering the code
itself (altho I'm sure changing mimedefang.pl would work well).
>--
>From: Kenneth Porter <[EMAIL PROTECTED]>
>
>I have this near the top of my mimedefang-filter:
>
># manually override compile-time features, clamd is installed
>$Features{'Virus:CLAMD'} = 1;
>$ClamdSock = "/var/run/clamav/clamd.sock";
>--
Dirk
___
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list
MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] MXCommand: connect: Connection refused: Is multiplexor running?
Hi all, We're seeing repeated instances of MXCommand: connect: Connection refused: Is multiplexor running? [...] mfconnect: Error communicating with multiplexor on our content filtering farm. Once MD starts logging these it never seems to recover, and while it still processes some mail, has to be restarted to get the logging back under control and process mail at normal speed. >From walking through the source code, we're getting as far as receiving the SMTP client connection, and Sendmail's initialising the filter (the start of srvrsmtp.c:smtp()). The filter function, mfconnect() calls down to MXCommand() (via MXCheckFreeSlaves()), which tries to connect(), and fails. The failure bubbles back up to Sendmail, which sets the tempfail flag, and responds to the client's SMTP verbs with 4xx errors. So far, so understood. What I don't understand is why this is happening. We start mimedefang-multiplexor with '-I 50' to specify a ridiculously high socket backlog. If I run "md-mx-ctrl load" while this is happening the multiplexor reports somewhere between 5 and 7 messages being processed per second -- nowhere near the 50 backlog limit. Rooting around Google has turned up a few similar report, with the suggestion to increase the listen backlog. Which we've done. All this is with MD 2.48 on Solaris 8. Any thoughts? Does this sound familiar to anyone? N ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Start order for sendmail, MD and Clam
Dirk the Daring wrote: Is there a particular order in which I should start sendmail, MD and Clam? That is, are there any dependencies, or reason that one should be running before the other (seems that sendmail will gripe about a missing socket if MD is not running, so I start MD first, but what about Clam?) Sendmail v8.13.4 MIMEDefang v2.51 Clam v0.85 Dirk, I start mine in the order of: CLAMD MIMEDefang Sendmail considering the logic that MIMEDefang makes calls that may require CLAMAV's resources (in this case clamd), and sendmail makes calls that may require MIMEDefang's resources, it seemed appropriate to ensure that those resources available before any chance of them being called. subsequently, i shut them down in reverse order. HTH Alan ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] MXCommand: connect: Connection refused: Is multiplexor running?
Nik Clayton wrote: > MXCommand: connect: Connection refused: Is multiplexor running? > mfconnect: Error communicating with multiplexor > What I don't understand is why this is happening. We start > mimedefang-multiplexor with '-I 50' to specify a ridiculously high socket > backlog. If I run "md-mx-ctrl load" while this is happening the > multiplexor reports somewhere between 5 and 7 messages being processed per > second -- nowhere near the 50 backlog limit. If md-mx-ctrl load works, but the milter is having trouble, could it be that the milter is running out of file descriptors? (Actually, in this case, I'd expect the socket call to fail and not the connect call, but I seem to recall some weird condition whereby socket returned a descriptor greater than 1024, and the connect call didn't like that.) Regards, David. ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] (no subject)
Hi, I've just updated my mimedefang from 2.51 to 2.52. I can see it compile cleanly, and it appears to build the mulitplexor as well. However, then I start it up, I see: bash-2.05# ./mimedefang start Starting mimedefang-multiplexor: mimedefang-multiplexor compiled without support for embedded perl. Ignoring -E flag. [ OK ] Starting mimedefang:[ OK ] It's fine if I roll back to 2.51. I've checked the permissions, and everything looks correct, I've even tried to force configure to use it. Still no joy. Can anyone shed any light ? Richard -- Richard Whelan Senior Systems & NMS Administrator Pipex Communications Direct: 01865 381568 Mobile: 07786 276020 www.pipex.net This e-mail is subject to: http://www.pipex.net/disclaimer.html ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Re: [Resolved}: Adding clamd *after* install
On Tue, 7 Jun 2005, Dirk the Daring wrote: Thanks to everyone who replied. I ended up adding some lines to mimedefang-filter as suggested by the replies below. I felt this was a better idea than hacking the mimedefang.pl script - that if, add the function via a configuration file change as opposed to altering the code itself (altho I'm sure changing mimedefang.pl would work well). Sure it's better to change a config file, but if you were to reconfigure and reinstall MIMEDefang, you would end up with a different mimedefang.pl not a different config file. So I'm not sure I'd consider it the same as changing source code...but whatever works for you. :) Matt ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Start order for sendmail, MD and Clam
alan premselaar wrote: CLAMD MIMEDefang Sendmail considering the logic that MIMEDefang makes calls that may require CLAMAV's resources (in this case clamd), and sendmail makes calls that may require MIMEDefang's resources, it seemed appropriate to ensure that those resources available before any chance of them being called. I suspect the order of ClamD and MIMEDefang doesn't matter, as long as they're both loaded before Sendmail, since (in theory) MIMEDefang won't need access to ClamAV until Sendmail hands it a message. Conceptually, though, it is cleaner to start Clam first. -- Kelson Vibber SpeedGate Communications ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Start order for sendmail, MD and Clam
I use the same order and additionally put a sleep statement before starting the sendmail SMTP daemon. I do this because MD takes a number of seconds to fully startup and load. I just monitored the log to find what value to sleep() for. Reasonably modern hardware may not have a need to sleep before starting sm. ~Jason -- ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Start order for sendmail, MD and Clam
Kelson wrote: > I suspect the order of ClamD and MIMEDefang doesn't matter, as long as > they're both loaded before Sendmail, since (in theory) MIMEDefang won't > need access to ClamAV until Sendmail hands it a message. Conceptually, > though, it is cleaner to start Clam first. The start order isn't that critical. If you start Sendmail first, you'll get a few tempfails and complaints about an unsafe socket file (DUMB error message), but eventually things should settle down. Regards, David. ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] [Resolved] Start order for sendmail, MD and Clam
>From: alan premselaar <[EMAIL PROTECTED]> > >>Is there a particular order in which I should start sendmail, MD and >> Clam? That is, are there any dependencies, or reason that one should be >> running before the other (seems that sendmail will gripe about a missing >> socket if MD is not running, so I start MD first, but what about Clam?) > >CLAMD >MIMEDefang >Sendmail Thanks, Alan. That's what I'm looking for. I'm writing my start scripts to check for dependencies accordingly (Clam starts first, doesn't check for MD or sendmail; MD starts next, checks for clam before starting; sendmail starts last, checks for MD before starting). The "stop" scripts are a little more problematic. I've decided that for stopping, say, clam, it should check for MD being run, generate a warning if MD is up, but still proceed with the stop even if MD is running. Same for MD with relation to sendmail. Dirk ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] [Resolved] Start order for sendmail, MD and Clam
Dirk the Daring wrote: ...snip... The "stop" scripts are a little more problematic. I've decided that for stopping, say, clam, it should check for MD being run, generate a warning if MD is up, but still proceed with the stop even if MD is running. Same for MD with relation to sendmail. Dirk, Yeah, this could be problematic. Especially in my case where if I make changes to my filter (not very frequently) or spamassassin rules (more frequently) i'll restart mimedefang but not necessarily sendmail or clamd. anyways, glad to help. Alan ___ Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
