Level 1 attachments - Is there anyway to unblock?

[BONNIE]

Ive got an attachment to an email that I need to unblock. Outlook will not
allow me to and from the help desk I have found it is a level 1 attachment.

I need this file to fix a program that has a corrupt cabinet file. Is there
anyway I can get Outlook to allow me to download this file? The file is
called
BudgetWinSetup.msi and sent to me by Support at Snowmint.com the creators of
the budget program I use on my computer.

Can anyone help me? Im only a medium level computer type... not the
brightest bulb in the box, but I mostly can figure things out.
Help?

 

[K. Orland]

http://www.howto-outlook.com/faq/blockedattachments.htm

Good luck!

 

[BONNIE]

That was SO easy and it unblocked it right away... well I had to update
something called netframe, but after doing that it installed and unblocked
it, I got the program installed and was able to reset the security back to
original settings easily. Thank you so VERY much!
Bonnie

 

[Delo]

Simply it works...
Thanks very much

 

[Cambria777]

This was great advice! Thanks! It unblocked the attachment, which was a
public folders shortcut (*.xnk) in Outlook 2003, but now when I open the
attachment, it will not follow the shortcut to the public folder, but instead
an "Attachment Security Warning" message opens with 2 options: Save to
disk... or Cancel. If I choose Cancel, nothing happens; the shortcut simply
won't work. If I choose "Save to disk..." and save the shortcut, then
double-click the shortcut from my hard drive, it works fine. Do you (or does
anyone) know how to get the shortcut to open inside Outlook? how to turn off
that warning message? As it is, my only option is to save the shortcut
outside Outlook, which is now how it used to be before I upgraded Outlook
2003 from SP2 to SP3 not long ago.

 

[Cambria777]

Thanks for the quick reply, but that is not the problem. There is no message
saying to show or hide. Before I made the change to the Registry to fix the
problem, Outlook had a message saying only that the attachment had been
blocked. Clicking on that message did nothing. I remembered that clicking
on it should do something, but after I upgraded from SP2 to SP3, that message
no longer gives me a choice. Before I edited the Registry, there was simply
a message there that was unclickable. There was no attachment. After I
edited the Registry, now the attachment is visible and I can double-click it.
But when I still had SP2 and double-clicked the attachment, it would
function; it would take me to the public folder that it pointed to. But with
SP3 installed, double-clicking it results in that Warning message I described
in my first post, where I only have the choice of Cancel or "Save to disk..."
This has something to do with SP3, I feel certain, because when I had SP2,
these Exchange shortcuts that point to a Public Folder were not an issue at
all. The attachment was always visible (no need to click any message about
how the attachment had been blocked, because it was NOT blocked. And
double-clicking that attachment (shortcut) always took me straight to the
public folder that it was pointing to. I've succeeded at unblocking the
attachment by using the instructions you provided about how to edit the
Registry. So I'm PARTLY successful at fixing this problem. The rest of the
problem is getting that Warning message to go away, so that I am not forced
to save those shortcuts to a disk and can simply open them inside Outlook.
Any ideas??? Any help would be greatly appreciated! Thanks!!!

 

[Cambria777]

I just found the answer to my own question. The user cannot bypass the "save
to disk" feature, not in SP3. I found the statement below on this page:

http://www.slipstick.com/outlook/esecup/getexe.asp

"After applying this registry fix or using one of the tools, the user still
has to save the attached file to a system drive before opening it. In effect,
the fix rolls the attachment behavior back to Outlook 2000 SR-1, with its
included Attachment Security Fix. An end-user cannot bypass this "save to
disk" behavior and open the file directly from the mail message, though an
Exchange administrator can."

So it seems that for now, I'm stuck with having to save the shortcuts to my
hard drive, but at least I can now access them, thanks to the information you
provided about how to edit the Registry. So thank you again... very much!!

 

[Cambria777]

I just found the answer to my own question. The user cannot bypass the "save
to disk" feature, not in SP3. I found the statement below on this page:

http://www.slipstick.com/outlook/esecup/getexe.asp

"After applying this registry fix or using one of the tools, the user still
has to save the attached file to a system drive before opening it. In effect,
the fix rolls the attachment behavior back to Outlook 2000 SR-1, with its
included Attachment Security Fix. An end-user cannot bypass this "save to
disk" behavior and open the file directly from the mail message, though an
Exchange administrator can."

So it seems that for now, I'm stuck with having to save the shortcuts to my
hard drive, but at least I can now access them, thanks to the information you
provided about how to edit the Registry. So thank you again... very much!!

 

[Dan]

I just found the answer to my own question. The user cannot bypass the "save
to disk" feature, not in SP3. I found the statement below on this page:

http://www.slipstick.com/outlook/esecup/getexe.asp

"After applying this registry fix or using one of the tools, the user still
has to save the attached file to a system drive before opening it. In effect,
the fix rolls the attachment behavior back to Outlook 2000 SR-1, with its
included Attachment Security Fix. An end-user cannot bypass this "save to
disk" behavior and open the file directly from the mail message, though an
Exchange administrator can."

So it seems that for now, I'm stuck with having to save the shortcuts to my
hard drive, but at least I can now access them, thanks to the information you
provided about how to edit the Registry. So thank you again... very much!!

You're making life harder than it has to be. Have the sender re-name the
needed file to an attachment name that Outlook will allow. (.TXT, .XEX, .LLD
......) Save the file to disk and rename it to the correct name.

 

[Diane Poremsky [MVP]]

You're making life harder than it has to be. Have the sender re-name the

needed file to an attachment name that Outlook will allow. (.TXT, .XEX,
.LLD
.....) Save the file to disk and rename it to the correct name.

That can be an exercise too. It's a lot easier just to unblock the
extension.

--
Diane Poremsky [MVP - Outlook]





EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[Thomas]

Kathleen-- i've a similiar problem--- i cannot seem to unblock images in my
MS Outlook 2007 inbox, EVERY single message that has Images NOW has
PLACEHOLDERS (black lined frames) of where the graphic would appear if it
were not blocked. For the life of me-- i cannot figure out where in the heck
i turned this On, let alone turn it off!! lol... Please help a simple guy
correct this stupid mistake....?

thanks...

Thomas

 

[nzkw3023]

Ive got an attachment to an email that I need to unblock. Outlook will not
allow me to and from the help desk I have found it is a level 1 attachment.

I need this file to fix a program that has a corrupt cabinet file. Is there
anyway I can get Outlook to allow me to download this file? The file is
called
BudgetWinSetup.msi and sent to me by Support at Snowmint.com the creators of
the budget program I use on my computer.

Can anyone help me? Im only a medium level computer type... not the
brightest bulb in the box, but I mostly can figure things out.
Help?

 

[Dan]

Suggesting registry modifications to people that are not comfortable renaming
files is reckless and irresponsible. Renaming files is the safe way to
circumvent the system. People that can't do this successfully _should not_
be modifying anyone's registry - including their own.

You're making life harder than it has to be. Have the sender re-name the
needed file to an attachment name that Outlook will allow. (.TXT, .XEX,
.LLD
.....) Save the file to disk and rename it to the correct name.

That can be an exercise too. It's a lot easier just to unblock the
extension.

--
Diane Poremsky [MVP - Outlook]





EMO - a weekly newsletter about Outlook and Exchange:
(e-mail address removed)

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[Mike]

My safe sender sent an e-mail message to me with a .mdb (MS ACCESS database)
file attached to my Outlook 2007 that I could not save. We tried to send it
with a .txt extension but that did NOT work. I like the idea of sending
files zipped and then unzipping. No messing around with the registry which
is like vodoo for me.

 

[Diane Poremsky [MVP]]

Why didn't the txt extension work?

Zipping is definitely better but if you routinely get mdb from senders you
trust, then adding it to the registry is much easier.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

 

[Mike]

I don't know why it didn't work using the procedure of renaming the
extension. I've done it before on another issue.

I downloaded the free program off the web that was mentioned on this
discussion stream. I have it on another computer so I forgot the name of the
progam. It changes the registry so that I can detach certain files windows
considers potentially dangeous. Great program. It worked perfectly and was
easy to use. I will donate some money to the author. He really seems to
know what he is doing. With this program, I consider my problem solved.
Good luck.

Why didn't the txt extension work?

Zipping is definitely better but if you routinely get mdb from senders you
trust, then adding it to the registry is much easier.

--
Diane Poremsky [MVP - Outlook]



Outlook Tips by email:
mailto:[email protected]

EMO - a weekly newsletter about Outlook and Exchange:
mailto:[email protected]

You can access this newsgroup by visiting
http://www.microsoft.com/office/community/en-us/default.mspx or point your
newsreader to msnews.microsoft.com.

My safe sender sent an e-mail message to me with a .mdb (MS ACCESS
database)
file attached to my Outlook 2007 that I could not save. We tried to send
it
with a .txt extension but that did NOT work. I like the idea of sending
files zipped and then unzipping. No messing around with the registry
which
is like vodoo for me.

 

[Ken Slovak - [MVP - Outlook]]

If this is Attachment Options you're talking about make sure you have the
latest version installed. I recently updated it to include some extensions
that were missing in Outlook 2007 and also released the version that
includes extensions added for Outlook 2007 SP2.

 

[Krzysztof Żelechowski]

Suggesting registry modifications to people that are not comfortable renaming
files is reckless and irresponsible. Renaming files is the safe way to
circumvent the system. People that can't do this successfully _should not_
be modifying anyone's registry - including their own.

These advices go to different people: the sender cannot change the
extensions but the receiver can modify the registry.

 

[Krzysztof Żelechowski]

The problem is arduous because Outlook Express creates a forbidden attachment
when you drop a handle to a Web page from Internet Explorer. Then the reader
using Microsoft Outlook cannot visit the URL. This is plainly insane. Don’t
you people in Microsoft talk to each other?

 

[Brian Tillman [MVP - Outlook]]

The problem is arduous because Outlook Express creates a forbidden
attachment
when you drop a handle to a Web page from Internet Explorer. Then the
reader
using Microsoft Outlook cannot visit the URL. This is plainly insane. Don’t
you people in Microsoft talk to each other?

"You people"? Rarely does anyone from Microsoft read this newsgroup. We're
all just ordinary users here.