1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
This was a rookie mistake. I had 2 regions set-up in Amazon SES. The one that was out of the sandbox (us-east-2) and one still in "sandbox" us-east-1. My Django code was using the wrong one. Changed the settings.py email settings to us-east-2:
EMAIL_BACKEND = 'django_ses.SESBackend'
EMAIL_HOST = 'email-smtp.us-east-2.amazonaws.com'
EMAIL_PORT = 587
EMAIL_USE_TLS = True
AWS_SES_REGION_ENDPOINT = "email.us-east-2.amazonaws.com"
AWS_SES_REGION_NAME = 'us-east-2'
DEFAULT_FROM_EMAIL = 'noreply@mysite.com'
con risposta 4 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 8 mesi fa
Congratulations! Your DKIM setup for the domain mysite.com is complete. You can now send DKIM-signed emails from any address within this domain through both Amazon SES.
For more information about DKIM, see the Amazon SES Developer Guide at http://docs.aws.amazon.com/ses/latest/DeveloperGuide/dkim.html . Please note that this email only relates to the US East (Ohio) region.