Get answers quicker by searching

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Unable to get SES quota from Amazon
  • Vote Up0Vote Down mpmumaumpmumau
    Posts: 1Sendy user

    I have installed Sendy on a server that I operate. While the installation process seems to have worked, I continue to get "Unable to get your SES quota from Amazon" as an error message in Sendy.

    I have reviewed other posts regarding this issue, and so far I have done the following:

    Verified that my server's time is synced to NTP. The following is my output from ntpq -p

     +mx-a.smith.is   198.55.111.5     3 u   69  128  377   80.885   -0.278   2.463
     -triangle.kansas 128.252.19.1     2 u    5  128  365   73.386   -3.568   3.965
     *name1.glorb.com 64.113.32.5      2 u  116  128  377   39.633   -1.671   0.892
     +pool-test.ntp.o 127.67.113.92    2 u   67  128  367   81.395    2.537   1.316
    

    I believe that that data confirms that I am less than a few seconds out of sync from various NTP servers; often it is even less than a second out of sync.

    • Ensured that my IAM credential has the AmazonSESFullAccess policy.
    • Double checked my credentials, and also created new IAM credentials to ensure that it wasn't a freak issue with the first account.

    What other things do I need to check in order to get the SES quota?

  • 2 Comments
  • Vote Up0Vote Down BenBen
    Posts: 3,505Sendy support

    Hi,

    Sync your server clock with NTP using the following SSH command for Linux:

    sudo /usr/sbin/ntpdate 0.north-america.pool.ntp.org 1.north-america.pool.ntp.org 2.north-america.pool.ntp.org 3.north-america.pool.ntp.org

    Best regards,
    Ben

  • Vote Up0Vote Down mpmumaumpmumau
    Posts: 1Sendy user

    Yeah I figured it out eventually. Just for posterity's sake, I was mistakenly trying to use my SES SMTP credentials rather than the IAM credentials. Once I plugged in the correct credentials, everything was ok.

This discussion has been closed.
All Discussions