MS Access CDO mail error - office 365 outlook

[kashabhi2003]

Hello Folks

I have researched a lot, but can not find myself out of this issue. I am creating a Database in Access 2010, where I need a functionality to send alerts via Office 365 outlook.
I got a piece of code that works for Outlook desktop, and have tried to modify it for Office 365 outlook.
But I am facing a Runtime error: "The server rejected the sender address. The server response was: 530.5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM".
Have tried several things, but nothing works. Any help would be appreciated.

 

[sneuberg]

There seem to be information out there on this. If you google "530.5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM" you will find this thread which looks similar to your problem.

 

[gemma-the-husky]

I am convinced that A2003 is just not compatible with Outlook 2013

this code

dim OApp as object
set OApp = createobject("outlook.application") fails in A2003.

I have not tried with A2010, but possibly that also fails. I imagine most users of 2013 have a full Office 2013 suite, so maybe this is something that affects anyone using O2013 and an earlier version of Access.

It is noteworthy that A2003 and A2010 reinstall over each other, but A2013 does not cause A2003 to need a reinstallation, so the object model is clearly different.

Can you try your code with A2013. (even a run time version) I would fully expect it to work properly.

 

[sneuberg]

Can you try your code with A2013. (even a run time version) I would fully expect it to work properly.

I tried his code on my Office 365 (Access 2013) system and I get the same error.

 

[The_Doc_Man]

At my last work site before I retired, I got this same exact error using SMTP/CDO to send mail to our own in-house SMTP mail gateway server. The problem for us was security, not anything wrong with CDO or SMTP mail.

Check with your security guys for having implemented host-based security systems that care not only about where you send it and who sent it, but HOW you sent it. My site's solution was to identify not only that I was sending SMTP mail to xx.xx.xx.xx but that MSACCESS.EXE was the originator. That fixed the problem. Also see if there is a firewall-based rule that would apply. Your security gurus would have the answer both to HBSS and firewall rule issues since they usually handle both of those components.

 

[LukeChung-FMS]

Here's a new paper we wrote that offers additional information on how to configure Office365's SMTP server to allow email relaying and mailbox delegation. Those things need to be setup properly before Office365 allows you to use the SMTP server.

There are also two login options:

1. A specific email account or
2. Authorized IP address of the sender

http://fmsinc.com/MicrosoftAccess/Email/smtp/index.htm

Hope this helps.