[Mimedefang] md_syslog not working Mimedefang 2.71
I am rather embarrassed to say that after years of using MD, I have recently decided to bite the bullet and install a new Debian version and update all the associated tools that I use and for the life of me I cannot get md_syslog to work. I am not sure whether there are any tools to debug perl that I can usefully use in a text based SSH putty window so I use md_syslog for trace output in my other servers. I have this set in sendmail.mc define(`confMILTER_LOG_LEVEL', 14)dnl define(`confLOG_LEVEL', 14) I have the library libunix-syslog-perl installed. Somewhere there is a setting eluding me I am sure but I am damned if I can find it ! Can anyone please advise? Many thanks jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On Wed, 23 Apr 2014, Jon Rowlan wrote: >I am rather embarrassed to say that after years of using MD, I have >recently decided to bite the bullet and install a new Debian version and >update all the associated tools that I use and for the life of me I >cannot get md_syslog to work. Might be a stupid question, but anyway: are you sure that you have a syslog daemon installed. The sysklogd package seems to be removed from debian wheezy. A dist-upgrade from squeeze to wheezy removed the sysklogd package from serveral of my systems without installing a replacement. :-( I'm now using the rsyslog package on my wheezy systems. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: c.j.theunis...@differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
>> Might be a stupid question, but anyway: are you sure that you have a syslog daemon installed. Not really a stupid question Kees, I hadn't checked that :-) I am using Wheezy and this is a clean new install and not an upgrade. Syslogd is a virtual package as far as I can tell from Aptitude. It's the only thing listed when I search for sysklogd. ps reports that I have rsyslogd running .. 2004 1 0 Apr23 ?00:00:00 /usr/sbin/rsyslogd -c5 I get basic mail.log logging ok, just not the md_syslog extra detail which is why I raised logging level for Milters and sendmail. jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 24 Apr 2014, Jon Rowlan wrote: I get basic mail.log logging ok, just not the md_syslog extra detail which is why I raised logging level for Milters and sendmail. md_syslog() submits the logs to the syslog demon directly, check out _wrap_for_sys_syslog/_wrap_for_unix_syslog in mimedefang.pl. Maybe you mimmick / test syslog with the code of mimedefang.pl and see where the logs are going. Maybe you need to enabled the "tag" or everything is in same generic log file. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU1izNlGgR0+MU/4GAQK+jAf8C+LT5GqCUm8Y2Bh6Tu/+TpgSWdDBdhX2 uDRc9XwvTRTNC9QbP2TzEE6jVDRyohtPPkYRZea94QDB90JwazTiRpGrdScrSgy0 FpOmOXgX9hA4WI/xTBd+UvXZXXRqdXRW3cDuVVGcSGJdR6w1Lc8RpRpaULuKL2FU rB8Z2eLwDaqVPgGryE+xvRBrxPLo8ScBv4nCMOyM3DZeGTO6lhWRqyRe/wJ7nMLj UfRGF+pXPXUiYe6YLgY2axQLZigvhbx9qJzbqb2+fHaOntL7kOBW1PXiljBCaW6X oSLsgFHBQGzYZ735EPfTv9VrUPoIXeeugkooRAYdjYOliZiSD5ZnjQ== =HVhp -END PGP SIGNATURE- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
>> Maybe you mimmick / test syslog with the code of mimedefang.pl and see where the logs are going. Maybe you need to enabled the "tag" or everything >> is in same generic log file. I am struggling to get this working, whilst I am happy with my basic knowledge of Perl fiddling with the filter, I am not knowledgable enough about Perl to test the use of SysLogD. Everything I have tried just doesn't work. Can anyone give me a snippet or two that will test the two types of syslog that I may have in place, it would really help me out as I am very keen to get MD working so I can get my relat in place. Thanks all. jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
You are a star Steffen, thank you. I was getting very close to this with my hacking, its interesting to see how to use Perl outside of MD. This script creates entries in mail.log fine. Apr 25 11:03:47 mimedefang.pl[23318]: Unix::Syslog TEST warning Apr 25 11:03:47 mimedefang.pl[23318]: Sys::Syslog TEST info Apr 25 11:03:47 mimedefang.pl[23318]: Sys::Syslog TEST warning But MD does not, is there a logging level setting somewhere that I am missing? Thanks again for the code ... much appreciated. jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
It seems that my interpretation of the symptoms is incorrect. It wasn't that md_syslog was not working ... more that my filter was in the wrong place and never called! Can someone please confirm, is it possible to remove the block of text added by MD which has the link to the MD web site http://www.roaringpenguin.com/mimedefang/enduser.php3 ? I prefer the previous version generic message. Thanks for the help all, jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
Please ignore me. Silly question, I was not looking in the right place. jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/25/2014 1:23 PM, Jon Rowlan wrote: > I prefer the previous version generic message. Previous? You're running MD 2.71 which is quite "previous", itself. :) Currently (as of 2.74) the default is: X-Scanned-By: MIMEDefang 2.74 on 10.1.1.1 (Where 10.1.1.1 is whatever IP address MD is running on) As the mimedefang man page states, you can use one of these options to change that behavior: -x string Add string as the content of the X-Scanned-By: header. If you set string to the empty string (i.e. -x ""), then no X-Scanned-By: header will be added. -X Do not add an X-Scanned-By: header. Specifying -X is equivalent to specifying -x "". Although 2.71 is 4 years old, the situation is probably similar. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
> Previous? You're running MD 2.71 which is quite "previous", itself. :) Yes, sadly I am using a Debian Distro, it's a little disappointing to think that I bite the bullet and go for the very latest "Wheezy" which in the last few months went from unstable to stable (i.e. very latest) and MD that is part of it is 4 years old! Its difficult to assess just how much has happened in 4 years ... Should I go for a compile my own do you think Matt? jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/25/2014 2:06 PM, Jon Rowlan wrote: > Should I go for a compile my own do you think Matt? I suppose that, if you don't have problems, 2.71 is fine. Attached is the change log since 2.71 to help you decide. OTOH, it's not difficult to compile & install MIMEdefang, as long as you have some familiarity with the general process of working with Autoconf and Make files, etc.. The hard part will be the perl module dependencies, as some of what you have may be too old to work with the latest MD. In that case, there's always CPAN. But that adds extra hassle. Personally, on my mail servers, I always build sendmail, mimedefang, spamassassin, and clamav from source. (Even if the distro has up-to-date packages.) My advice would be to stick with what your distro gives you, unless you encounter problems, or just want to have fun installing 2.74 yourself. :) WARNING: Before upgrading MIMEDefang, please search this file for *** NOTE INCOMPATIBILITY ** to see if anything has changed that might affect your filter. 2013-05-27 David F. Skoll * MIMEDefang 2.74 RELEASED 2013-05-25 David F. Skoll * Increase buffer size for md-mx-ctrl responses. 2013-01-22 David F. Skoll * Close input file handle in append_to_html_part. Bug found by Kees Theunissen. 2012-09-17 David F. Skoll * Add action_add_entity function. * Simplify code in action_replace_with_warning. 2012-06-18 David F. Skoll * Remove obsolete text from man page. * Avoid deprecated "defined(@array)" construct. 2012-03-27 David F. Skoll * Implement new "load1" md-mx-ctrl command which gives statistics in more useful format than "load" * get_mx_ip_addresses: Treat MX records of '', '.', '0', '0.', '0 .' and '0 ' as bogus. * watch-multiple-mimedefangs.tcl: Major improvements; see the new -n, -r, -s and -t command-line options. 2012-02-07 David F. Skoll * Add rcpt_addr, rcpt_host and rcpt_mailer to default set of macros that we ask for. * Log Sendmail queue ID in more places. * Remove dead "connect_to_socket" routine in mimedefang.pl * Do not invokve smfi_setsymlist unless "-y" option to mimedefang is given. smfi_setsymlist leaks memory in versions of Sendmail prior to 8.14.4. 2012-01-23 David F. Skoll * MIMEDefang 2.73 RELEASED 2012-01-20 David F. Skoll * Create /var/spool/MIMEDefang with mode 0750 by default. 2012-01-18 David F. Skoll * Make the -G option cause files created by mimedefang to be group-readable. Add the new MD_ALLOW_GROUP_ACCESS init script variable. 2011-12-21 David F. Skoll * Make the multiplexor snoop in on communications and save the Sendmail queue-ID for logging purposes. It logs the queue ID when logging a slave's STDERR. 2011-12-12 David F. Skoll * Make configure.in check whether or not libmilter requires -lldap. * Fix Graphdefang to handle new md_syslog output style. * Always check return code from chdir() in mimedefang.pl. In certain cases on large and heavily-loaded servers, if the chdir() failed MIMEDefang would end up working in the wrong directory with attendant chaos. * Add "-G" option to mimedefang and mimedefang-multiplexor. This makes their sockets group-readable and group-writable. * Pass along the client port number, server IP address and server port number to all filter functions. This feature was sponsored by Scayl. 2011-07-20 David F. Skoll * MIMEDefang 2.72 RELEASED 2011-06-20 David F. Skoll * MIMEDefang 2.72-BETA-2 * The "make unstripped" target has disappeared. Instead, use: make INSTALL_STRIP_FLAG='' * The RPM_INSTALL_ROOT make variable has disappeared. Instead, use the standard DESTDIR: make install DESTDIR=/some/dir * In mimedefang.c, truncate overlong responses from the multiplexor. Also sanitize replies so "\r" doesn't get fed to smfi_setmlreply. * If a slave process replies with a very long reply, have the multiplexor consume (and discard) the excess input so the multiplexor-to-slave protocol does not become de-synchronized. 2011-06-16 David F. Skoll * When mimedefang becomes a daemon, have it wait for a "go/no-go" message from the child before exiting. This should eliminate race conditions whereby the MTA starts before the milter socket is present. * Revert change in 2.72-BETA-1 that passed client port number. It was a hack; we need a proper way to pass largish amounts of information to the filter and that will have to wait for a major reworking of MIMEDefang. 2010-11-01 David F. Skoll * MIMEDefang 2.72-BETA-1 * Avoid run-time errors from Unix::Syslog on some platforms
Re: [Mimedefang] md_syslog not working Mimedefang 2.71
On 4/25/2014 2:26 PM, Matt Garretson wrote: Personally, on my mail servers, I always build sendmail, mimedefang, spamassassin, and clamav from source. (Even if the distro has up-to-date packages.) Amen... I love package-based systems to get up and running and maintain 99.9% of the server but for the "reason to live" programs, that's best left to source or your own custom packages. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
I am very tempted to try a source compile once I have a stable platform on my live server. One thing that seems to still hamper me is the permissions issues I get. I like to use MD / SA / Clam. I still suffer on my old servers with Freshclam and the fact that some of the clam Daemons are run as user Defang. What I would like to do is standardise the combination. Is it possible to add defang and clamav users to a group and apply group permissions so these can all talk happily together rather than me have to change .conf file username settings .. So that I can update each package independantly and quickly integrate? I could write a single script to set folder perms for the group permission then. Does anyone have any "up and running faster" tips for this scenario? jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/25/2014 3:10 PM, Jon Rowlan wrote: > Is it possible to add defang and clamav users to a group and apply group > permissions so these can all talk happily together rather than me have > to change .conf file username settings .. Yes. All you have to do is add the clamav user to the defang group, and make sure your MIMEdefang spool dir has permissions equivalent to this: drwxr-x--- 9 defang defang 260 2014-04-25 15:36 /var/spool/MIMEDefang/ My spool dir is a tmpfs so I put those permissions into fstab to ensure they are set at mount time. I also use the -G option for MIMEdefang, but I can't remember if it's necessary. If you have selinux enabled, you may have other issues. But I always disable it. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
> Yes. All you have to do is add the clamav user to the defang group, and make sure your MIMEdefang spool dir has permissions equivalent to this: > drwxr-x--- 9 defang defang 260 2014-04-25 15:36 /var/spool/MIMEDefang/ I did that and cannot get the daemonised clam working as there still seems to be a permissions issue but I see that the command line clamav is running fine and picking up EiCar. That's good, I presume that is sufficient? > I also use the -G option for MIMEdefang, but I can't remember if it's necessary. I can't find any reference to -G in man of mimedefang, mimedefang-multiplexor or mimedefang-filter. > If you have selinux enabled, you may have other issues. But I always disable it. apparently (as far as I can see from articles I have found) selinux is installed in Debian Wheezy but disabled. Thanks Matt! jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/25/2014 1:49 PM, Matt Garretson wrote: > I also use the -G option for MIMEdefang, but I can't remember if > it's necessary. That option was introduced in 2.73. I don't think 2.71 requires it. Nels Lindquist ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/26/2014 5:50 AM, Jon Rowlan wrote: > I did that and cannot get the daemonised clam working as there still > seems to be a permissions issue but I see that the command line clamav > is running fine and picking up EiCar. That's good, I presume that is > sufficient? Well, if you'll be scanning any significant amount of email, you'll definitely want to get clamd up & running. Although MIMEdefang is able to find and use the stand-alone command-line scanner (clamscan), that would be much less desirable than having clamd up, allowing MD to talk directly to the clamd socket. This would save a lot of overhead for each scan. Nels wrote in another reply that your version of MD does not have the -G option, so the advice I gave Friday might not work. You might have to make clamd run as the defang user. To do this, you'd have to edit your clamd.conf and your freshclam.conf, as well as checking the permissions of your clamav database directory. But, before doing that, it might be a good idea to first get clamd running so that clamdscan works. After that, then you can work on getting the permissions right for MIMEDefang to use clamd. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
> Well, if you'll be scanning any significant amount of email, you'll definitely want to get clamd up & running. > Although MIMEdefang is able to find and use the stand-alone command-line scanner (clamscan), that > would be much less desirable than having clamd up, allowing MD to talk directly to > the clamd socket. This would save a lot of overhead for each scan. Clamdscan works fine at the command line, its just that I am struggling to get the clam scan of any kind working via the socket. > Nels wrote in another reply that your version of MD does not have the -G option, so the advice I gave > Friday might not work. You might have to make clamd run as the defang user. To do this, > you'd have to edit your clamd.conf and your freshclam.conf, as well as checking the > permissions of your clamav database directory. What does the -G do, I wonder whether I should upgrade to get the latest and greatest. But initially I want to get a distro version working ... Thanks Matt, jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On 4/28/2014 3:27 PM, Jon Rowlan wrote: > Clamdscan works fine at the command line, its just that I am struggling > to get the clam scan of any kind working via the socket. Do you have AllowSupplementaryGroups yes in your clamd.conf and freshclam.conf? ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On Mon, 28 Apr 2014, Jon Rowlan wrote:
>Clamdscan works fine at the command line, its just that I am struggling
>to get the clam scan of any kind working via the socket.
Did you configure MIMEdefang somehow to use that socket?
This is my /etc/mail/mimedefang.pl.conf on a debian server:
- 8< ---
# Mimedefang configuration file
# This file is a perl file which gets 'require'd from mimedefang
# You can set the virus-scanner paths etc.
# See mimedefang.pl
$Features{'Path:QUARANTINEDIR'} = '/var/spool/MD-Quarantine';
$Features{'Virus:CLAMAV'} = '/usr/bin/clamscan';
$Features{'Virus:CLAMD'} = 1;
$ClamdSock = '/var/run/clamav/clamd.ctl';
# DO NOT delete the next line, or Perl will complain.
1;
- 8< ---
Debian modified /usr/bin/mimedefang.pl to 'require' this file.
Regards,
Kees Theunissen.
--
Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724
Dutch Institute For Fundamental Energy Research (DIFFER)
e-mail address: c.j.theunis...@differ.nl
postal address: PO Box 1207, 3430 BE Nieuwegein, NL
visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
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] md_syslog not working Mimedefang 2.71
> Did you configure MIMEdefang somehow to use that socket? > This is my /etc/mail/mimedefang.pl.conf on a debian server: Thanks Kees, I have that file, I will try this out. jON ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. 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] md_syslog not working Mimedefang 2.71
On Mon, 28 Apr 2014, Jon Rowlan wrote:
>Clamdscan works fine at the command line, its just that I am struggling
>to get the clam scan of any kind working via the socket.
Did you configure MIMEdefang somehow to use that socket?
This is my /etc/mail/mimedefang.pl.conf on a debian server:
- 8< ---
# Mimedefang configuration file
# This file is a perl file which gets 'require'd from mimedefang # You
can set the virus-scanner paths etc.
# See mimedefang.pl
$Features{'Path:QUARANTINEDIR'} = '/var/spool/MD-Quarantine';
$Features{'Virus:CLAMAV'} = '/usr/bin/clamscan';
$Features{'Virus:CLAMD'} = 1; $ClamdSock = '/var/run/clamav/clamd.ctl';
# DO NOT delete the next line, or Perl will complain.
1;
- 8< ---
Debian modified /usr/bin/mimedefang.pl to 'require' this file.
I have just discovered that I do not have clamscan on my server but
clamdscan appears to work from the command line.
So I think that means that I have a correctly configured daemonised clam
install and clamdscan will using the socket I presume?
Thanks Kees,
jON
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
