On Feb 7, 2008 11:12 AM, <[EMAIL PROTECTED]> wrote:
>
> On Feb 7, 2008 10:53 AM, Dennis Peterson <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote:
> > > Thanks for the reply Dennis. The 'virus' is actually a Phishing
> > > attempt from the 02/04 def update thats hitting on the logwatch email
On Feb 7, 2008 10:53 AM, Dennis Peterson <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Thanks for the reply Dennis. The 'virus' is actually a Phishing
> > attempt from the 02/04 def update thats hitting on the logwatch email
> > here is the line from the clamd.log
> >
> > Thu Feb 7 10:
Thanks for the reply Dennis. The 'virus' is actually a Phishing
attempt from the 02/04 def update thats hitting on the logwatch email
here is the line from the clamd.log
Thu Feb 7 10:27:47 2008 ->
/var/spool/MailScanner/incoming/13948/29EC821AC463.28768.message:
Email.Phishing.RB-2646 FOUND
Is t
Hello list,
I run a small mail server with clamd used to scan the incoming and
outgoing email. I recently noticed that I had stopped receiving my
logwatch daily digest. I looked into it and clam is stopping it
claiming its phishing. Is there any way to find out what part of the
email may be trigge
Hello list,
I run a small mail server with clamd used to scan the incomming and outgoing
email. I recently noticed that I had stopped receiving my logwatch daily
digest. I looked into it and clam is stopping it claiming its phishing. Is
there any way to find out what part of the email may be trigg
