This will be the FAQ page for WP SES Plugin.

Fell free to shoot your questions below as a comment.


Q:I installed WP SES on my WP install and was able to get everything tested and the test emails work great. The only thing is I can’t get it to intercept the emails my contact form sends. They end up going through the normal SMTP route and not SES.

This is the function for the mail: mail($to, $subject, $message, $header);

A: Looks like your contact form does use php builtin mail() function instead of WP core function.
That’s why the plugin can’t intercept it.

Please change to
wp_mail($to,$subject,$message,$header);

Be aware that right now, $header would be ignored by the plugin, so if any extra info was there, it would be lost (not a concern for standard usage).


Q:I used my ID and secret and repeatedly put them into WP SES, but it didn’t work, I also generated a new ID and secret too, but to no avail it still didn’t work.

A:
Did you use these keys before with another service (like s3), did they worked with another service ?
Did you sign up for the SES service ?
Then, please paste the error message you got when trying to verify a sender address (top of the screen). This will tell what is wrong with your keys (bad auth, no ses subscription , aso)


Q:Some plugin requires mail_filter , it’s not taken care of in wp_ses

A: You can try this :
wp-ses.php, around line 331, below
function wpses_mail($to, $subject, $message, $headers = '') {
Insert the following line:
extract( apply_filters( 'wp_mail', compact( 'to', 'subject', 'message', 'headers' ) ) );
it should do the trick.


Q:The “forgotten password” link is stripped from the email.

A: Jonas kindly gave a fix :
Here is the fix for the url problem:

Change wp-ses.php:334 from
$html = $message;
to
$html = preg_replace('/< (http:.*)>/', '$1', $message);
The s need to be stripped from the html version of the message as well. Apparently AWS was running a strip_tags on the html version too.

106 Comments → “FAQ”


  1. Dave

    12 years ago

    Are you planning on including a DKIM signing/support feature?

    Reply

    • admin

      12 years ago

      Hi Dave,

      Yes, it’s definitly something I want to include in a future release.
      The goal is to have the best delivrability, and DKIM are part of this.

      Reply

  2. lolo

    12 years ago

    Hi,

    I cant’t make it work with mailpress. Any ideas?

    works great with other plugins! thanks

    Reply

    • admin

      12 years ago

      Hi,

      Thanks for asking.

      Mailpress does redefine the default wp_mail function.
      This can only be done once.
      So wp-ses and mailpress are not compatible with each other.

      I think this could be solved by writing a mailpress add-on

      It’s on the todo list…

      Reply

  3. dan

    12 years ago

    Do you have a list of mail plugins that are confirmed to work with WP-SES?

    Reply

    • admin

      12 years ago

      Hi Dan;

      WP-SES should work with any other plugin that does not redefine pw_mail function.
      any plugin that works with wp_mail_smtp, for instance, should work with WP-SES instead.

      I can not give an extensive list, but if you send me compatibility or incompatibility reports, I could list them here.

      Reply

      • dan

        12 years ago

        ALO Easymail Newsletter works & obviously mailpress doesn’t.

        Any reports on “mailing list” or any other lightweight mailing list managers? (Don’t need anything special for composing, multiple lists, etc)

        Reply

        • dan

          12 years ago

          actually, I have to take the last back; wp-ses seems to strip half of an activation link and the subject out of activation emails. Would you like me to get you in touch with the ALO easymail guys?

          Reply

        • admin

          12 years ago

          Hi;

          I will have a look at ALO easymail, thanks for letting me know !

          Reply

  4. Chris

    12 years ago

    After activating the plugin and filling in the settings, the settings page (admin page) no longer displays. I cannot make changes to the settings or test any of the functionality.

    WordPress 3.1.

    Chris

    Reply

    • admin

      12 years ago

      Hi Chris,

      Make sure your host does support the php CURL extension.
      Php5 will be needed, too.
      Those requirements will be stated in the next version, sorry for the inconvenience.

      Reply

      • Chris

        12 years ago

        That fixed it. Thanks!

        Reply

  5. Flavia

    12 years ago

    The plugin is great, thank you!
    Only I found a problem when sending the “Lost your password” mail, I think because the mail is not encoded in UTF-8. The Lost your password mail then looks like this for the end user:

    Someone requested that the password be reset for the following account: http://mysite.com Username: testuser If this was a mistake, just ignore this email and nothing will happen. To reset your password, visit the following address:

    So the URL is not even visible for the user (even though if you look at the mail source you can see it).

    Thanks!

    Flavia

    Reply

    • admin

      12 years ago

      Thanks,

      I’ll have a look into it !

      Reply

    • Mike

      12 years ago

      I confirm the issue with the forgot password feature. Actually, when I submit the forgot password field, I get this:

      Warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set in /home/xxx/public_html/web/wp-content/plugins/wp-ses/ses.class.php on line 493

      Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/web/wp-content/plugins/wp-ses/ses.class.php:493) in /home/xxx/public_html/web/wp-includes/pluggable.php on line 934

      but the mail does send, and does NOT contain the URL as the other guy described too.

      Reply

      • admin

        12 years ago

        Hi Mike,

        The URL in the mail will be fixed soon.
        As for the warning (not a bug nor an error), it’s because of the php settings (safe mode), you can ignore it as far as the message are sent.

        Reply

        • Mike

          12 years ago

          I’m getting this on a white page when I register on the site:

          Warning: curl_setopt() [function.curl-setopt]: CURLOPT_FOLLOWLOCATION cannot be activated when safe_mode is enabled or an open_basedir is set in /home/xxx/public_html/web/wp-content/plugins/wp-ses/ses.class.php on line 493

          Warning: Cannot modify header information – headers already sent by (output started at /home/xxx/public_html/web/wp-content/plugins/wp-ses/ses.class.php:493) in /home/xxx/public_html/web/wp-includes/pluggable.php on line 934

          The registration email with password IS sent, but I can’t have this page coming up when people register on the site.. Any fix?

          Reply

          • admin

            12 years ago

            Hi Mike;

            You can try to uncomment line 493 of wp-ses/ses.class.php


        • Jonas

          12 years ago

          Hi

          Were you ever able to fix the problem where the URLS for forgotten password links were being stripped? I did not see a fix but attempted to roll my own by removing the s before calling strip_tags in wp-ses:334. See below:
          $html = $message;
          // Keep Important URLS from being stripped out
          $txt = preg_replace(‘//’, ‘$1’, $html);
          $txt = strip_tags($txt);

          This leaves the URL in the the message string, but for some reason link is still missing from the actual email. Is AWS SES itself stripping it out? I notice that the email also contains the main site URL which is not being stripped.

          How are others getting around this?

          Thanks!

          Reply

        • Jonas

          12 years ago

          Here is the fix for the url problem:

          Change wp-ses.php:334 from
          $html = $message;
          to
          $html = preg_replace('/< (http:.*)>/', '$1', $message);
          The s need to be stripped from the html version of the message as well. Apparently AWS was running a strip_tags on the html version too.

          Reply

          • admin

            12 years ago

            Thanks a lot, Jonas.

            Faq Updated, will be in the next release.


  6. David

    12 years ago

    Works great. Thank you. Two suggestions:

    a) You can have several different email addresses verified by Amazon. You should be able to select from them in your code when sending email out.

    b) you should also allow people to override the sender name for even the current default send address. Amazon requires the actual email address to be verified, but the “from name” can be anything you want. We sometimes send emails out from the From Name “Newsletter” and some as “Welcome” etc. We can work around this limitation by overriding the global $wpses_options[‘from_name’] prior to sending, but it would be a little cleaner if the plugin would allow for you to change it directly. To be backward compatible with wp_mail, you probably should just parse the headers and use any name that is passed as “From: xyz” (ignoring the ) part…

    c) the stats page is basically unreadable because it comes out in a totally random order. We send out emails all day long, and when we run the report, the dates/times are all mixed up. I would suggest you do a uasort() based on $point[‘Timestamp’].

    Reply

    • admin

      12 years ago

      Thanks for the feedback, David;

      I do take note of your suggestions for the next version.

      Sylvain

      Reply

  7. Bharath

    12 years ago

    Hi,

    I liked the plugin! I am able to send full test mails to the confirmed addresses, but not being able to send any mails to any other addresses. The message I get is SES returned – null for confirmed addresses, I get an alphanumeric string.

    How do I fix it?

    Thank you.

    Reply

    • admin

      12 years ago

      Hi;

      I Guess you are still in sandbox. You need to go into production mode. See the Amazon SES page for more details:
      http://aws.amazon.com/ses/

      Cheers,

      Sylvain

      Reply

  8. Bharath

    12 years ago

    Hey I realized from the SES docs that I was sandboxed and had to go to http://aws.amazon.com/ses/fullaccessrequest to get full access. It would be nice if your plugin could detect this and point new users this link. I am now awaiting full access.

    Reply

    • admin

      12 years ago

      Ok, great !

      Reply

  9. Scott

    12 years ago

    Just set up WP SES, and everything is working great! One small issue that I reported here: http://wordpress.org/support/topic/plugin-wp-ses-one-minor-php-issue?replies=1#post-2142937

    Otherwise, things are fantastic – thanks for the wonderful plugin. Looking forward to the future releases!

    Merci!

    -Scott

    Reply

  10. RJ

    12 years ago

    Great plugin Sylvain! Many thanks. I echo @Davids suggestions of being able to choose which “verified” email address to send mail from and also support for the “reply-to” address would be awesome.

    Cheers,

    Richard

    Reply

    • admin

      12 years ago

      Many Thanks !

      All taken note and will be in next release.

      Reply

  11. Gilad

    12 years ago

    Hi

    We like WP-SES very much. However we have a conflict – another plugin that is important to us is doing an

    add_filter (‘wp_mail’, …) ;

    WP-SES currently replaces wp_mail but does not enable the wp_mail filter chain.

    I want to emphasize – the other plugin is not replacing wp_mail but only chaining itself as we showed above.

    Is there any way for us to use WP-SES and still use the other plugin?

    Thanks!

    Reply

    • admin

      12 years ago

      Hi Gilad,

      Thanks for the comment.
      That’s a feature request I’ve had.
      wp_mail filters will be used in the next release.

      Thanks,

      Sylvain

      Reply

      • Gilad

        12 years ago

        Awesome. Thanks.

        Any idea when that will come? Or a workaround we could use in meantime?

        Thanks again for the great plugin functionality.

        Reply

        • admin

          12 years ago

          Well, in the meantime you can try this :

          wp-ses.php, around line 331, below
          function wpses_mail($to, $subject, $message, $headers = '') {
          Insert the following line:
          extract( apply_filters( 'wp_mail', compact( 'to', 'subject', 'message', 'headers' ) ) );
          it should do the trick.

          Reply

          • Gilad

            12 years ago

            Thanks! A quick check seems to indicate that it works.

            I’ll get back if there are further issues/questions. We really appreciate the quick response.


          • admin

            12 years ago

            You’re much welcome,

            Sylvain


  12. Joe Lipson

    12 years ago

    Hi Sylvain, Thanks for the plugin, it’s great.

    I made a quick change that fixed a problem I was having.

    When I first installed the plugin the WP admin screen was messed up and had PHP source code sprinkled through it. The cause was a single PHP short opening tag ( <? ) at line 115 of of the file admin.tmpl.php. I changed it to <?php and everything is great.

    cheers

    Joe

    Reply

    • admin

      12 years ago

      Hi Joe,

      Thanks for the fix.
      You’re right, short tags are deprecated.

      Reply

  13. Galakto

    12 years ago

    Hi,

    great plugin. There is one thing that makes me a little uncomfortable though. I host websites on AWS and I give full WP control to the owners. THe problem is that they can go to the plugin admin page and see my AWS credentials. Any way to fix that?

    Thanks.

    Reply

    • admin

      12 years ago

      Well;

      No much you can do since you give admin access.
      You could hardcode your credentials into the plugin, but I guess an admin user could as well view the plugin source and get the credentials.

      The best solution would be to use the client credentials, not your own.

      Reply

  14. Brian

    12 years ago

    I’ve been using the plugin for some time, but today I’m having problems. Whenever I activate the plugin in production mode it says it is active, but when I leave the page I get the warn that it is inactive. Sure enough, when I visit the activate page it is inactive.

    It’s like a light switch that turns itself off whenever you turn it on. Any thoughts?

    Reply

    • admin

      12 years ago

      Hi Brian;

      Didn’t saw this problem.
      I guess all other checks are “green”, and you didn’t change your sender email ?

      Does the mail test (to your confirmed email, before activation) work ?

      Reply

      • Brian

        12 years ago

        Yeah, everything else was green and the production test works and sends email to my other accounts.

        I had used the plugin for many months successfully so I presume it was a conflict with another plugin. It only showed up when I had to uninstall all my plugins and reinstall them to diagnose an RSS feed issue.

        I ended up going through the plugin and looking for every place where you set the plugin active variable to 0 and changing it to 1. This forced the plugin to not deactivate itself on me and it now works.

        I realize that this is a hack and as a former developer this doesn’t help you much. I should have done it situation by situation so I could have giving you the exact case that was trigger it go back to 0 again. However, I really just needed to get things in a working state again.

        Reply

        • admin

          12 years ago

          Thanks Brian,

          I do understand. I will check it for the next release.

          Reply

          • Veselin Kantsev

            12 years ago

            Brian is correct,
            it appears to be a conflict with another plugin or at least SES assumes so.

            If the check on line 379 in “wp-ses.php” is disabled, the “Another plugin did override wp-mail function” warning is shows up in the SES Options page while the plugin remains “Activated”.

            Otherwise it deactivates itself and the “Simple Email Service is not fully activated” message appears.

            Regards,
            Veselin


          • admin

            12 years ago

            Thanks Veselin,

            So the check is broken, and it appears to be another plugin that does use it’s own wpmail function.
            wpmail can only be overriden once, so there is no solution other than to modify one of the two plugins to integrate the other one’s functionnality.

            Brian, if you can identify the conflicting plugin, I’ll try to check.


          • Brian

            12 years ago

            I think I can narrow the conflict to one of two plugins. I’ve used wp mail smtp (http://wordpress.org/extend/plugins/wp-mail-smtp/) and TDO mini forms (http://wordpress.org/extend/plugins/tdo-mini-forms/). One or the other (or both) is likely to overwrite the mail function I think.

            I’ve also used WP-email (http://wordpress.org/extend/plugins/wp-email/), but I don’t think that is it as I’ve been able to edit that plugin to work with this.


          • admin

            12 years ago

            Sure, wp-mail_smtp does rewrite the wp_mail function to use smtp.
            Can’t use smtp and ses at the same time.


          • Brian

            12 years ago

            Yes, I wouldn’t use WP Mail SMTP at the same time, but just having it deactivated seemed to cause an issue, which I thought was very weird. (Unless it was the TDO Mini forms or another plugin that was causing the problems.)

            I was replacing WP Mail SMTP with WP SES so that I can send things through SES which I’ve found to be more reliable than the gmail hack.


  15. RJ

    12 years ago

    Hi Sylvain,

    Just another question; we’re having problems with “BCC” emails not being received through WP-SES. The “TO” address works fine, but any email addresses in the “BCC” field are not delivered.

    Is anyone else having this problem?

    Any help much appreciated.

    Cheers,

    Richard.

    P.S. Any news on when the next release is coming… would love to have support for the “reply-to” address and the option to send from any “verified” email address as well.

    Reply

    • admin

      12 years ago

      Hi Richard;

      wp_mail does only use the TO: field, then a “headers” string, that can contain a lot of things.
      The method used by wp-ses as for now is simple_email.
      That is, no extra header is sent.

      That’s why bcc are not sent: they are within the header string, that is rewritten by amazon.

      I’d like to support extra headers, but this involves some work, I do not know if it will be available for the next release, sorry.

      No ETA for the moment.

      Cheers,

      Sylvain

      Reply

  16. Mike

    12 years ago

    Hi guys, please see my forum posting on the AWS forum here about the # of recipients:

    https://forums.aws.amazon.com/thread.jspa?threadID=75310&tstart=0

    Can you clarify if I’ll be able to use WP-SES to notify my blog readers about new posts?

    Reply

    • admin

      12 years ago

      @Mike,

      Just read the post and amazon answer about #of emails.
      This goes beyond the scope of this plugin.

      wp-ses does replace the default mailer by amazon ses service.
      How the mails will be sent (bcc or to:) depends of the plugin you use to manage the emails to your subscribers.
      I think they are usually sent one by one.

      If I read well, amazon says one email with 50 bcc counts as 1, where as 50 to: emails counts, well, as 50.
      So, if you need to send large amounts of emails, you have to request a larger quota to amazon.

      I’ll try to implement some skind of capping in a future version: should you go over your quota, the plugin will fall back to standard email delivery.

      Reply

  17. fabio

    12 years ago

    I have a problem.

    The Test email work fine, but the production mode test send me this error

    Warning: SimpleEmailService::sendEmail(): Sender – MessageRejected: Email address is not verified. Request Id: ce145689-d3dc-11e0-9146-27b4b0783b46 in /home/ricette/public_html/cloudlift.eu/wp-content/plugins/wp-ses/ses.class.php on line 362

    Reply

    • admin

      12 years ago

      Hi Fabio.

      “MessageRejected: Email address is not verified. ” : You have to follow the steps and verify your sending email address before using it in production mode.

      Reply

  18. Rodrigo

    12 years ago

    Hi. I installed the plugin in wp 3.2.1 and it seems not to be working. It gives this message: “WP SES – Simple Email Service is not fully activated. Please check it’s config: Settings → WP SES.”, but when I go there, the admin interface does not appear. Any suggestions?

    Reply

    • Rodrigo

      12 years ago

      Seems like the admin interface dispears when trying to add a verified email. Any suggestions?

      Reply

    • Rodrigo

      12 years ago

      Got it working. FTR, seems like curl was not installed and the plugin was not complaining either.

      Reply

  19. Brian

    12 years ago

    It looks like this has a conflict with TDO Mini Forms. It’s probably as you suggested before, both are looking to overwrite the wp-mail function.

    This plugin is currently more valuable than TDO Mini Forms, so you win the battle :-).

    Also there seems like the admin page is missing a close bold tag in the alerts that it isn’t set up properly. If you only have it partially set up everything on the page gets bolded (all your posts if you happen to be on the posts page), because the alert in the yellow box doesn’t have the close bold, font, or style tag.

    Email if you have any further questions for me.

    Reply

    • admin

      12 years ago

      Thanks Brian;

      Looks like it’s time to release a new version: got several easy fix to implement, as well as a list of incompatible plugins.
      I’ll also include a detection of rewritten wp-mail function, to avoid hunting for plugins that might rewrite wp-mail.

      Thanks !

      Sylvain

      Reply

  20. clackey

    11 years ago

    Having issues with Amazon SES and woocommerce. I can successfully get WP messages through but not woocommerce store confirmations, etc.. I’ve tried your plugin as well as others. I’ve also posted on the WOO forums but heard nothing so far. Any ideas?

    Reply

    • admin

      11 years ago

      Well,

      I suppose woocommerce does not use standard wp_mail function but a custom one, hence your troubles.
      Sorry, but I did’nt have this theme, so I can’t check.

      Reply

  21. clackey

    11 years ago

    Actually, they claim they are using the standard wp_mail function so it must be some special requirements around Amazon SES and HTML emails. I’ll try and dig into it further at some point.

    Reply

  22. deltafactory

    11 years ago

    WooCommerce’s default email includes a data uri as a background image in the body. It looks like that is the cause.

    https://forums.aws.amazon.com/thread.jspa?threadID=92579

    Reply

  23. Steve W

    11 years ago

    Do you plan to continue with the development of this plugin for current and future versions of WordPress?

    Reply

    • admin

      11 years ago

      Yes.

      No update for a while, but I’ll maintain it if needed.

      Reply

  24. Brian

    10 years ago

    Can you please provide some clarity on how queuing will work? For example let’s say that my max send rate is 5 messages per second, and I have a large subscriber base, and wordpress send more than 5 emails per second, what will happen to those emails?

    Will they be queue for the next second, or will they be discarded, and the message not delivered?

    Thanks,

    Brian

    Reply

    • admin

      10 years ago

      Hi Brian,

      It will be a real queue, not a trashcan. Sending rate will be limited, and messages will stay in queue, first in first out, to be sent later on.
      Of course, if you continuously send more messages than your sending rate allows, the queue will never stop growing and you’ll eventually run into problems.

      Reply

  25. tudoutou

    10 years ago

    I installed both wp-ses and contact form 7,when a contact information was submitted,I would get a mail notification.But now the sender email address changed to $wpses_options[‘from_email’] which is no-reply@domain.com.
    If I left the option blank,it works fine with normal sender name and email,but wp-ses would be de-actived after refresh.
    Could you tell me where is the setting of headers “From: name “

    Reply

    • admin

      10 years ago

      Hi tudoutou,

      There are some standing issues with contact form7, I’m digging into them.

      Howver, I’m not sure what you did and want to do.

      The “From” email has to be a valid and amazon verified email.
      What are you calling “normal sender name and email” ?
      What is the From email you want amazon to use ?
      Did you add this from: field into contact form 7 ?

      Sorry, I’m not sure I fully understand.

      Reply

  26. Nick

    10 years ago

    At what point will the plugin not require root AWS privileges and only ask for the AWS IAM SES user credentials?

    Reply

  27. gaurav

    10 years ago

    Hi,
    I am using this plugin.I have verified the emails and got keys for accessing.but than also plugin says that the email has not been confirmed yet.Keys are not valid
    Please help

    Reply

    • admin

      10 years ago

      Keys are not valid :

      1/ wp-ses need the curl php extension. Check your host does support it
      2/ typo within the API keys
      3/ Did you ask amazon to put your account into production mode ?
      4/ Check error-log

      Reply

  28. Bernard Golden

    10 years ago

    Awesome plugin. Thanks so much for creating it!

    Reply

  29. Philip Yuen

    10 years ago

    installed plugin and activated, it say ‘WP SES – Simple Email Service is not fully activated. Please check it’s config: Settings → WP SES.’ Now i can’t go back to the WP SES settings. Only a blank page is shown. Please help.

    Reply

    • admin

      10 years ago

      1/ wp-ses need the curl php extension. Check your host does support it
      2/ Check error-log

      Reply

  30. Christopher Morgan

    9 years ago

    I’m receiving an error saying:

    Amazon API Keys are not valid, or you did not finalize youy Amazon SES registration.
    Sender Email has not been confirmed yet.
    Plugin is not active.

    Does the plugin require the AWS SES credentials? I have those entered properly. Or is it wanting other credentials?

    Reply

    • admin

      9 years ago

      Try confirming the sender email first via the amazon ses console, then activate the plugin.

      Reply

  31. task

    9 years ago

    How best to address the issue. When using AWS to host multiple websites. Even if you use IAM to create a different user account for each clients mail, the plugin exposes all the e-mail accounts that are approved. So you could have a client at acme.com decide to send a bunch of spam out at xyz.com if they are on the same aws account. In either case would not want all clients to know how many other clients are in the same AWS account and this plugin exposes that data. It is a potential security issue.

    Reply

    • admin

      9 years ago

      Hi,

      I understand your concern.
      It looks like an Amazon SES problem, and not specifically an issue with the plugin.
      SES Approved senders are linked to the SES account, not the IAM user account;
      The API does return them all, the plugin shows them all and that makes sense.

      It would be possible to hide the approved senders that are not the main sender email, but
      1/ if using other senders with other plugins, they would not show up
      2/ it would be security by obscurity

      I can add a define in the config if that makes you feel safer.

      With your usage of amazon SES: one account for many clients and letting them change the sender, the only real solution I see can only come from amazon,
      and would be to link the approved sender emails to the user, not the account itself.

      As a matter of fact, whatever sender email is used to spam, it’s your main SES account that is at risk.

      Reply

  32. Seagyn

    9 years ago

    Hi,

    I’ve tried to use this plugin but ran into 2 issues.

    1. I could only get the mails to send via SES if I gave it an IAM user with full access. I had it set to allow all SES functions and it still didn’t work.
    2. Once I gave it root access, it sent for a while and then stopped working.

    Any ideas?

    Reply

  33. Seagyn

    9 years ago

    Oh and it also gives the following when I try to send test emails: SES Answer – id NULL

    Reply

    • admin

      9 years ago

      id Null means the SES api did not sent the email.
      This could be bad credential, too few rights, not in production …
      Depending of your php config, you may find the SES error code in your error_log file.
      The error is loggued with E_USER_WARNING

      I’ll add the error for test messages to the dashboard, this could prove helpfull.

      Also check this:
      http://docs.aws.amazon.com/ses/latest/DeveloperGuide/ses-errors.html
      and
      http://docs.aws.amazon.com/ses/latest/DeveloperGuide/api-error-codes.html

      Regarding AIM, many users successfully use IAM, I don’t know if it needs some special rights. It shouldn’t !

      Reply

      • Seagyn

        9 years ago

        Hi,

        I’m in production. I’ve given it credentials with FULL root access. I’ve used my personal access keys.

        Like I said in my previous comment, it worked. Then stopped. I’ve also added keys, saved it a few times and it says invalid keys. Then come back a few hours later and it’s fine.

        Are you using a IAM user with ONLY SES action capabilities?

        Thanks,
        Seagyn

        Reply

        • admin

          9 years ago

          Work then don’t work or vice versa looks like a connectivity (hosting?) or an Amazon problem.
          I’m not aware of another user experiencing the thing

          Reply

  34. Roy Johnson

    9 years ago

    Hello

    Is it possible to upload a list of 10,000+ email addresses, and send a bulk email newsletter to all these subscribers, using WP SES in conjunction with Amazon Web Services?

    Reply

    • admin

      9 years ago

      It’s very unlikely.

      This is not a wp-ses related question.
      WP-SES does the interface between wordpress plugins of functions, and the amazon SES service.

      So, if you got a plugin that imports many email and send newsletter to them (there are),
      if this plugin does not use their own sending method (there are many less)
      Then, theorically, you can send manymany emails.

      However, Amazon SES has
      – very little tolerance for spam and complaints
      – throttling and max sending rate : you will not be able, because of amazon SES rules, to send 10k emails in a snap.

      Reply

  35. Erno

    9 years ago

    Hi, all of my settings are correct because I can send a full production mode test via wp-admin.
    However my plugin state is:
    Sender Email is set
    Amazon API Keys are not valid, or you did not finalize youy Amazon SES registration.
    Sender Email has not been confirmed yet.
    Plugin is not active.

    And I can’t send any mail via my contact forms which use the wp_mail() function.
    Can you please advise some trouble shooting tips?

    Reply

    • admin

      9 years ago

      Sender email has to show as confirmed, or no mail will be sent.

      Check, via ses console, that your sender email is listed as confirmed sender for the same SES endpoint you use in the plugin.
      If not, ask for conformation and validate the mail.

      Then, sender will show as validated within the plugin, and plugin will be activable.

      Reply

  36. Tobias

    8 years ago

    Hi

    Thanks for a great plugin. Though I’m having issues with confirmation of the sender email. The AWS API Keys work, but even if the sender address is marked as confirmed in AWS SES the plugin doesn’t seem to pick it up. It says “Confirmed” NO no matter what I do.

    I have other confirmed addresses and they work in the plugin, but the newly added on doesn’t.

    Reply

    • Tobias

      8 years ago

      Ah, forgot to add my IAM user(for which API Keys I use) to the correct Security Group in AWS… works now!

      Reply

  37. Bolaji erigbemi

    8 years ago

    If im using Godaddy hosting, can AmazonSES still send thousands of email? because they appear to have blocked all SMTP services exept theirs

    Reply

    • admin

      8 years ago

      When using wp-ses, all emails goes trough Amazon SES, via their API (no smtp).
      So It works even if all smtp servers/ports are closed, ok then with Go daddy.

      Sending thousands of mails is another question: please keep in mind the limits of your amazon SES account, the quality of the mail you’re sending aso.

      Reply

  38. Daniel

    8 years ago

    It appears the plugin doesn’t check for verified domains. ie: If an address is part of a verified sending domain the plugin will still say that the sender hasn’t been verified.

    Reply

    • admin

      8 years ago

      @Daniel: Indeed !
      I’ll add to the checklist and see if the SES API makes that possible.

      Thanks !

      Reply

      • Daniel

        8 years ago

        Yup, it’s possible. And you can do it at the same same time as migrating away from deprecated methods.

        ListVerifiedEmailAddresses is deprecated
        ListIdentities will return both verified emails and domains

        VerifyEmailAddress is deprecated
        VerifyEmailIdentity will verify emails instead, and
        VerifyDomainIdentity will verify domains

        Reply

        • admin

          8 years ago

          Splendid !

          Reply

  39. BK

    8 years ago

    Is there a reason why the email addresses are case sensitive? we verified Email@domain.com but when I entered email@domain.com it came back as unverified.

    Reply

    • admin

      8 years ago

      @BK : No specific reason.
      I add this to the todo list, will be handled in the next version.

      Thanks,

      Sylvain

      Reply

    • Daniel

      8 years ago

      Technically speaking it’s actually possible for email@domain.com and Email@domain.com to be different usrs. The user portion is not defined as case insensitive and the standard leaves whether ‘Email’ and ’email’ are the same or not up to the mail software on the individual host.

      Reply

  40. Christian

    8 years ago

    It is possible to retrieve the security credentials from the instance metadata service for EC2 instead of specifying it in configuration?

    Reply

Leave a Reply