On 2011-03-05, Kevin Fenzi <kevin(a)scrye.com> wrote:
> and everything passes a trivial build and start test on RHEL6 --
> should I take over maintainership of these all, and submit them=20
> following the Join_the_package_collection_maintainers routine ?
Well, there's (at least) one additional monkey wrench in this:
recently we revamped clamav in EPEL.
We need to fix up amavisd-new to handle the new clamav.
So, if you could modify the package for the new clamav that would be
I just tested upgrading to this clamav from epel-6-testing, and can't
see any immediate problems. Any hints to what you expect there to be
of problems here ?
# rpm -qa|egrep 'amavis|clam'
and amavisd finds both the primary and secondary scanners on startup:
Mar 5 12:33:14 asav amavis: Using primary internal av scanner code for
Mar 5 12:33:14 asav amavis: Found secondary av scanner ClamAV-clamscan at
Haven't tested any scanning yet, because this RHEL6 based mailserver
isn't complete yet..
Additionally, if we can get one of the amavisd-new maintainers to
to mentor you, we can sponsor you that way. See:
I'll look into it, thanks!