ClamAV Best Practices - Debian

This is a discussion on ClamAV Best Practices - Debian ; Hello, What's the current best practice or consensus for running ClamAV on spam filter servers? Are people running from stable (etch), from backports, or from volatile? The DSA (1660) earlier this week made me start to wonder what people are ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: ClamAV Best Practices

  1. ClamAV Best Practices

    Hello,

    What's the current best practice or consensus for running ClamAV on spam
    filter servers? Are people running from stable (etch), from backports,
    or from volatile? The DSA (1660) earlier this week made me start to
    wonder what people are doing out there now. It's been a while since I
    dug into Clam on Debian.

    Steve


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Re: ClamAV Best Practices

    On Wed, Oct 29, 2008 at 08:27:58PM -0500, Steve wrote:
    > Hello,
    >
    > What's the current best practice or consensus for running ClamAV on spam
    > filter servers? Are people running from stable (etch), from backports,
    > or from volatile? The DSA (1660) earlier this week made me start to
    > wonder what people are doing out there now. It's been a while since I
    > dug into Clam on Debian.


    Volatile, here.

    --
    ``Fog In Channel: Continent Cut Off'' (newspaper headline, c. 1905)


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Re: ClamAV Best Practices

    Volatile. Clamav is exactly why volatile was conceived in the first place.

    --
    Keith Edmunds

    +-------------------------------------------------------------------------+
    | Tiger Computing Ltd | Helping businesses make the most of Linux |
    | "The Linux Specialists" | http://www.tiger-computing.co.uk |
    +-------------------------------------------------------------------------+


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Re: ClamAV Best Practices

    On Thu, Oct 30, 2008 at 7:40 AM, Keith Edmunds wrote:

    > Volatile. Clamav is exactly why volatile was conceived in the first place.




    +1 for Volatile here too... happily chugging away on about 10 of our
    bastions



    --
    $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'


  5. Re: ClamAV Best Practices


    Thanks for the replies. What about things like spamassassin and
    postgrey? I added the volatile repos to sources.list and went to
    install clamav but then I saw the message indicating '6 not upgraded' so
    I ran apt-get -u upgrade at which point I was given this:

    The following packages have been kept back:
    clamav clamav-daemon clamav-freshclam spamassassin
    The following packages will be upgraded:
    clamav-base postgrey spamc

    So should I manually install clamav clamav-daemon clamav-freshclam
    spamassassin from volatile?

    Just wondering what other people are doing or have in production.

    Steve


    On Thu, Oct 30, 2008 at 10:13:34AM +0000, Joel Merrick wrote:
    > On Thu, Oct 30, 2008 at 7:40 AM, Keith Edmunds wrote:
    >
    > > Volatile. Clamav is exactly why volatile was conceived in the first place.

    >
    >
    >
    > +1 for Volatile here too... happily chugging away on about 10 of our
    > bastions
    >
    >
    >
    > --
    > $ echo "kpfmAdpoofdufevq/dp/vl" | perl -pe 's/(.)/chr(ord($1)-1)/ge'



    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Re: ClamAV Best Practices

    On Thu, 30 Oct 2008 08:54:49 -0500, steves@braingia.org said:

    > So should I manually install clamav clamav-daemon clamav-freshclam
    > spamassassin from volatile?


    I'm not sure what you're asking. Should you install them manually? No: use
    "aptitude upgrade". Should you run the volatile versions at all? That's up
    to you; I'm assuming you understand the purpose of the volatile repository
    (if not, understanding that would be a good starting point).

    --
    Keith Edmunds

    +-------------------------------------------------------------------------+
    | Tiger Computing Ltd | Helping businesses make the most of Linux |
    | "The Linux Specialists" | http://www.tiger-computing.co.uk |
    +-------------------------------------------------------------------------+


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  7. Re: ClamAV Best Practices


    Er, yes, sorry. I understand both how to and the purpose of volatile.
    I'm more looking just to find out how other Internet providers are doing
    things with spamassassin, et. al, these days on Debian.

    Steve

    On Thu, Oct 30, 2008 at 09:07:51PM +0000, Keith Edmunds wrote:
    > On Thu, 30 Oct 2008 08:54:49 -0500, steves@braingia.org said:
    >
    > > So should I manually install clamav clamav-daemon clamav-freshclam
    > > spamassassin from volatile?

    >
    > I'm not sure what you're asking. Should you install them manually? No: use
    > "aptitude upgrade". Should you run the volatile versions at all? That's up
    > to you; I'm assuming you understand the purpose of the volatile repository
    > (if not, understanding that would be a good starting point).
    >
    > --
    > Keith Edmunds
    >
    > +-------------------------------------------------------------------------+
    > | Tiger Computing Ltd | Helping businesses make the most of Linux |
    > | "The Linux Specialists" | http://www.tiger-computing.co.uk |
    > +-------------------------------------------------------------------------+
    >
    >
    > --
    > To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  8. Re: ClamAV Best Practices

    On Thu, Oct 30, 2008 at 17:10, Steve wrote:
    >
    > Er, yes, sorry. I understand both how to and the purpose of volatile.
    > I'm more looking just to find out how other Internet providers are doing
    > things with spamassassin, et. al, these days on Debian.


    SA and ClamAV both from volatile, ClamAV updates via freshclam, SA
    updates via SA provided cron job.

    Works flawlessly.

    -Jim P.


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  9. Re: ClamAV Best Practices

    On Thu, Oct 30, 2008 at 08:54:49AM -0500, Steve wrote:
    > The following packages have been kept back:
    > clamav clamav-daemon clamav-freshclam spamassassin
    > The following packages will be upgraded:
    > clamav-base postgrey spamc
    >
    > So should I manually install clamav clamav-daemon clamav-freshclam
    > spamassassin from volatile?


    Manually, no. But it may be worth specifying to use the vol' repo,
    something like:

    apt-get install -t volatile clamav clamav-daemon clamav-freshclam

    might do for you.

    I'm not a fan of greylisting, per se.

    --
    ``If we do not conjure up a war into being,
    certainly no one else will do so.''
    (Alfred von Kiderlen-W�chter, German Foreign Minister, 1910)


    --
    To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread