On Thu, 2008-12-04 at 12:43 +1300, Lists wrote:
> Arthur Dent wrote:
> > The best thing to do is to download the script, put it somewhere where
> > the user that will run it (possibly "clamav") has read + execute access,
> > (I created a /home/clamav/ directory) and then try running it manually
> > first. If it works it will download the extra files need by Clamav for
> > the spam and phishing sigs.
>
> So if the manual run works it will download everything needed and clam
> will know its there and to use it?
Depends. Come on, Kate, have a look at the scripts. As I briefly
mentioned before, they are intended to be read (at least those I ever
had a look at include their own full docs) and *configured*.
The latter is important. If it isn't configured according to *your*
ClamAV setup, it can't possibly do anything. If and how the script or
your cron job will have to poke clamd (you're running that, aren't you?)
again, depends.
> Also will it add info to the headers of the email so that I can check
> which emails are being hit by the plugin?
No, "it" doesn't.
It's third-party signatures. ClamAV uses them, if configured properly.
Whatever adds headers *now* will do so for third-party sigs just as
well.
Wait -- what "plugin" are you talking about?
/me mumbles something about "wrong list" and "should have included TM
hints" according to some recent post on that other list...
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
