*This message was transferred with a trial version of CommuniGate(tm) Pro*
When I try and compile clamav under 10.5 I get the following error.
checking for clamav in /etc/passwd... checking for clamav using
netinfo... ./configure: line 25403: /usr/bin/nidump: No such file or
directory
./config
Hello All.
Just a follow up. I removed selinux-policy using yum
and clamdscan is working correctly now. Not sure how
to fix this correctly and still keep selinux though.
Thanks for help.
Thomas
--
Flambeau Inc. Technology Center - Baraboo, WI
Email: [EMAIL PROTECTED]
Keyserver: http://pg
Xavier Beaudouin escreveu:
> Hello,
>
In December 2006, we were running ClamAV 0.88.7, and there were still
a fair number of "real" viruses being detected in inbound email. Now
running 0.91.2 and 0.92, there seem to be only phishing attempts, and
not even very many of them. In
Török Edwin wrote:
> And you've called 'mail', and let postfix call procmail?
Yes that is correct.
> I'm not sure where procmail is executed, but if inside the chroot you've
> got a prob.
I can use ~/.procmailrc to create a file in /tmp when postfix calls procmail.
Since procmail can read the
tblader wrote:
> Török Edwin wrote:
>
>> Is your mailserver running chrooted? I remember postfix can do that.
>>
>
> You are correct, but I don't think this is the problem. If I put
> a line in $HOME/.procmailrc to touch a file: /tmp/foo.procmail then
> that file ends up in /tmp, not a chr
Török Edwin wrote:
> Is your mailserver running chrooted? I remember postfix can do that.
You are correct, but I don't think this is the problem. If I put
a line in $HOME/.procmailrc to touch a file: /tmp/foo.procmail then
that file ends up in /tmp, not a chroot /tmp.
Would this mean procmail
tblader wrote:
> Sending the message via MUA results in problem connecting to clamd
>
>
>$ echo EICAR | mail -s test40 [EMAIL PROTECTED]
>$ cat /tmp/clamd.log
>...
>--
>stream: OK
>--
>WARNING: Can't
Török Edwin wrote:
> tblader wrote:
>> Török Edwin wrote:
>>
>>> Check permissions on /tmp/clamd.socket
>>>
>> seems to be OK
>> $ ls -lart /tmp/clamd.socket
>> srwxrwxrwx 1 clamav clamav 0 Dec 28 09:15 /tmp/clamd.socket
>>
>>
>>
>>> Just set TCPSocket, and not TCPAddr. Does it work?
>
Hi there,
On Fri, 28 Dec 2007 Brian Read wrote:
> I use a number of smeservers (aka e-smith), which all use clamav to
> scan incoming emails. Up to (and including) version 6 I got plenty
> of hits from clamav. As I upgraded to version 7, the clamav hits
> subsided to only phishing emails being
tblader wrote:
> Török Edwin wrote:
>
>> Check permissions on /tmp/clamd.socket
>>
>
> seems to be OK
> $ ls -lart /tmp/clamd.socket
> srwxrwxrwx 1 clamav clamav 0 Dec 28 09:15 /tmp/clamd.socket
>
>
>
>> Just set TCPSocket, and not TCPAddr. Does it work?
>>
>
> OK - updated config i
Török Edwin wrote:
> Check permissions on /tmp/clamd.socket
seems to be OK
$ ls -lart /tmp/clamd.socket
srwxrwxrwx 1 clamav clamav 0 Dec 28 09:15 /tmp/clamd.socket
> Just set TCPSocket, and not TCPAddr. Does it work?
OK - updated config is below*. Now listening on ANY interface
and TCP:3310.
tblader wrote:
> Hello.
> I am running clamav[0] on centos 5 and trying to get it integrated
> with postfix and procmail[1]. I get one of two error messages showing
> up in /tmp/clamd.log when procmail runs[2]
>
> When I configure clamd.conf to use the LocalSocket directive,
Check permissions on
Hello.
I am running clamav[0] on centos 5 and trying to get it integrated
with postfix and procmail[1]. I get one of two error messages showing
up in /tmp/clamd.log when procmail runs[2]
When I configure clamd.conf to use the LocalSocket directive, I
get "cant connect to clamd". If I change clam
Hello list again.
I solve tho problem.
Stupidly I add freshclam line in root's crontab and it was also running for
clamav user cron at the same time!
Sorry for bothering the list.
Nikos
> > UpdateLogFile /var/log/freshclam.log
> > LogSyslog yes
>
If you are using LogSyslog, why do you speci
14 matches
Mail list logo
