asheroto

Thanks for that info. @elliotvs what are your thoughts on this?

The errors are not site-specific, as others have experienced the same issue. It’s related to deprecated functions that the Yoast developers would need to replace with newer methods.

Hello,

I’m not seeing an error on the website itself, just in the logs. So I don’t think a screenshot is possible for these errors.

Thanks!

Thanks so much for your quick reply and fix! Version 3.2.1 indeed fixed the issue. Much appreciated.

Haha wow, that fixed it. It didn’t fix it the other day, but I think that’s when the permissions were broken, so I didn’t think to X out again. Thanks again for your help on that.

Thanks for looking into this, your plugin works great! Appreciate the support.

Thanks again for your help. Turns out the conflict is caused by this plugin

Disable WordPress Update Notifications

Once I disabled it I no longer had that message.

Is there something I should tell the developer of that plugin to avoid conflicting with your plugin? Or is there no way to avoid it?

Is it just the way that a plugin is using the wp_mail function? How do other plugins email without issue while some fail? You mentioned it being overridden?

• This reply was modified 1 year, 6 months ago by asheroto.
• This reply was modified 1 year, 6 months ago by asheroto.
• This reply was modified 1 year, 6 months ago by asheroto.

Thanks so much for your reply.

I updated the policy and was able to get the error message in the logs to go away, however message at the top “We’ve noticed that emails are being sent from the following unverified email addresses” still appears, even though I am able to see the e-mail address in the “VERIFIED SENDERS” table and it says “SUCCESS”.

Any ideas?

Thanks, it reported several lines so I will disable them and report back.

Yes, I’m glad you mentioned the mu-plugins directory because that’s a neat trick that could be useful in the future!

As an idea for this plugin, perhaps it would help other users if you could detect if the wp_mail() function is not working and then e-mail the site administrator. There could be a “Debug” area of the plugin that could run these commands or something similar. ??

I’ll let you know, thanks again!

I am also having this issue. The odd thing is that when I run the grep for

grep -R "function wp_mail"
grep -R "wp-includes/pluggable.php"

The only plugins that come up are Jetpack. So I disabled that, but the issue still happens.

I went ahead and disabled all of the plugins that could be related to any mail function, but the issue still occurs. Using Woocommerce.

The other weird thing is that my plugins are all the same. The only thing I did differently was change PHP from 7.4 to 8.2 and then update WP Offload SES to 1.6.5. I disabled all of my plugins that could be related to this and it still shows the message.

If I use mu-plugins then it works.

• This reply was modified 1 year, 6 months ago by asheroto.

@deliciousbrains more info on this, am using 1.6.5. Looks like the plugin is trying to ses:ListEmailIdentities and ses:GetAccount on * instead of just the resource it needs That’s probably why the verification is failing.

This is from the debug.log:

[27-Aug-2023 16:49:14 UTC] WP Offload SES #203: There was an error attempting to receive your SES identities. (Error executing "ListEmailIdentities" on "https://email.us-east-1.amazonaws.com/v2/email/identities?PageSize=1000"; AWS HTTP error: Client error: `GET https://email.us-east-1.amazonaws.com/v2/email/
identities?PageSize=1000<code>resulted in a</code>403 Forbidden` response:
{"Message":"User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:ListEmailIdentities on re (truncated...)
 AccessDeniedException (client): User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:ListEmailIdentities on resource: * because no identity-based policy allows the ses:ListEmailIdentities action - {"Message":"User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:ListEmailIdentities on resource: * because no identity-based policy allows the ses:ListEmailIdentities action"})
[27-Aug-2023 16:49:14 UTC] WP Offload SES #208: There was an error attempting to retrieve your SES account details. (Error executing "GetAccount" on "https://email.us-east-1.amazonaws.com/v2/email/account"; AWS HTTP error: Client error: GET https://email.us-east-1.amazonaws.com/v2/email/account resulted in a 403 Forbidden response:
{"Message":"User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:GetAccount on resource: * (truncated...)
 AccessDeniedException (client): User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:GetAccount on resource: * because no identity-based policy allows the ses:GetAccount action - {"Message":"User: arn:aws:iam::1234567890:user/my-username is not authorized to perform: ses:GetAccount on resource: * because no identity-based policy allows the ses:GetAccount action"})

For example, the user I have has a policy that gives access to the domain. I don’t want to give this one website access to all of my SES accounts, that would be a security issue. ??

SES policy:

{
"Version": "2012-10-17",
"Statement": [
  {
    "Sid": "VisualEditor0",
	"Effect": "Allow",
	"Action": [
	"ses:VerifyEmailIdentity",
	"ses:GetSendQuota",
	"ses:SendRawEmail",
	"ses:DeleteIdentity",
	"ses:GetIdentityVerificationAttributes",
	"ses:ListIdentities",
	"ses:VerifyDomainIdentity",
	"ses:GetAccount",
	"ses:ListEmailIdentities"
  ],
  "Resource": "arn:aws:ses:us-east-1:1234567890:identity/myDomain.com"
  }
 ]
}

The other issue I’m running into is that I cannot even send e-mail if I rely on the domain to verify because of this issue, I must use the e-mail address in the resource above. Meaning, the above actually doesn’t even let me send emails, only this will work…

"Resource": "arn:aws:ses:us-east-1:1234567890:identity/[email protected]"

So what I’m doing right now is…

{
"Version": "2012-10-17",
"Statement": [
  {
    "Sid": "VisualEditor0",
	"Effect": "Allow",
	"Action": [
	"ses:VerifyEmailIdentity",
	"ses:GetSendQuota",
	"ses:SendRawEmail",
	"ses:DeleteIdentity",
	"ses:GetIdentityVerificationAttributes",
	"ses:ListIdentities",
	"ses:VerifyDomainIdentity",
	"ses:GetAccount",
	"ses:ListEmailIdentities"
  ],
  "Resource": [
	"arn:aws:ses:us-east-1:1234567890:identity/domain.com",
	"arn:aws:ses:us-east-1:1234567890:identity/[email protected]"
 ]
  }
 ]
}

Specifying both as I have verified both.

• This reply was modified 1 year, 6 months ago by asheroto.

Hello,

I am still experiencing this issue as well, using 1.6.5.

Ah thank you, didn’t think to check GitHub, of course!

Thanks, subscribed to PR.

• This reply was modified 1 year, 7 months ago by asheroto.

Thanks for your quick response on this, 1.14 working without issues!

Hi, I’ m getting this as well with the latest version.