Mailscanner attach scan problem

Martin Hepworth maxsec at gmail.com
Wed Dec 15 16:36:37 GMT 2010


and again make sure the clamd settings for port etc match with the
clamd.conf settings

Out of interest what version of clamav are you running?

-- 
Martin Hepworth
Oxford, UK


On 15 December 2010 14:24, Glenn Steen <glenn.steen at gmail.com> wrote:

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


More information about the MailScanner mailing list