>>>
> The problem is that Norton IEG and Viruswall, among others, do not
> detect inline attachments. Inline attachments are how files are sent
> when creating a message using a web browser.
When using a web browser, the file gets sent to the IMail web server in a
non-mail format. But, the IMail web server should convert it to MIME and
the user receiving the E-mail shouldn't be able to tell whether the file had
originally been sent by a regular E-mail program or through the web.
> Just for fun, send the EICAR test through your server by attaching
> it to a message using a browser. Then send it again using a mail
> client app. The first will get through, the second will be caught.
The reason for this is that through the web browser, the mail goes directly
to the IMail server. If the account is local, the virus will stay. If the
account is not local, the virus will only get caught if IMail is set to send
through a gateway that has virus scanning.
When you send through a mail client, it should be set up to use the virus
scanner as its SMTP server.
<<<
No, I have two machines with many different domains. I use the web interface
on one machine, create a message to a different domain on a different
machine and attach a file to this message. When it is sent, there is no
anti-virus product that will even recognize that there is an attachment.
Therefore, no action can/will be taken. Products that do content checking do
find the file and that is what I am using to provide security now.
Symantec told me today that NAVIEG is due for a new release next month. They
believe that it will detect inline attachments.
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.