Now fails for Outlook web mail report

ScottStalheim · June 2021

Now with success on GMail web mail reports, I thought to give it a try with Outlook and Azure. After some fiddling with the settings to match (Azure and RB), I get pretty far, to the point I get the web browser message ""Success. Please Close Browser". But then no email draft comes up or is sent, unlike the case with GMail. Generally I get no error messages, except a couple times I got "class EHTTP/1.1 400 Bad Request".

I register the Outlook 365 plugin. Is there likely something on the Outlook side I still need to do, like verifying my app, or might there be something going on with RB here? Thans.

Scott S.

nicocizik · June 2021

Hi Scott,

I'm glad you got the Gmail web plugin working with the new architecture changes.

For Outlook, try implementing the OnEmailError event of the plugin and see if that gives more insight to what is happening. Generally it will give a more descriptive response than "Bad Request".

See the following article on how to implement this event.

http://rbwiki.digital-metaphors.com/output/email/how-to-show-email-errors/

ScottStalheim · June 2021

Thanks Nico,
I wondered about the "SMTP" in the RBWiki code example, since this is web mail, but it seems to work.
Showing the errors reveals:
"public clients can't send a client secret"

I am a bit puzzled since a client secret seems to be needed. Perhaps I should just remove this Azure application and start it over. There were some options on starting I do not see now, and I opted to make the app as public as possible. Also azure help asks if I am calling API's - and perhaps within RB, I am calling API's?

Scott

nicocizik · June 2021

Hi Scott,

I believe this error comes from registering a public application (or mobile/desktop application) with Microsoft. Be sure you are creating a Web Application with a redirect URI as http://localhost and see if that solves the problem.

Now fails for Outlook web mail report

Comments