Matt Shaw

Hi there,

Sorry to hear you ran into this. We haven’t seen any similar reports with 6.1.1 – could you please confirm if there are any errors logged?

These errors would usually be logged to the wp-content/debug.log file if you have WP_DEBUG_LOG enabled, or they might be in your server or hosts PHP error log.

Hi there,

Yes, we did release an update for the pro version as well today that contains the security fixes.

Unfortunately it’s against the www.remarpro.com forum guidelines to offer support for the paid version of the plugin, so please feel free to reach out to us at https://www.advancedcustomfields.com/contact/ so we can assist further.

Hi,

I think the source of confusion here is that the “From Name” and “From Email” settings in WooCommerce -> Settings -> Emails heavily imply that the values for these settings will be used as the From header, not the Reply-To.

If this is the desired functionality in WooCommerce, perhaps the names of the settings should be updated to “Reply-To Name” and “Reply-To Email” to better reflect what those settings are used for?

We don’t recommend using the same AWS account for all of your clients, since all of their emails will count towards the same daily send limit and send rate. Additionally, there could be some security concerns where one client could send email as another client.

However it is possible to hide the verified senders tab by defining the following constant in your wp-config.php file:

define( ‘WPOSES_HIDE_VERIFIED’, true );

I hope that helps, please let us know if you have any other questions.

Hi,

We recommend setting up a server level cron as shown here:
https://deliciousbrains.com/wp-offload-ses/doc/cron-setup/

Setting it to run once per minute would be ideal.

Hi,

If you’ve already set up the verified senders on Amazon you shouldn’t need to also set that up in the plugin – it’s just there in case you need to verify another sender.

If the plugin tries to send an email from an email address that hasn’t been verified, you’ll get a notice in the plugin settings page.

Hi there,

Do you have a server-level cron set up to process the emails? We have a doc on how to set that up here.

Hi @cowbelly,

I just wanted to give you a heads up that we’ve identified the reason for the error that you ran into and a fix will be included in the next release. Were you only noticing that error when sending emails via Wordfence?

Hi,

It looks like there’s a few issues at play here.

First, the Activity tab does need to unserialize the recipients before displaying them, but this won’t affect the sending of mail. The recipients are unserialized before the email sent. I’ve just raised an issue on our internal issue tracker so we can make sure the activity tab displays the recipients properly in the next release – thanks for the report on that.

It looks like there’s an error when adding a header to the email. Do emails work with the “wp_mail return-path” plugin disabled? There seems to be an error with that plugin as well, so I wonder if that’s related somehow.

Hi,

The notice that emails are being from an unverified email address usually means that there is another plugin configured to send emails from a sender that hasn’t been verified with Amazon.

Sometimes this can be something like a contact form plugin that is configured to send email as the submitter of the contact form – in that case, changing the plugin settings to send as a verified email address and instead using the “Reply To” for the submitter’s email address will resolve the issue.

If you’ve resolved any issues with unverified senders and are still getting email failures, your best bet is to enable debug logging as shown here:
https://deliciousbrains.com/wp-offload-ses/doc/general-debugging/

And see if anything is logged after an email fails to send.

@hmonroe,

I replied via email but adding this here in case anyone else runs into this problem –

?After further testing it looks like setting the “Reply To” setting to “headers” does actually work, but you have to change the default “From” address in Contact Forms 7 from “[email protected]” to an email address that has been verified by Amazon SES.
?
?Can you please try that and let me know if that works on your end? If not, can you share a screenshot of your Contact Form 7 settings?

Yep, you can deactivate/remove the Amazon Web Services with this version.

Thanks for your help tracking this down @svenm73 and @ov3rfly. This should be fixed in the latest version.

Hi @gfields108 and @patbell101,

I tested this out and wasn’t able to replicate this, even on PHP 7. If you’re still running into this issue, can you please reach out via https://bettersearchreplace.com/plugin-support/ with the diagnostic information from the Better Search Replace Help tab?

@tamarakorr The warning that you’re seeing with the PHP7 compatibility scan is a false positive due to some compatibility code and can be ignored – the plugin should run normally on PHP 7.

Hi @rjhob9,

Yep, this should work. Revisr just uses Git, so commits made outside of Revisr will show up inside of Revisr and the other way around.