We are running the new version of clamav with the milter enabled and
everything is functioning properly. I just have a question.
Is there a way that one can with the new milter clean and then accept
mails that are infected with a virus or can they only do one option
like accept or quarantine?
On 2009-03-31 15:26, Ebrahim Abrahams wrote:
> We are running the new version of clamav with the milter enabled and
> everything is functioning properly. I just have a question.
>
> Is there a way that one can with the new milter clean and then accept
> mails that are infected with a virus or can
Folks,
ClamAV 0.95 will include a completely new clamav-milter. You can read
more about it on the ClamAV Blog at clam-av.blogspot.com.
We really would like feedback on it, please let us know what you think!
-Nigel
--
Nigel Horne, nigel.ho...@sourcefire.com
Director of Product Management (Clam
Since upgrading to clamav 0.95 I am getting the log message "fd[10]: OK"
appearing in my clamav log file. Clamav is configured to log to syslog.
Also, I am logging clean messages.
Here is a section of my log file that shows the message appearing a
couple of times and then syslog buffering it:
Vincent Aniello wrote:
> Since upgrading to clamav 0.95 I am getting the log message "fd[10]: OK"
> appearing in my clamav log file. Clamav is configured to log to syslog.
> Also, I am logging clean messages.
Hi Vincent,
Turn off LogClean in clamd.conf.
--acab
__
aCaB wrote:
> Turn off LogClean in clamd.conf.
While I could do that, I would prefer the feature to work correctly. Is
anyone else having this issue with 0.95? Is this a known bug that will
be fixed in a future version?
Thanks.
--Vincent
Disclaimer: Any references to Pipeline performance co
On 2009-03-24 15:22, Vincent Aniello wrote:
> aCaB wrote:
>
>> Turn off LogClean in clamd.conf.
>>
>
> While I could do that, I would prefer the feature to work correctly. Is
> anyone else having this issue with 0.95? Is this a known bug that will
> be fixed in a future version?
>
Wha
> Török Edwin wrote:
> What is the bug here? That the filename scanned is not logged?
I think so. When LogClean = yes I get a lot of this in my log file:
Mar 24 09:26:28 emailfw3 clamd[23436]: fd[10]: OK
Mar 24 09:27:13 emailfw3 last message repeated 4 times
Mar 24 09:28:21 emailfw3 last message
Vincent Aniello wrote:
> Since upgrading to clamav 0.95 I am getting the log message "fd[10]: OK"
> appearing in my clamav log file. Clamav is configured to log to syslog.
> Also, I am logging clean messages.
>
I'm guessing that your clamdclient or clamav-milter is using fd-passing.
My specul
Nathan Brink wrote:
> I'm guessing that your clamdclient or clamav-milter is using fd-passing.
> My speculation: This means that clamd wouldn't know the name of the file
> (and that what clamd is scanning may not be a file). The only way clamd
> can identify the file it is scanning is by the num
Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
I have not been able to get a version greater than 0.92.1 on Solaris 10
x86 to build to date, and am
wondering what changed after 0.92.1 that is giving me the problem.
./configure --sysconfdir=/etc
checking build system typ
John Goubeaux wrote:
> Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
>
> I have not been able to get a version greater than 0.92.1 on Solaris 10
> x86 to build to date, and am
> wondering what changed after 0.92.1 that is giving me the problem.
>
>
> ./configure --sysc
Thanks,
Good to know that at least it does work. Your build environment is
different ( I am using gcc to compile ). Its odd though b/c I am
doing the same thing as when I built the earlier versions, same env
etc. So am trying to figure out what has changed ?
-john
>John Goubeaux wrote:
>>
On Thursday 02 April 2009 (02:00 pm), John Goubeaux wrote:
> Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
>
> I have not been able to get a version greater than 0.92.1 on Solaris 10
> x86 to build to date, and am
> wondering what changed after 0.92.1 that is giving me t
On Thu, Apr 2, 2009 at 11:00 PM, John Goubeaux
wrote:
> Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
Feel free to use OpenCSW packages, we have ClamAV 0.95 for Solaris
8/9/10 on x86/sparc.
http://opencsw.org/packages/clamav
All dependencies are handled automatically wi
John Goubeaux wrote:
> Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
Builds fine for me with gcc:
http://farm.0xacab.net/build/show/2335
-aCaB
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://w
On 2009-04-03 00:00, John Goubeaux wrote:
> Has anyone done a successful build of clamAV-0.95 0n Solaris 10 x86 ?
>
> I have not been able to get a version greater than 0.92.1 on Solaris 10
> x86 to build to date, and am
> wondering what changed after 0.92.1 that is giving me the problem.
>
>
>
stems Administrator
Gevirtz Graduate School of Education
UC Santa Barbara
Phelps Hall 3534
805 893-8190
- Original Message -
From: shuttlebox
Date: Friday, April 3, 2009 0:00 am
Subject: Re: [Clamav-users] clamAV-0.95 0n Solaris 10 x86 Build
To: ClamAV users ML
> On Thu, Apr 2, 2009 at 11:00
>
> Before that error message, does it say something about libbz2.a?
> If so try upgrading your bzip2 package.
>
> Best regards,
> --Edwin
>
>
>
Yes, it appears this might be the culprit!
Text relocation remains referenced
against symbol offset in file
0x1 /usr/local/lib/libbz2.a(bzlib.o)
Well install of latest bzip2 package did not remedy the build error
Is it possible that the presence of older clamAV libraries in
/usr/local/lib is causing the error?
eg... Do I want to stop and remove the existing ClamAV version before
attempting a build of the newer version ? which I assume
John Goubeaux wrote:
> Well install of latest bzip2 package did not remedy the build error
>
> Is it possible that the presence of older clamAV libraries in
> /usr/local/lib is causing the error?
>
It looks like the linker is finding a lot of old libraries. I remove them
before
building but
Hi,
I just upgraded to ClamAV 0.95. I am trying SafeBrowsing.
Please, I would like to know why it is mandatory to run freshclam
every 30 minutes when using that feature (safebrowsing).
Thank you for your attention and for the great ClamAV.
Best regards,
Cássio
__
cas...@gmail.com wrote:
> Hi,
>
> I just upgraded to ClamAV 0.95. I am trying SafeBrowsing.
>
> Please, I would like to know why it is mandatory to run freshclam
> every 30 minutes when using that feature (safebrowsing).
>
> Thank you for your attention and for the great ClamAV.
On Tue, Mar 24, 2009 at 7:30 PM, aCaB wrote:
> cas...@gmail.com wrote:
>> Please, I would like to know why it is mandatory to run freshclam
>> every 30 minutes when using that feature (safebrowsing).
>>
>> Thank you for your attention and for the great ClamAV.
>
> This is mandated by the
24 matches
Mail list logo
