> -----Original Message-----
> >The failing signature is:
> >
> >Email.Phishing.Exeter.0002:0:0,6:44656172{-18}537562736372696
> 265722c{-4
> >}
> >5765{-4}617265{-4}63757272656e746c79{-4}6361727279696e672d6f7
> 574{-4}61{
> >-
> >4}6d656e7461696e616e6365{-4}70726f63657373{-4}746f{-4}796f757
> 2{-18}6163
> >6
> >36f756e742c{-4}746f{-4}636f6d706c657465{-4}74686973
>
> You might try perhaps placing your new signature into an
> "ndb" file and then running something like:
>
> clamscan -d Path-2-NDB-file
>
> That would report if there were a malformed signature in the file.
>
> --
> Gerard
I had tried that and I get the same problem, it just says 'Malformed
database', which gives no hint as to what it is about the signature
which is the problem! I was looking for something which would point out
where the problem is in the signature.
Regards,
Phil.
--------------------
Phil Chambers
Postmaster
University of Exeter
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
