M
Michael Moser
I recently dragged a URL from IE directly into a new task I had
created. When I now open that task again, the URL is not displayed,
instead there is a line that says "Outlook blocked access to the
following potentially unsafe attachment: foobar.url" and the URL is
NOT displayed!
How can I stop this idiocy? I want to *see* that URL! And since when
can a URL be unsafe??? If at all, it's the browser that's unsafe if it
is configured to download and executes things without prior asking and
its implementation (or that of the objects or language invoked) has
security holes (of which MS has a long history...)!
But since I know that the URL is NOT harmful (after all I created it
myself by dragging it into that task) I want to *see* it! I *HATE*
such paternalistic approaches that simply withhold information. At a
minimum I want to be asked (and maybe warned...), whether Outlook
should display that URL or not!
so, how can I change that setting? I guess, this was introduced with
the recent ServicePack 4 that I applied to my Window 2000 since I
never encountered this before.
Michael
created. When I now open that task again, the URL is not displayed,
instead there is a line that says "Outlook blocked access to the
following potentially unsafe attachment: foobar.url" and the URL is
NOT displayed!
How can I stop this idiocy? I want to *see* that URL! And since when
can a URL be unsafe??? If at all, it's the browser that's unsafe if it
is configured to download and executes things without prior asking and
its implementation (or that of the objects or language invoked) has
security holes (of which MS has a long history...)!
But since I know that the URL is NOT harmful (after all I created it
myself by dragging it into that task) I want to *see* it! I *HATE*
such paternalistic approaches that simply withhold information. At a
minimum I want to be asked (and maybe warned...), whether Outlook
should display that URL or not!
so, how can I change that setting? I guess, this was introduced with
the recent ServicePack 4 that I applied to my Window 2000 since I
never encountered this before.
Michael