jas said:
I didn't shout at you, as a volunteer or as a professional. I am not
being
petulent. I provided the version number, etc to the Microsoft folks
and they
posted whatever they posted.
So you somehow convinced a Microsoft employee or process to submit your
post on your behalf? You weren't the one using CDO (webnews) to visit
the newsgroups to post your own message? Hmm, so how did you submit
your message here?
(I use Outlook 2004). If you are the Vanguard
... meaningin the forefront ... you should avoid judgements, when you
may hot
have all the facts. I hold Microsoft responsible for changing the
way my
program worked wikthout letting me know, and then not providing me
with a way
to change it.
Four years old and you need notification now? The security update that
added the protection against hazardous attachment filetypes was added
over 4 years ago
(
http://www.microsoft.com/presspass/press/2000/Jun00/SecurityUpdateMA.asp).
To submit a request for change or for an added feature, visit
Microsoft's home page, click on the "Contact Us" link at the bottom of
the page, and follow the links to their feedback web form
(
http://register.microsoft.com/mswish/suggestion.asp) to submit your
request to their wishlist. You weren't here asking for help. You won't
get much notice, if any, from Microsoft itself by posting here.
As to your being a volunteer, that's all nice. I'm a volunteer at a
lot of
things. I've never been chastised for asking a question.
You will when you SHOUT in our ears. Lots of other users manage to
employ the Microsoft CDO webnews-for-dummies interface to newsgroups
without being forced to use all uppercase in composing the text for
their Subject header. Using all caps is considered SHOUTING.
You may wnat to avoid judgemental responses. We'll all be better
off.
If a major product doesn't do exactly what you want, often there are
workarounds or extras you can use to accomplish your wants. After
adding the e-mail security update, Microsoft published a KB article
(link already provided in my prior post) that tells you how to remove
whatever filetypes you want from the list of hazardous ones, so you
could tailor Outlook just how you wanted regarding which, if any,
filetypes to block. The solution already exists.
Some users don't like to delve into the registry because they are
uncomfortable with performing surgery at that low a level in the
operating system. So utilities have appeared to facilitate changing the
security behavior for filetype attachments, like Attachment Options
which is what I use with Outlook 2002 (you'll find a link to it at
http://www.slipstick.com). There are solutions when using Exchange by
utilizing security templates but you never mentioned Exchange so it is
probably not part of the environment in which you are requesting the
change in security behavior.
The solutions to achieve the behavior you want already exist. Editing
the registry to alter behavior is not something unique to Microsoft
products. Free tools exist to eliminate having to use regedit.
