edwardcross

@nadim322 I think you’ve falling in Microsoft’s trap of there being two values when generating the client secret. For some reason Microsoft shows a copy button for both the secret ID, and the secret itself. If you copy the ID rather than the secret, you’ll get this error.

Unfortunately you won’t be able to view the secret again. You’ll have to delete it and recreate it. However, make sure you copy the secret value this time around, and not the secret ID.

@steadynow hi sorry, I’d updated my Cloudflare origin certificates and was forgetting this website depended on them too. The site is back up and running now.

@larissaf15 I haven’t provided this facility, as to me this should be done at the mail server level (not my plugin), given its the Microsoft mail server that is sending the message. One assumes the from name for the Microsoft account is consistent and doesn’t change.

@idsec yep, I know logging would be very useful, but my basic understanding of PHP error handling doesn’t seem to result in a working logger I’m afraid. I haven’t had the time to investigate what I’m doing wrong, and it seems to only be bespoke setups where there are issues (primarily related to Microsoft licencing and API and mailbox configuration). Its on the list, but no guarantees I’ll get something to work logging wise I’m afraid.

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

@webctrl so this is a Microsoft setting rather than my plugin. The exact steps may depend on your licence. However, this guide may help: https://docs.microsoft.com/en-us/microsoft-365/admin/add-users/give-mailbox-permissions-to-another-user?view=o365-worldwide

@exetico thanks for the feedback, I know the logging is an area for significant improvement, but I’m afraid my PHP skills haven’t focused that much on error handling. I did try and make a log handler, but it seemed to crash WordPress and I haven’t had the time to figure out best practice as yet. I’m sure its exceptionally simple and I’m doing something silly.

@one3rdnerd that message would suggest to me that the database still contains the pre-version 1.8.3 authentication object which isn’t namespaced.

Version 1.8.3 onwards searches for a namespaced object in the database, hence you’ll get an error about an incomplete object, as the object exists but not as the plugin expects.

To get around this, as stated on the main page of the plugin, you need to reauthorise to overwrite the object with the new namespaced object.

@meltra the plugin will use oAuth tokens for authentication and not username and password, so it doesn’t matter which option you choose. However, to get the tokens in the fist place, you have to authorise with your username and password.

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

@larissaf15 thanks for the question, I assume you are using the plugin to send notification emails to an administrator type account, as the plugin itself does not receive mail, it only sends (or more specifically, relays messages to a Microsoft mail server).

There are a whole manner of reasons why your emails might be being blocked, and its very unlikely to be the plugin setup.

I assume, given you know something is being blocked, then it is being sent (so the plugin is doing its job correctly). What you need to check therefore are the email headers of one of these blocked emails, as that will tell you what’s going on, and it will most likely be down to your mail server setup.

Common issues are, using a mail server that isn’t allowed by the domain that the from email address is linked to (this will show as an SPF record error in the mail headers). Your mail server may also have strict filtering of emails without valid DKIM records, you can change this (or simply ensure your DKIM record is correct in the domain linked to the from address).

These are just some potential reasons, but it could well be something else entirely. That’s why its vital to look at the email headers and get someone that knows what they’re looking at to review them (or one of the free tools out there on the web).

Ed

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

Given I haven’t heard anything back on this I’m closing.

So by default WordPress will use the admin email of the site. It sounds like this is not the same as the office 365 address. If so, this could explain why you’re not receiving anything, as Office 365 will effectively be spoofing the address, and spam filters with pick up on this.

The form should be set so that the from address is the address of the office 365 account in question, the reply to address should be the address of the enquiry/form submitter (if applicable).

Ed

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

@bethangela so that will depend on your form plugin, not my mail plugin, in the same way that who you send your email to is entirely down to who you choose to put in the email form fields of your email client software. The mail server will simply process the email request and send it accordingly to the named recipients.

If instead you mean you want to have multiple versions of my plugin authorised with different office 365 accounts, and multiple forms sending information from one of these different office 365 accounts – the answer is no, that is not possible with this plugin.

Ed

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

@rogerpz81 so I can’t replicate this. Out of interest if you disable my plugin do you still get this error. Given I’ve now namespaced the libraries my plugin uses, I would expect the cache plugin to still be failing without my plugin enabled. If it still fails, the reason is because the cache plugin is requiring GuzzleHTTP, but isn’t loading it.

My plugin was previously loading the GuzzleHTTP library without namespacing, so the cache plugin could have been piggybacking on that, but now I’ve namespaced it (to avoid conflicts with plugins that are loading libraries without namespacing them), you’re getting an error, as it can’t find GuzzleHTTP.

This is my hunch, based on the error, and the fact the only change is that I’ve now namespaced the libraries (ironically to avoid conficts…)

@cgoro I assume, as it’s been over two months that this was fixed so I’m closing.

@danish20 I think this is probably resolved in the latest version.