Sylvain Deaure

You could try enabling the integrated logging function.
Maybe you have a conflicting plugin. This will tell.

Well,
Many plugin devs do not RTFM and break things.

Some respectable authors do, I’ve done it too.

I do not make the WP rules. If a plugin breaks the pluggable functionnality, it’s not my responsability.
The good thing to do is to warn the plugin author.
pluggable.php IS auto loaded by WP once all plugins are loaded. There is a flow to follow, or things fall apart.

Some workaround may be possible, but I’m not sure we can rely on them.

Well,

Never experienced this, just checked again right now.
When using the “production mode test”, the mail is sent FROM the email setup in the options above, TO the recipient entered in the form.

If you’ve got a rejected error, that’s because the sender is not validated for your endpoint, or you are not in production mode.

Hi,

The quotes are here to isolate the “header” word from the rest of the sentence, they are not meant to be typed in.

Just enter
headers
without quotes in the “Reply To” field.

Right.

Logging was only meant to be used as a temporary debug measure, not 24/7.

The log file is created when activating logs. Then, when updating, WordPress indeed deletes and replaces the whole directory, so the logfile is gone.

I’ll have a tought about that, thanks !

Hi,

I suppose you’re running a WP of an EC2 instance, and want to use IAM roles, right ?

For now, this is not supported.

I could add this feature if there is a significant interest.
I fear it would be limited to advanced users that understand Amazon services pretty well.

Done,

Thanks for helping !

Hi,

The error message is pretty clear : you’re using a sender email that is not verified by amazon. So amazon won’t send it.

You can only send a mail with SES if it’s sender is validated for the region you use.
If you need another email being shown, use “reply-to”.

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

Hi,

It looks like the error is printed by the form plugin itself.

It is however important to print it, because it shows that your setup is not right :
you use a user form to setup the sender email.

This sender email my not be amazon verified (it has no reason to be), so the mails won’t get sent.

You should use reply-to header field instead of sender.

Hi,

“wp_mail already defined in […]/pluggable.php”
This means that another (badly coded) plugin did force inclusion of pluggable.php file.
This file should NOT be manually included, it is loaded by the WP core.
When it is force loaded by a plugin, this breaks all pluggable WP functions, so the mail one.

Check your other plugins file for “pluggable.php” string, you’ll find the culprit and could advice it’s author to correct his code.

Hi,

Many thanks Jeremy for the notice.

@diglett, this was just a deprecated call, no hurry yet, but I applied the pull request anyway.

It’s live.

Hi,

I can’t audit nor test all other plugins.

As far as the plugin does NOT rewrite the wp_mail() function nor use a custom email implementation, it should be fine.

But I can’t make any guarantee on behalf of other plugins, so you’ll have to give it a try ??

Glad to hear,

Thanks for the feedback!

Hi,

You server date time is not up to date, thus the request timestamp is wrong and the Amazon API won’t validate.

Update you server date/time and keep it in sync.

• This reply was modified 7 years, 5 months ago by Sylvain Deaure.

Ok,
Tagging as resolved as this is a hosting issue, nothing related to the plugin itself.