Blocking .htm files and relevance to rich text/ HTML emails

Hi

We have an external company trying to an email an attachment that is an .htm file. It is not getting through our SMTP Gateway which is configured to block .htm files as a security requirement.

My questions are

a) Is this considered necessary by the wider community
b) Disregarding the .htm attachment, does the fact that some emails are HTML formatted, and some are Rich Text, have anything to do with the problem? Or are HTML emails and an .htm attachment two different things (I assume they are)
c) Is it conceiveable to block HTML mails and is there any advantage? Or does blocking take place on attachments by and large?

We are using Exchange 2003 Sp2, Outlook 2003/2007 clients. Apologies in advance, I know this may sound like a daft question :)

Thx
LVL 3
kam_ukAsked:
Who is Participating?
 
David LeeCommented:
Hi, kam_uk.

a.  In my experience, not usually.  Executables are the big threat, although I suppose in some ways an .htm could be considered an executable in that launching it could take the user some place they don't want to go.

b.  No.  Attachments and the message body are two different things.  No relationship.  There are companies and organization that block HTML messages too.  Both for security and for space.

c.  Yes, it is conceiveable after a fashion, although blocking is primarily an attachment issue.  The way to do that is to configure Outlook to read all messages in plain-text.  That blocks access to the HTML version of the message.  It's basically the same as attachment blocking which doesn't actually stop the message from getting through, it just blocks access to the attachment.
0
 
kam_ukAuthor Commented:
Thanks!
0
 
David LeeCommented:
You're welcome.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.