Send Outlook Mail

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

I have several Access programs that send mail through pre-Security Update
Outlook 2000 clients. What is the right way to adapt this send mail routine
for such for running on post-Security update Outlook clients and skips the
prompts?

thanks
 
Steve,

Unless you are working in an Exchange environment, these prompts cannot be
turned off. If you are working in the Exchange environment see:
http://www.outlookcode.com/d/sec.htm

To work around this feature, I have been pleased with Express Soft's free
utility called "ClickYes", available for download at:
http://www.express-soft.com/mailmate/clickyes.html. It does not make the
security prompt go away, but it does use api calls to click the 'Yes' button
for you. Here is a link to a thread where you can find code that will check
to see whether ClickYes is running, start the utility, run email-related
code, and then turn the utility off. http://tinyurl.com/3x3xj

ClickYes is not the only work-around or option available; others can be
found at: http://www.outlookcode.com/d/sec.htm

hth,
 
I had the same problem and did lots of research. Basically, you have to jump thru hoops to bypass it. The easiest way it to remove the security updates. If this is not possible, I would inform management that it is not possible without an extensive amount of work. And any bypass technique is likely to be friustrated by new security updates.
 
Thanks for the info. I am indeed in an exchange enviroment. If I may ask
this - I see in the links that some reprogramming using CDO says it would
work. The server the Access VBA project runs on is a WIndows 2000 server and
has the CDO object library available. The Exchange server is on a seperate
box and it is Exchange 5.5 on NT4. Does that matter? I added the code below
to my Access file and it executes error free but no mail ever gets sent. Can
anyone help me out further?

' Reference to Microsoft ActiveX Data Objects 2.5 Library
' Reference to Microsoft CDO for Windows 2000 Library
Dim iMsg As New CDO.Message
' configure message here if necessary
With iMsg
.To = "(e-mail address removed)"
.From = (e-mail address removed)"
.Subject = "Test"
.TextBody = "*** DO NOT REPLY TO THIS AUTOMATED MESSAGE ***"
.AddAttachment \\server\share\file.txt"
.Fields(cdoDispositionNotificationTo) = (e-mail address removed)"
' finish and send
.Fields.Update
.Send
End With
Set iMsg = Nothing
 
These programs server to make my job function that much easier as well as
keep internal and external forces up to date with as little ongoing effort
as possible. So, ultimately I both need and want to solve it else I will
have to deal with the results of not solving every day. The reprogramming
using the CDO object library does not appear too intense and I have the
ability to move the applications to a Windows 200 server where this library
is already present. However, per my previous post - at the moment the CDO
code executes without error and does not prompt - but no message gets sent.
If anyone can help on why that is the case with the following code, I would
appreciate it.

' Reference to Microsoft ActiveX Data Objects 2.5 Library
' Reference to Microsoft CDO for Windows 2000 Library
Dim iMsg As New CDO.Message
' configure message here if necessary
With iMsg
.To = "(e-mail address removed)"
.From = "(e-mail address removed)"
.Subject = "Test"
.TextBody = "*** DO NOT REPLY TO THIS AUTOMATED MESSAGE ***"
.AddAttachment "\\server\share\file.txt"
.Fields(cdoDispositionNotificationTo) = "(e-mail address removed)"
' finish and send
.Fields.Update
.Send
End With

Set iMsg = Nothing



Dorian said:
I had the same problem and did lots of research. Basically, you have to
Click to expand...
jump thru hoops to bypass it. The easiest way it to remove the security
updates. If this is not possible, I would inform management that it is not
possible without an extensive amount of work. And any bypass technique is
likely to be friustrated by new security updates.
 
Answered myself, but if it helps anyone else - I thought I had coded this
too, but I must not have saved it. Once I added the code below ahead of the
message config it worked like a charm.

' Reference to Microsoft ActiveX Data Objects 2.5 Library
' Reference to Microsoft CDO for Windows 2000 Library
Dim iConf As New CDO.Configuration
Dim Flds As ADODB.Fields
Set Flds = iConf.Fields

' Set the configuration
Flds(cdoSendUsingMethod) = cdoSendUsingPort
Flds(cdoSMTPServer) = "mail.example.com"
' ... other settings
Flds.Update

Dim iMsg As New CDO.Message
Set iMsg.Configuration = iConf
 
Back
Top