SUMMARY: MailScanner

From: Dirk Kleinhesselink (dkleinh_at_phy.ucsf.edu)
Date: 06/27/03

  • Next message: Jonathan Williams: "DNS question" 
    Date: Fri, 27 Jun 2003 08:54:51 -0700 (PDT)
To: tru64-unix-managers@ornl.gov

    I finally got MailScanner working with sophos antivirus on Tru64 5.1A.
    The problem was that the Perl module file, Sys::Syslog.pm that is in the
    perl 5.6.0 distribution shipped with 5.1A, at least, is broken. I was
    able to get MailScanner going by changing the calls to the syslog utility
    from 'unix' to 'inet'. I probably could've also fixed by upgrading to a
    newer perl release. My fix was to modify the MailScanner perl library
    module, Log.pm (/opt/MailScanner/lib/MailScanner/Log.pm) and change the
    line:
    eval { Sys::Syslog::setlogsock('unix'); } # This may fail!
    to:
    eval { Sys::Syslog::setlogsock('inet'); } # This may fail!

    I had responses from Nikola Milutinovic, who advised the use of AMaVisD,
    instead of MailScanner -- uses less system resources than MailScanner and
    also Sophie as a free alternative to the commercial Sophos.

    Also Richard Mollel who is using MailScanner on 4.0g with Perl 5.8.

    I'm using Tru64 5.1A and MailScanner 4.21-9.

    Dirk Kleinhesselink

    > Is anybody successfully running MailScanner ? I have a tru64 5.1A cluster
    > running sendmail-8.11.6 (patched) and I'd like to use MailScanner to pass
    > mail through Sophos. I've installed MailScanner (version 4.21-9) and
    > sophos according to directions. Sophos seems to be working OK if I run
    > sweep against a directory, so I believe it to be installed OK. However,
    > when I start MailScanner, it seems to start OK and does not give me any
    > error messages, yet it never seems to process anything from the incoming
    > mail queue, nor can I find any informational messages from it -- I just
    > see one or two mailscanner processes and that's it. I tried to turn on
    > debugging by setting debug = yes in the MailScanner.conf file and then I
    > got this when I tried to run it:
    >
    > # ./check_mailscanner
    > Starting MailScanner...
    > In Debugging mode, not forking...
    > Your vendor has not defined the Sys::Syslog macro _PATH_LOG at
    > /usr/lib/perl-5.6.0/lib/5.6.0/alpha-dec_osf/Sys/Syslog.pm line 277.
    >
    > Thanks for any help,
    >
    > Dirk Kleinhesselink
    >

  • Next message: Jonathan Williams: "DNS question"

    Relevant Pages

    • Re: dependency problems w/mailscanner
      ... Now apt is complaining about unmet perl ... >> Is there some way to tell mailscanner to forget about the perl rpms ... perfectly functional perl + many extra modules installation. ... mailscanner has unresolved dependencies for perl rpms ...
      (RedHat)
    • Re: dependency problems w/mailscanner
      ... mailscanner has unresolved dependencies for perl rpms ... > even though all of the required perl modules are installed and working ... ended up with two Perl installations and had to remove one. ...
      (RedHat)
    • Re: dependency problems w/mailscanner
      ... > I don't think that MailScanner looks for Perl rpm's per se. ... For some reason ... > ended up with two Perl installations and had to remove one. ... Wrt MailScanner, it does seem to think it needs a pile of perl rpm ...
      (RedHat)
    • Re: Suggestion for anti-spam
      ... Have a look at MailScanner with SpamAssassin: ... Both OSS, both use Perl, both have no licesing restrictions. ... purchase commercial support for MailScanner. ...
      (comp.unix.solaris)
    • Re: Unix Anti-Virus Recommendations
      ... I use Mailscanner with McAfee/NAI virus scanner with Sendmail and it works ... I used Sophos for a while, but wasnt as happy with it as I am with ... On Mon, 4 Mar 2002, Mark Baldwin wrote: ...
      (Focus-SUN)