Forum Moderators: bakedjake
just set up newest version of clamAV and have been looking at ways to set it up for certain accounts.
i have tried clamassassin which uses a procmail recipe but clamd always ends of using 99% of CPU (whether that's the fault of clamassassin or clamd i don't know - the logs don't yield a clue).
i wondered what other methods people use and whether these can be turned off/on per user.
thanks
i just spent a sleepless night installing mailscanner - without success. but it now appears that it wasn't mailscanner that was at fault, but an endless mail loop to the address to which bounced mails are sent which was exceeding my quota and causing all sorts of problems.
i shall investigate this and then if necessary open another post.
i am sure mailscanner will work once i get this mailer-daemon mail loop sorted (some of the mails have been bounced so many times i can't count the number of nested messages in each mail - well over 10 MB!)
cheers