tely detected? David Franco-Rocha - Original
Message - From: "Matt" [EMAIL PROTECTED] To: Declude.JunkMail@declude.com
Sent: Monday, March 21, 2005 8:16 AM Subject: Re: [Declude.JunkMail]
Exclude BABEXT Notify for COM
There seems to be a bug in all versions
Subject:
Re: [Declude.JunkMail] Exclude BABEXT Notify for COM
David,
I posted some log snippets last week on the Declude Virus list that
show what is happening.
Yes, the notifications are being sent in error. These COM files are
being detected by Declude Virus as "
There seems to be a bug in all versions where a bogus COM file is still
bounced as a banned extension (unlike other 'bogus' types that are
detected).
The workaround is to add SKIPIFEXT COM to the top of your
bannotify.eml, however this will stop all bounces for COM files
regardless of whether
Don,
The manuals are on the web site. Select Tech Support at the top of the page
and you will be taken to links for the manuals.
As for the bogus COM file issue, we understand that this is a problem and
are looking into ways to resolve it.
David Franco-Rocha
- Original Message -
From:
Matt,
This will work for the meantime and thank you very much!
-Don
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent: Monday, March 21, 2005 8:17 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Exclude BABEXT Notify for COM
[EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Monday, March 21, 2005 8:16 AM
Subject: Re: [Declude.JunkMail] Exclude BABEXT Notify for COM
There seems to be a bug in all versions where a bogus COM file is still
bounced as a banned extension (unlike other 'bogus' types that are
detected
e.JunkMail@declude.com
Sent: Monday, March 21, 2005 8:16 AM
Subject: Re: [Declude.JunkMail] Exclude BABEXT Notify for COM
There seems to be a bug in all versions where
a bogus COM file is still bounced as a banned extension (unlike other
'bogus' types that are detected).
