All Office 365 Routed to Sent Mail

So this is the default for the way I’ve setup the application (to store all sent mail in your sent mail folder of the account you’ve linked to WordPress). I may in a future release provide the option to disable this in the plugin settings, but it would have to be an all or nothing setting. I.e. you either store a record of your sent mail sent via WordPress, or you don’t.

I don’t think this is a DNS issue, it is a difference between the tenancy you have linked to WordPress via the authorisation app used by the Graph API, and the actual account you have attempted to authorise with this app (explained in response to your previous issue titled “parsererror elementor contact form”).

• This reply was modified 4 years, 2 months ago by edwardcross.
• This reply was modified 4 years, 2 months ago by edwardcross.

Hi….

I am just re-reading your response(s) and it hit me that you said your plugin only sends contact form email to Office 365 to SENT MAIL ONLY ?

Ideally, I would like to send contact form submission to 3 Office 365 user IN BOXES.

Is that NOT an option, or am I reading ou wrong ?

I did manage to route the contact form to my gamil address so I can at least monitor any new customers for my client.

The test form submission also went to my O 365 client’s SENT mail box.

Here is the header info for the contact form submission.

from: Peter Barber <peter@jaggroupllc.com> via jaggroupllc.onmicrosoft.com
to: “pat@clickdujour.com” <pat@clickdujour.com>
date: Jan 20, 2021, 3:15 PM
subject: New message from “Jag Group LLC”
signed-by: JAGGROUPLLC.onmicrosoft.com
security: Standard encryption (TLS) Learn more
: Important according to Google magic.

So the plugin simply makes a single Office 365 account the mail server for your WordPress site. You cannot attribute more than one Office 365 account to your WordPress site, although you can set the plugin to send from a shared mailbox linked to your Office 365 account. However, it can only send from either one of these at any one point (not both), and you need to set which in the plugin settings if seeking to send as another account.

As it makes your Office 365 account the mail server for your website, the plugin therefore tells Office 365 to record any emails sent from your Office 365 account’s mail servers. In the same way that if you send an email from your office 365 web account, it will log that email in the sent folder of said account.

You can of course send an email from your office 365 account to that very same account (as you can with any email account). You’ll just see the sent email within both your sent items and your inbox (as the mail will have originated from the same account).

In the context of your client therefore, you need to be setting up the azure active directory using your Client’s office 365 account details. You then need to be signing into this account when clicking the authorise button within the plugin settings. This will mean that any email sent using wp_mail() within wordpress gets sent from this clients office 365 account.

They can then set any contact form to send a copy of the email to that very same account, but it will also be logged in the sent mail folder of said account, given that that was the account said email will have been sent from.

Hope that makes sense :D.

Whew !

I getting kinda burnt out from all this Office 365 research.

??

I am gonna try and resolve this – but if I can’t – will deactivating and removing your plugin SAFEFULLY reverse / remove all the settings from O-365 / Azure ?

I read your info on the proper way to remove worpress plugins.

Does yours have the option to remove all related database files ?

Or will I have to remove them manually via the database ?

So WordPress can’t remove any setting from Office 365 / Azure. That would be quite a big security issue if it could!

However, what my plugin does have is the ability to remove any access and refresh tokens received through the OAuth authentication process with Microsoft Graph, along with the client secret, tenant id etc. you will have stored within the WordPress database via the plugin settings page.

Given that access tokens expire after an hour, this isn’t so much of an issue if left in the database. However, the refresh tokens (used to get a new access token on expiry) remain valid for up to 90 days if not used. Similarly, the client ID can be set to never expire within Azure Active directory (although the default is 1 year I believe) Hence, if people wish to remove my plugin, I’ve provided the facility to remove all the data from WordPress’s database. However, you can also set it to keep the data, in case you’re only seeking to temporarily disable/remove the plugin and plan to install it again in the near future.

If you do remove the plugin and delete the data in the WordPress database, you may also wish to remove the client ID/delete the authentication app created within Azure active directory. I would certainly do the former at least. However, both will have to be done separately within the Azure Active Directory interface.

I hope all my support questions can at least help others.

Thanks for all the info – and the prompt responses !