and again make sure the clamd settings for port etc match with the clamd.conf settings<br><br>Out of interest what version of clamav are you running?<br><br clear="all">-- <br>Martin Hepworth<br>Oxford, UK<br>
<br><br><div class="gmail_quote">On 15 December 2010 14:24, Glenn Steen <span dir="ltr"><<a href="mailto:glenn.steen@gmail.com">glenn.steen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On 15 December 2010 13:50, Ante Gulam <<a href="mailto:ante.gulam@ri-ing.hr">ante.gulam@ri-ing.hr</a>> wrote:<br>
> Hi,<br>
><br>
><br>
><br>
> I did everything as you wrote.. step by step... same thing happend as when i<br>
> was trying<br>
><br>
> To get it work... No more error for clam considering perms... (lstat())..<br>
> But no mails<br>
><br>
> Coming through... No idea anymore.. Mails stays in postfix hold.. and in<br>
> var/log/mail.log<br>
><br>
> I get same msg as before:<br>
><br>
><br>
><br>
> Dec 10 14:44:52 mailfilter MailScanner[5319]: New Batch: Scanning 2<br>
><br>
> messages, 5178 bytes<br>
><br>
> Dec 10 14:44:52 mailfilter MailScanner[5319]: SpamAssassin cache hit for<br>
><br>
> message 478966C69B.86DF2<br>
><br>
> Dec 10 14:44:52 mailfilter MailScanner[5319]: SpamAssassin cache hit for<br>
><br>
> message 185E96CDD3.BDED9<br>
><br>
> Dec 10 14:44:54 mailfilter MailScanner[5363]: MailScanner E-Mail Virus<br>
><br>
> Scanner starting...<br>
><br>
><br>
><br>
> Cache hit keeps rising as mails keep coming.. any ideas about that? Clam log<br>
> is of course without errors now..<br>
><br>
><br>
><br>
> Regards,<br>
><br>
> A<br>
><br>
</div></div>If you do<br>
su - postfix -s /bin/bash<br>
and then try access the incoming wirk directories, does that work?<br>
Access by ls and/or cd /var/spool/MailScanner/incoming ...<br>
If that works, do the same for clamav<br>
su - clamav -s /bin/bash<br>
... and try access things...<br>
If one, or more, of them doesn't work, we still have a permission<br>
problem to solve;-)<br>
An "ls" of the incoming work dir when you have clamd enabled (all the<br>
steps I stipulated done), would be nice...:)<br>
How did you configure clamd, BTW? Mine looks like:<br>
<br>
# grep Clamd /etc/MailScanner/MailScanner.conf<br>
# Clamd only: configuration options for using the clamd daemon.<br>
# more than 1 CPU) then you can set "Clamd Use Threads" to "yes" to<br>
Clamd Port = 3310<br>
Clamd Socket = /tmp/clamd.socket<br>
Clamd Lock File = # /var/lock/subsys/clamd<br>
Clamd Use Threads = yes<br>
# grep clamd.socket /usr/local/etc/clamd.conf<br>
LocalSocket /tmp/clamd.socket<br>
<div><div></div><div class="h5">#<br>
<br>
Cheers<br>
--<br>
-- Glenn<br>
email: glenn < dot > steen < at > gmail < dot > com<br>
work: glenn < dot > steen < at > ap1 < dot > se<br>
--<br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
Before posting, read <a href="http://wiki.mailscanner.info/posting" target="_blank">http://wiki.mailscanner.info/posting</a><br>
<br>
Support MailScanner development - buy the book off the website!<br>
</div></div></blockquote></div><br>