Software

Ask something
Discussion Locked

Outlook security update

0 helpful
8 replies

by seskds

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We presently have a system written using Access and VB which generates an e-mail, attaches a snapshot file to it, and delivers it via the clients local Outlook app. We want to keep the procedure the same but have encountered a problem with Outlook 2000 SP-2 and 2002 due to the security update. I am familiar with the solution which involves the Exchange Server's Public folder but would like to know if there is a solution which only involves the client and not the server. Are there any settings that can be changed on the local installation of Outlook
to make this happen?

8 replies

by syscokid

For Outlook 2002:

www.slipstick.com/outlook/esecup/getexe.htm#ol2002

For Outlook 2000:

"
Interestingly, several people on the newsgroups have reported good results from just replacing two Outlook application files with the corresponding files from the original Office CD or Office 2000 SR-1. (SR-1 probably would be better -- you could copy them before you run the SP2 update.) The two files are Outllib.dll from the Office folder and Outllibr.dll from the Office\1033 folder. This is an unsupported method and probably does not fix all the aspects of the patch, however. It may also cause other problems on your system. Implement at your own risk."

That, and other good info, is found at:

http://www.slipstick.com/outlook/esecup.htm

by syscokid

For Outlook 2002:

www.slipstick.com/outlook/esecup/getexe.htm#ol2002

For Outlook 2000:

"
Interestingly, several people on the newsgroups have reported good results from just replacing two Outlook application files with the corresponding files from the original Office CD or Office 2000 SR-1. (SR-1 probably would be better -- you could copy them before you run the SP2 update.) The two files are Outllib.dll from the Office folder and Outllibr.dll from the Office\1033 folder. This is an unsupported method and probably does not fix all the aspects of the patch, however. It may also cause other problems on your system. Implement at your own risk."

That, and other good info, is found at:

http://www.slipstick.com/outlook/esecup.htm

by skippi

I needed a client fix also and was leery of using the older version .dll replacement method. I opted to use a hexadecimal editor to open the current outllib.dll and change the excluded extensions. It is relatively painless and is working great. We have been using this since July 2001. The following URL is where I found information on editing the outllib.dll.:

ww.windows2000faq.com/articles/index.cfm?articleid=19722.

After installing SP2 I did a hex edit on the outllib.dll file to exclude extensions I wanted to pass through. I did my search on "exe" no quotes. Then replaced the selected extensions with !@#. I tried replacing only one character of the string and that failed as a corrupted .dll. It was my first time using a hex editor on a .dll and I survived with good results. Hope this is a help.

by shanghai sam

Actually, our particular problem revolves around automation security more than attachments. At present, Outlook Redemption seems to be a viable solution for our particular application. Thanks.

This discussion is closed to new replies.