Avoid security pop-up when sending Excel attachment in Outlook

[helgeroe]

Hi
I'm tying to send a Excel generated mail with attachment from Outlook, but get this security message:

A program is trying to automatically send e-mail on your behalf.
Do you want to allow this?
If this is unexpected, it may be a virus and you should choose "No".

Excerpts from the code I'm using:

Set oOutlook = CreateObject("Outlook.Application")
Set oNameSpace = oOutlook.GetNameSpace("MAPI")
oNameSpace.Logon , , True

Set oMailItem = oOutlook.CreateItem(0)
With oMailItem
.To = Email
.Subject = emne
.body = tekst
.Attachments.Add ActiveWorkbook.FullName
.Importance = olImportanceHigh
' .Display
.send
End With

How do I avoid this pop-up?

Would also be practical to mark the e-mail with High Importance (tried in the code, but did not work) and to flag the mail to be followed up within a date.

Using Office 2003.

Thanks.

Helge

 

[VoG]

This should help you http://www.rondebruin.nl/mail/prevent.htm

 

[helgeroe]

This should help you http://www.rondebruin.nl/mail/prevent.htm

Thanks, but did not get this to work.

Tried to use this code, but no mail is created:

Set iMsg = CreateObject("CDO.Message")
Set iConf = CreateObject("CDO.Configuration")
With iMsg
Set .Configuration = iConf
.To = Email
.Subject = emne
.TextBody = tekst
.AddAttachment ThisWorkbook.Path & "\" & sti & "\" & FilNavn & ".xls"
.Send
End With

What do I do wrong?

Also do you know how to put High Importance in a message and/or flag it?

 

[diddi]

i have just solved this problem myself...
but i didnt use CDO.

security can be blocked using 'advanced security' by mapilab (google)

its free

i have no connection with this software developer.

 

[diddi]

FYI this was my code from last week

http://www.mrexcel.com/forum/showthread.php?t=523645

 

[helgeroe]

i have just solved this problem myself...
but i didnt use CDO.

security can be blocked using 'advanced security' by mapilab (google)

its free

i have no connection with this software developer.

Thanks, but the code will be used by several different people in the organization and will be difficult to implement due to the strickt installation policy we have here.