Overcoming the Outlook Security Update
John Lewis
If like myself you get fed-up with Outlook popping up the message
'Someone is trying to access Outlook.. etc" when you connect with
Outlook in your VO app, then the link below is a solution to overcome
that problem.
http://gethelp.devx.com/techtips/exo_pro/10min/10min1200/10min1200-2.asp
It involves downloading a file from Microsoft and setting up some
permissions. The download link and full instructions are provided in
this article.
Alternatively I have found that there are 2 dll files which are
patched when the security patch is applied. These are:
Outllib.dll residing in your Office folder, (e.g. C:\Program
Files\Microsoft Office\Office)
and
Outllibr.dll residing in your 1033 folder, (e.g. C:\Program
Files\Microsoft Office\Office\1033)
By replacing these with the original files from your Office CD then
you will not get the nagging prompt from Outlook, but obviously your
system is now at risk from a worm etc
I hope this is of some help.
Regards to all
John Lewis
@je
just a better way to manage it have a look at the Advanced Security tool
from Mapilab. http://www.mapilab.com/download/#security
When you install this tool you get one prompt and can allow access to
specific applications.
Ed
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:pdc4u1dj18o347ehm...@4ax.com...
John Lewis
What is the cost, it does not list the cost for the advanced security
module? How is it used?
Regards
John
Stephen Quinn
> What is the cost, it does not list the cost for the advanced security
> module?
It's free - see the product description page
> How is it used?
Read the docs
HTH
Steve
John Lewis
which does the agreeing to the security prompts automatically.
It would be fine for single emails but not practical for sending many.
Regards
John
On Sat, 04 Feb 2006 02:49:18 GMT, in comp.lang.clipper.visual-objects
you wrote:
@je
to Check always allow access for your application once, after that your
users will never see it again.
Ed
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:1l49u1t0nepmojs49...@4ax.com...
John Lewis
I do get the point, I allowed my app to call Outlook and I as you say
I don't see the pop-up security windows, BUT, if I am sending MANY
emails the process runs like a lame dog. The performance is totally
unacceptable.
I was referring to another solutin which was not free, which behaved
as if you were clicking the buttons yourself on the security window.
This ran much faster but there is still a performance hit.
How many emails are you sending at one time?
Regards
John
GSchaller
It doesn't work like that. Once installed and the box ticked, it
provides almost no visible impediment at all. We generate bulk tasks and
emails in overnight rollover processes and see any change in Outlook's
performance.
However, nor am I completely sure what you are doing so I don't know
where we take this next.
Geoff
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:p6kbu15ea4vtmm7tm...@4ax.com:
Gary Stark
> Hi Ed,
>
> I do get the point, I allowed my app to call Outlook and I as you say
> I don't see the pop-up security windows, BUT, if I am sending MANY
> emails the process runs like a lame dog. The performance is totally
> unacceptable.
>
> I was referring to another solutin which was not free, which behaved
> as if you were clicking the buttons yourself on the security window.
> This ran much faster but there is still a performance hit.
John,
Search the archives. I posted exactly such a solution in about the
middle of last year, in VO code.
It permitted you to set the time value for how long Outbreak permitted
your application access, and it cost you all of ...
er ....
um ...
ahhh ...
yeah, nuttin' to use.
John Lewis
Is this the thread?
>>We're going to be placing our hooks into the VO2Outlook 3 GUI app, which
>>is a library that the VO2Outlook InboxExplorer uses.
>>Open the TS_SimpleInboxExplorer module, and in your text editor, open
>>the SetupInbox() method of TS_SimpleInboxExplorer.
>>Add the following declaration somewhere near the start of this method:
>>LOCAL dwID AS DWORD
>>After the line
>> FOR i := 1 UPTO nCount
>>Add
>> CreateVOThread( NULL, 0, @Outbreak(), NULL, 0, @dwID )
Does this only work with COMSDK? I have a small problem with that but
Geoff gave me some cluse which I can look in to.
Thanks for your help.
Regards
John
Gary Stark
> Hi Gary,
>
> Is this the thread?
>
Yep.
@je
you generate. When using exchange you can relax the security just for the
account you are using for the send, or even set up a specific account just
for your process. There's lots of info on the MS-site on how todo that and
they provide some forms for administrators to use.
http://office.microsoft.com/en-au/assistance/HA011402911033.aspx , middle of
the page: "Enabling customized security settings for users"
Ed
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:p6kbu15ea4vtmm7tm...@4ax.com...
John Lewis
Unfortunately I can't get COMSDK to run the VO2Outlook Getting
started. It simple closes VO I tried Geoff's suggestions without any
luck.
Regards
Jihn
John Lewis
Thanks for your patience. Unfortunately clients have not got exchange
server, hence my attempts to overcome security.
Thanks for your help.
Regards
John
Gary Stark
> Hi Gary:
>
>
> Unfortunately I can't get COMSDK to run the VO2Outlook Getting
> started. It simple closes VO I tried Geoff's suggestions without any
> luck.
>
> Regards
>
> Jihn
>
Hi, Jihn <g>
I'd be checking DLL versions to sort this issue. The ComSDK does work
with 2.7 - that's what I used to produce the sample in question, so
there must be some local issue that's interfering here, and DLLHell
sounds like as good a place as any to start. :)
--
g.
Gary Stark
gst...@RedbacksWeb.com
http://www.RedbacksWeb.com
FDW
Let me know the exact VO version ( I presume you have 2740 but I need to
know for sure ). Did you get the setup from the www.comsdk.com site or
some other place? What is the date/time on that install file?
Regards
Frans
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:eqleu1pk1r66hgsdd...@4ax.com:
John Lewis
I am using VO build 2740
COMSDK130VO2735b.exe dated 19 December, 2005 @ 16:48 downloaded from
your website.
I have tried several time to reinstall it, one time in my rush I
accepted the default C:\CAVO27 instead of changing it to my d:\cavo27a
(its actually VO2.7b build 2740) so I don't know if this makes a
difference. Is it something that got stored in the registry when I
did this.
I appreciate your help and sorry to be a PIA
Regards
John
John Lewis
Further to my earlier post I just scanned my PC and found that the
install had created some folders on my C: drive as follows:
C:\Talen\Cavo2730\ComSDK\Source(PRGs)\00TsBase
The UDC, TS_Base_3_Trace.UDC was inside the 00TsBase folder. It was
this file that referenced on the UDC Tab of the properties window. I
deleted this and selected the same file but located in my
D:\CAVO27a\bin folder
I don't know if this has any bearing on the matter.
Regards
John
On Mon, 6 Feb 2006 21:18:18 +0000, "FDW"
<fdewit_Remove_@_Remove_planet.nl> wrote:
GSchaller
(But Frans will have to assist here)
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:6kpgu1lh2i70po3vu...@4ax.com:
John Lewis
Sorry, the date I quoted was the date I downloaded. I just went to
your website & redownloaded but the AEF's and REPO are identical and
dated 01/12/2004 @ 01:03 (dd/mm/yyyy)
John
On Mon, 6 Feb 2006 21:18:18 +0000, "FDW"
<fdewit_Remove_@_Remove_planet.nl> wrote:
FDW
After reinstalling my original 2716 and upgrading to A and B and then to
2740, and then importing the COMSDK I see the same problem.
The problem is in the CAVOLink.DLL, you have to downgrade to the 2735
version of the linker and all works fine. I have discussed this with
Robert and he acknowledges that there is no problem when you replace the
2740 linker with 2735 version.
Also, I will send you a 2740 verified version of the COMSDK by private
mail, if there is any other one interested in this then drop me a mail.
Regards
Frans
P.s. See you all at DevFest
"John Lewis" <datapro_...@dial.pipex.com> wrote in message
news:2oogu158oesn5bgil...@4ax.com:
John Lewis
Frans de Wit, discovered that it was the CavoLinker.dll which caused
all my problems. I replaced the 2740 dll with the 2735 dll and now I
am cooking with gas.
I have been playing with your code (see below), but can not get it to
work completely. Possibly it is because there are slight variations
in Outlook?
The Function FindWindow() did not work with the string you supplied
and I changed this to "Microsoft Outlook", instead of "Microsoft
Office Outlook"
Next I changed the string "&Allow access for" to "Allow access for"
Both the PostMessage() return TRUE but I don't see anything happen
in the dialog window
The comboBox is not enabled until you tick the checkbox, but although
you get handle to the checkbox, you don't actually Post a message to
this so I think this may be the problem.
Could you take a look at this if you got chance.
Thanks and my best wishes
John
====================================================
FUNCTION Outbreak()
// Copyright (c) 2005 Gary Stark
// gst...@Redbacksweb.com
LOCAL hWndOther AS PTR
LOCAL hWndYesButton AS PTR
LOCAL hWndCheckBox AS PTR
LOCAL hWndCombo AS PTR
LOCAL nLoops AS DWORD
LOCAL nMaxLoops AS DWORD
LOCAL cWindCaption AS STRING
LOCAL pRect IS _WINRect
LOCAL lLox, lHiy AS LONG
nLoops := 0
nMaxLoops := 25
//cWindCaption := "Microsoft Office Outlook"
cWindCaption := "Microsoft Outlook"
hWndOther := FindWindow(Null_Psz, PSZ(cWindCaption))
WHILE hWndOther == NULL_PTR .and. nLoops < nMaxLoops
Sleep( 500 ) // wait for the dialog
hWndOther := FindWindow( Null_Psz, PSZ( cWindCaption ) )
nLoops += 1
Yield()
END
IF !hWndOther == NULL_PTR
// we have a dialog
hWndCheckBox := FindWindowEx( hWndOther, NULL_PTR,
String2Psz("Button" ), String2Psz( "Allow access for" ) )
hWndCombo := FindWindowEx( hWndOther, NULL_PTR,
String2Psz("ComboBox" ), String2Psz( "" ) )
hWndYesButton := FindWindowEx( hWndOther, NULL_PTR,
String2Psz("Button" ), String2Psz( "Yes" ) )
IF !hWndOther == NULL_PTR
SetForegroundWindow( hWndOther )
Sleep( 500 ) // wait
GetWindowRect( hWndYesButton, @pRect )
?PostMessage( hWndYesButton, WM_CHAR, Asc( "A" ), 1L ) //
Returns .T.
// Uncomment the next two lines to set the Outlook
// timer to 2 minutes
?PostMessage( hWndCombo, WM_CHAR, Asc( "2" ),
1L ) // Returns .T.
?lLox := pRect.left + 30 // returns 30
?lHiy := pRect.Top + 10 // returns 10
SetCursorPos( lLox, lHiy )
Sleep( 5000 ) // wait
mouse_event( MOUSEEVENTF_LEFTDOWN, lLox, lHiy,0, 0 )
mouse_event( MOUSEEVENTF_LEFTUP, lLox, lHiy,0, 0 )
END
ELSEIF nLoops >= nMaxLoops
errorbox{ , "MS Outlook failed to start" }:SHow()
END
IF nLoops < nMaxLoops
IF Check4End( hWndYesButton )
// All is ok
ELSE
ExitVOThread(0)
END
ELSE
ExitVOThread(0)
END
On Tue, 07 Feb 2006 08:07:07 +1100, Gary Stark <bogus...@yahoo.com>
wrote: