Sending Mail with CDO

BrianWren · April 13th, 2009, 11:23 AM

Code:

In Proj.vbp, have the following reference:
 
Reference=*\G{3FA7DEA7-6438-101B-ACC1-00AA00423326}#1.15#0#_
..\..\..\Program Files\Common Files\System\MSMAPI\1033_
\CDO.DLL#Microsoft CDO 1.21 Library
 
In code, I have:
Public Sub MySendMail(argTo As String, _
                argMsg As String, _
                argSubj As String)
 
On Error GoTo Er
 
Dim mSn    As New MAPI.Session
      Dim ...
 
mSn.Logon "brian.wren"          ' This initiates a 
                              ' long wait, followed
...                             ' by two Dlg.s.

This is problematic for me. I am testing the proof of concept with this, and, if it flies, this will be incorporated into an .EXE that runs unattended on a server, having been started by TaskManager, and therefore having no desktop (at least not a visible one.)

That means thet no one will be able to service the dialogs, should they pop up.

What do I need to do to make it so that logging on using CDO doesn't raise a warning?

I know that âtrustâ and âtrust relationshipsâ are becoming quite an issue, but I donât know if this involves that technical term. So I would like to know what it does involve.

But even if this is a âtrust relationshipâ issue, I don't know how to establish sufficient trust to qwell the message that pops up.

The message is ...

Well. Just now I retried it to get the text of the elements. .Logon does create a long wait, but, it was the line:

Recipients (AS MAPI.Recipeints) .Resolve

that raised a complaint:

Code:

__________________________________________________________
[ Microsoft Office Outlook                             [x] ]
 
/!\ A program is trying to access email addresses you have
    stored in Outlook.  Do you want to allow this?
 
    If this is unexpected, it may be a virus & you should
    choose "No."
     _                     ________________
    [_] Allow access for  [ 1 minute   [\/]] <ââ<< Drp-dn
      _________     ________     __________
     [   Yes   ]   [   No   ]   [   Help   ]
      Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯     Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯     Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯Â¯

msg.Send raises a similar error.

gbianchi · April 13th, 2009, 01:14 PM

As far as I know, this doesn't have anything to do with VB, it relates Outlook security. Anyway, Maybe you can just trace the outlook windows and press the buttons (all done within the program).

Did the pop up raises if you use a control within a form??? (just curiosity)...

vb5prgrmr · April 16th, 2009, 02:51 AM

Just like having a form appear from an icon in the task bar...could you not use a form even if it is a simple about form to contain the control and use a timer to make sure the form closes in a few seconds so as not to interfere too much with your process. Just a thought...

Then the other though is the MAPI API of which you will find defined in the same folder as the win32 api file but I am not sure as I can't remember where I put my example code but I know there is some out there (and maybe even on this site in some archive as I remember a book about MAPI).

Good Luck