Jason Bilbrey
06-07-2002, 01:58 PM
I've spoken to NAI tech support on this issue and they
insist it's not their problem.
Problem Description: A user creates a simple Microsoft
word document (no macros, etc). They then try to post
this document to an Exchange 5.5 Public folder (File -->
Send To --> Exchange Folder). As soon as they post
the .DOC file, Network Associate's GroupShield 5.0 sends
an alert saying that an .EXE file has been blocked
(because we block .EXE files). The "new" .EXE file is
always named in the 8.3 format. The first 8 characters
are the first 8 characters of the subject line...even
though the original .DOC file had a completely different
name.
NAI insists this is _not_ their problem, and that
something else must be changing the name of the document
before it gets to their software. This problem never
occured when we were still on GroupShield 4.5. This
problem has only started occuring randomly (very
infrequent) since we switched to GroupShield 5.0
We're using Exchange 5.5 with the latest service packs and
GroupShield 5.0 is using ESE for scanning. Our older
version of GroupShield 4.5 had been using AVAPI...
Has anyone seen anything like this? Any ideas?
Jason
insist it's not their problem.
Problem Description: A user creates a simple Microsoft
word document (no macros, etc). They then try to post
this document to an Exchange 5.5 Public folder (File -->
Send To --> Exchange Folder). As soon as they post
the .DOC file, Network Associate's GroupShield 5.0 sends
an alert saying that an .EXE file has been blocked
(because we block .EXE files). The "new" .EXE file is
always named in the 8.3 format. The first 8 characters
are the first 8 characters of the subject line...even
though the original .DOC file had a completely different
name.
NAI insists this is _not_ their problem, and that
something else must be changing the name of the document
before it gets to their software. This problem never
occured when we were still on GroupShield 4.5. This
problem has only started occuring randomly (very
infrequent) since we switched to GroupShield 5.0
We're using Exchange 5.5 with the latest service packs and
GroupShield 5.0 is using ESE for scanning. Our older
version of GroupShield 4.5 had been using AVAPI...
Has anyone seen anything like this? Any ideas?
Jason