AUGE_OHR wrote:

> did someone know what to do to get rid of the "Security" Pop-Up ?

Of course 

http://www.contextmagic.com/express-clickyes/

Maybe you also could use something like Autohotkey scripting to simulate
the click...

Thomas

Hello Jimmy,
have installed a special software by a customer, where you only have to 
confirm this securtiy message once to register your calling software. It 
is freeware, but I cannot find it again at the moment, have to restart 
my old server. But it is definitly possible to supress permanent this 
messages with a addon.
regards
Rudolf

Am 14.03.2011 08:28, schrieb AUGE_OHR:
> hi,
>
> when "send" Email with activeX via Outlook i got a "Security" Pop-Up
> on http://www.slipstick.com/outlook/esecup.htmi read "why"
>
> *** Quote ***
> The "object model guard" feature of the patch imposes two extreme
> restrictions on automating Outlook from add-ins that use either the Outlook
> object model or Simple MAPI:
>
> a.. If an add-in tries to send an Outlook message, the user gets a
> notification pop-up and must explicitly authorize or deny each attempt to
> send. The user must wait 5 seconds before the Yes button becomes available
> to click.
> b.. If an add-in tries to access address information in an Outlook item or
> the address book or to save an Outlook item as a file, the user gets a
> notification pop-up and can deny access, authorize a one-time access or
> extend access for a period of several minutes. PDA sync utilities are an
> example of the kind of application that will be affected by this
> restriction.
> The object model guard applies even if your code is digitally signed or
> running from a published Outlook form. The only way to turn it off is via
> the administrative options. Because of these restrictions, some Outlook
> features become virtually unusable, because of the number of times the user
> has to confirm the dialog boxes:
>
> a.. Sequential routing from Word
> b.. Mail merge to e-mail in Word
> c.. Automated mailing programs that use the Outlook Send method
> *** eof ***
>
> now i found
> http://www.add-in-express.com/creating-addins-blog/2007/09/12/disable-outlook-security-warnings-sending-email-messages-in-access/
>
> *** Quote ***
> Sub SendEmailMessageViaOutlookObjectModel()
> Dim olApp As Outlook.Application
> Set olApp = New Outlook.Application 'GetObject(,"Outlook.Application")
> Dim email As Outlook.MailItem
> Set email = olApp.CreateItem(olMailItem)
>
> Dim SecurityManager As Object
> Set SecurityManager = CreateObject("AddInExpress.OutlookSecurityManager")
> SecurityManager.ConnectTo olApp
> SecurityManager.DisableOOMWarnings = True
> On Error GoTo Finally
> email.Recipients.Add "user@server.com <mailto:user@server.com>"
> email.Subject = "Message subject"
> email.Body = "Message body"
> email.Send
> Finally:
> SecurityManager.DisableOOMWarnings = False
> Set SecurityManager = Nothing
> Set email = Nothing
> Set olApp = Nothing
> End Sub
> *** Eof ***
>
> but i did not have "AddInExpress.OutlookSecurityManager" in my Registry ...
> so CreateObject() fail 
> did someone know what to do to get rid of the "Security" Pop-Up ?
>
> greetings by OHR
> Jimmy
>

hi,
got it:
http://www.office-addins.com/-outlook-addins/advanced-security-for-outlook.html
regards
Rudolf

Am 15.03.2011 09:15, schrieb Rudolf Reinthaler:
> Hello Jimmy,
> have installed a special software by a customer, where you only have to
> confirm this securtiy message once to register your calling software. It
> is freeware, but I cannot find it again at the moment, have to restart
> my old server. But it is definitly possible to supress permanent this
> messages with a addon.
> regards
> Rudolf
>
> Am 14.03.2011 08:28, schrieb AUGE_OHR:
>> hi,
>>
>> when "send" Email with activeX via Outlook i got a "Security" Pop-Up
>> on http://www.slipstick.com/outlook/esecup.htmi read "why"
>>
>> *** Quote ***
>> The "object model guard" feature of the patch imposes two extreme
>> restrictions on automating Outlook from add-ins that use either the
>> Outlook
>> object model or Simple MAPI:
>>
>> a.. If an add-in tries to send an Outlook message, the user gets a
>> notification pop-up and must explicitly authorize or deny each attempt to
>> send. The user must wait 5 seconds before the Yes button becomes
>> available
>> to click.
>> b.. If an add-in tries to access address information in an Outlook
>> item or
>> the address book or to save an Outlook item as a file, the user gets a
>> notification pop-up and can deny access, authorize a one-time access or
>> extend access for a period of several minutes. PDA sync utilities are an
>> example of the kind of application that will be affected by this
>> restriction.
>> The object model guard applies even if your code is digitally signed or
>> running from a published Outlook form. The only way to turn it off is via
>> the administrative options. Because of these restrictions, some Outlook
>> features become virtually unusable, because of the number of times the
>> user
>> has to confirm the dialog boxes:
>>
>> a.. Sequential routing from Word
>> b.. Mail merge to e-mail in Word
>> c.. Automated mailing programs that use the Outlook Send method
>> *** eof ***
>>
>> now i found
>> http://www.add-in-express.com/creating-addins-blog/2007/09/12/disable-outlook-security-warnings-sending-email-messages-in-access/
>>
>>
>> *** Quote ***
>> Sub SendEmailMessageViaOutlookObjectModel()
>> Dim olApp As Outlook.Application
>> Set olApp = New Outlook.Application 'GetObject(,"Outlook.Application")
>> Dim email As Outlook.MailItem
>> Set email = olApp.CreateItem(olMailItem)
>>
>> Dim SecurityManager As Object
>> Set SecurityManager = CreateObject("AddInExpress.OutlookSecurityManager")
>> SecurityManager.ConnectTo olApp
>> SecurityManager.DisableOOMWarnings = True
>> On Error GoTo Finally
>> email.Recipients.Add "user@server.com <mailto:user@server.com>"
>> email.Subject = "Message subject"
>> email.Body = "Message body"
>> email.Send
>> Finally:
>> SecurityManager.DisableOOMWarnings = False
>> Set SecurityManager = Nothing
>> Set email = Nothing
>> Set olApp = Nothing
>> End Sub
>> *** Eof ***
>>
>> but i did not have "AddInExpress.OutlookSecurityManager" in my
>> Registry ...
>> so CreateObject() fail 
>> did someone know what to do to get rid of the "Security" Pop-Up ?
>>
>> greetings by OHR
>> Jimmy
>>
>

hi,

> got it:
> http://www.office-addins.com/-outlook-addins/advanced-security-for-outlook.html

thx,, i think this is excat what i meen with "SecurityManager"
-> CreateObject("AddInExpress.OutlookSecurityManager")

i have to look "inside" how they did it and what i miss

greetings by OHR
Jimmy

Jimmy,

>i have to look "inside" how they did it and what i miss

There are two separate products:

1) The FREE "Advanced Security for Microsoft Outlook" program, which
   replaces the default Outlook security messages and requires (some)
   User interaction. You can read about and download it here:

http://www.office-addins.com/-outlook-addins/advanced-security-for-outlook.html

2) The NOT FREE "Security Manager 2010 for Microsoft Outlook" program,
   which allows developers to programmatically bypass several Outlook 
   Security settings, when working with Microsoft Outlook. You can read
   about it and order it from Add-in Express Ltd. for €99 (or €249) at 
   the following web site:

	http://www.add-in-express.com/outlook-security/?oa

That company (Add-in Express Ltd.) also sells other products, which are
called "Add-in Express 2010" for different development environments.

Because all of those applications can disable or suppress the Outlook
security warnings, I would have to assume that any kind of application
should be able to do the same -- if you know how -- making this security
features suspiciously useless. Anyway, you could try to figure out what
those applications actually do to disable the Outlook messages and do 
the same directly in your (Xbase++) application, or you can use one or
both of those.

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas.GP@Charter.net
       Andreas_Gehrs-Pahl@EJusticeSolutions.com
       Andreas@DDPSoftware.com
web:   http://www.Aerospace-History.net

Andreas Gehrs-Pahl wrote:

> should be able to do the same -- if you know how -- making this security
> features suspiciously useless. 

This so-called "scurity" feature was useless from the beginning as it is no
big deal to create a program that watches for the Outlook confirmation
window and click "yes"

So all it does is to annoy people that only try to use Outlook for its
essential purpose - sending email.

Thomas

Jim

Well if the problem is using OutLook and you want keep all emails and 
all kind of solution are worth or need to do a lot off stuff to work ...

You can send emails via see4xb with CC or BCC to the same emamil 
account, so all emails will be in your outlook inbox.

Regards
Osvaldo Ramirez


On 3/14/2011 1:28 AM, AUGE_OHR wrote:
> hi,
>
> when "send" Email with activeX via Outlook i got a "Security" Pop-Up
> on http://www.slipstick.com/outlook/esecup.htmi read "why"
>
> *** Quote ***
> The "object model guard" feature of the patch imposes two extreme
> restrictions on automating Outlook from add-ins that use either the Outlook
> object model or Simple MAPI:
>
> a.. If an add-in tries to send an Outlook message, the user gets a
> notification pop-up and must explicitly authorize or deny each attempt to
> send. The user must wait 5 seconds before the Yes button becomes available
> to click.
> b.. If an add-in tries to access address information in an Outlook item or
> the address book or to save an Outlook item as a file, the user gets a
> notification pop-up and can deny access, authorize a one-time access or
> extend access for a period of several minutes. PDA sync utilities are an
> example of the kind of application that will be affected by this
> restriction.
> The object model guard applies even if your code is digitally signed or
> running from a published Outlook form. The only way to turn it off is via
> the administrative options. Because of these restrictions, some Outlook
> features become virtually unusable, because of the number of times the user
> has to confirm the dialog boxes:
>
> a.. Sequential routing from Word
> b.. Mail merge to e-mail in Word
> c.. Automated mailing programs that use the Outlook Send method
> *** eof ***
>
> now i found
> http://www.add-in-express.com/creating-addins-blog/2007/09/12/disable-outlook-security-warnings-sending-email-messages-in-access/
>
> *** Quote ***
> Sub SendEmailMessageViaOutlookObjectModel()
> Dim olApp As Outlook.Application
> Set olApp = New Outlook.Application 'GetObject(,"Outlook.Application")
> Dim email As Outlook.MailItem
> Set email = olApp.CreateItem(olMailItem)
>
> Dim SecurityManager As Object
> Set SecurityManager = CreateObject("AddInExpress.OutlookSecurityManager")
> SecurityManager.ConnectTo olApp
> SecurityManager.DisableOOMWarnings = True
> On Error GoTo Finally
> email.Recipients.Add "user@server.com <mailto:user@server.com>"
> email.Subject = "Message subject"
> email.Body = "Message body"
> email.Send
> Finally:
> SecurityManager.DisableOOMWarnings = False
> Set SecurityManager = Nothing
> Set email = Nothing
> Set olApp = Nothing
> End Sub
> *** Eof ***
>
> but i did not have "AddInExpress.OutlookSecurityManager" in my Registry ...
> so CreateObject() fail 
> did someone know what to do to get rid of the "Security" Pop-Up ?
>
> greetings by OHR
> Jimmy
>