Outlook 2003 - How to allow programmatic access

  • Thread starter Bruno Campanini
  • Start date
B

Bruno Campanini

I would like to send mail from Access withoung appearing that warning
"Sambody is trying to send mail..."

Bruno
 
V

VanguardLH

Bruno Campanini said:
I would like to send mail from Access withoung appearing that warning
"Sambody is trying to send mail..."

Bruno

Are you using the same version of Access as you have for Outlook (are
both 2003 versions)?

Otherwise, you could use Mapilab's free security add-on to let you
decide which programs it will remember as having secure access to
Outlook.

http://www.mapilab.com/outlook/security/
 
V

VanguardLH

Bruno Campanini said:
VanguardLH formulated on Sunday :


Is there any other way to do the job without using add-ins?

http://office.microsoft.com/en-us/o...k-security-template-settings-HA001140295.aspx

This looks to be how an admin in a corporate network (domain) would
modify a policy that gets pushed on the company's workstations when they
log into the domain. If you have a version of Windows that includes the
local policy editor or the group policy editor, you can add (import)
security templates; however, this article doesn't give a link to
download the .adm template file so I suspect it refers to a standard
policy available at the server/domain host. All policies are registry
settings so it is also possible to research which registry keys and data
items are associated with each policy but quite often that info is
buried or so rarely touched upon that a general online search won't find
the info. You never mentioned your host is in a domain (i.e., that you
log into a domain) and I didn't see a template download so you could
import it and then modify your own security settings against Outlook.

The problem is not that Access is using Outlook to send e-mails but that
Access, the way you are using it, wants to access the contacts list
(address books) defined in Outlook. If the macro in Access provided the
e-mail addresses then it wouldn't need to be scanning through your
address books.

When you installed Office 2003, I suspect you excluded installing the
CDO interface between Office components (or it is configured that way by
default in the installer). Have you gone into Add/Remove Programs,
reran the installer (select Change), and checked if the CDO feature is
enabled or not? When you see the tree list of components and the
features under each, look under the Outlook component for the CDO
feature. CDO is listed for Outlook back in 2003 but eventually
Microsoft dropped it so it isn't even listed in a custom install for
Office 2010 (I don't know about the installer's tree choices for 2007).
From Office 2007, the Trust Center dialog took care of allowing
programmatic access -- but you're back on Office 2003.

CDO has security flaws and malware made use of its vulnerabilities so it
was eventually discarded (by defaulting to exclude it in an install of
Office). Malware could use CDO to spew spam to all your contacts listed
in your Address Book. That's why I mentioned using the Mapilabs add-on.
Instead of letting *any* program access to your Address Book via CDO,
you decide which program has access via the add-on.

http://www.outlookcode.com/article.aspx?ID=52
http://www.outlookcode.com/archive0/d/sec.htm

I've ran into programs that used the Redemption model. The problem is
every redemption module has to be coded for the specific program, so
each such program has its own redemption module. You could end up with
many redemption models whose code is 99% the same except for certifying
the program that uses a particular instance. If there is a problem or
error in Redemption, you can't tell which program's instance of it had
the problem or error.

Back in Office 2003, the Mapilab add-on is your best choice.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top