On 2/10/2011 4:29 PM, Kelsey Cummings wrote:
So very not cool!
Yikes. Nothing like an unplanned and untested upgrade. At least I am now
running the latest! I had about 900 emails queued up since clamd failed.
All looks good now.
-Matthew
___
Help u
On 10/28/2010 1:06 PM, Hook wrote:
Unsuscribe
From: Hook
To: ClamAV users ML
In-Reply-To:<4cc83169.9050...@cmpublishers.com>
MIME-Version: 1.0
Subject: [Clamav-users] Unsuscribe
X-BeenThere: clamav-users@lists.clamav.net
X-Mailman-Version: 2.1.11
Precedence: list
Reply-To: ClamAV users ML
List
On 8/5/2010 3:42 PM, Noel Jones wrote:
But it would be easy enough to bypass by changing the cASE of the name
or using J. Doe etc. (you might be able to use wildcards to ignore
case in the sig)
Can anyone help me figure out how to ignore case so I can catch JoHn
SmItH any other variant with
On 8/5/2010 3:42 PM, Noel Jones wrote:
Creating "banned word" signatures is pretty straightforward. Convert
the names to hex, add the clamav stuff and save it in a foo.ndb file
in the clamav directory. A sig for "John Doe" would look something
like (completely untested):
Client.Data.John.D
I asked this on the Spamassassin list, and was advised I would have
better luck with ClamAV. I do have ClamAV running in several setups, but
have never done anything exactly like this.
My typical setup would be Postfix -> Amavisd -> ClamAV.
I work for a healthcare company. I have been asked to
