Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

handle SES From address verification and requesting production access from Amazon #9

Open
aculich opened this issue Oct 19, 2014 · 4 comments

Comments

@aculich
Copy link
Contributor

aculich commented Oct 19, 2014

To send email via AWS SES (Simple Email Service) requires verification:

You can only send email from verified email addresses and domains. If you have not requested production access to Amazon SES, you must also verify every recipient email address except for the recipients provided by the Amazon SES mailbox simulator. For more information, go to the Amazon SES Developer Guide.

The sendcreds.py script currently just prints out the formatted message to the console, but doesn't actually handle sending the email right now since this is another layer of feature to add.

For the moment, if you want to replace the ses.send_email() part with a standard local-SMTP method that you already use, then feel free to update the code since both @paciorek and @BagOfMostlyWater have commit access to this repository.

More info:

@aculich aculich assigned aculich and unassigned aculich Oct 19, 2014
@aculich
Copy link
Contributor Author

aculich commented Oct 19, 2014

For the purposes of your course the local-SMTP method is probably simplest and most expedient, however as a general solution SES seems worthwhile to implement at a later time. The other items remaining on the TODO list seem to be a higher priority in my mind, but let me know what you think.

@paciorek
Copy link
Contributor

Yes, sounds fine to me. Ryan, I'll probably just write a script that sends
the user password via email using mailx.

On Sun, Oct 19, 2014 at 9:36 AM, Aaron Culich [email protected]
wrote:

For the purposes of your course the local-SMTP method is probably simplest
and most expedient, however as a general solution SES seems worthwhile to
implement at a later time. The other items remaining on the TODO list seem
to be a higher priority in my mind, but let me know what you think.


Reply to this email directly or view it on GitHub
#9 (comment)
.

@BagOfMostlyWater
Copy link

That'd work, though if you want it to be part of provision.py you can use
smtplib to send mail through scf.berkeley.edu. Both methods are pretty
simple.

Ryan, from my phone
On Oct 19, 2014 9:40 AM, "Christopher Paciorek" [email protected]
wrote:

Yes, sounds fine to me. Ryan, I'll probably just write a script that sends
the user password via email using mailx.

On Sun, Oct 19, 2014 at 9:36 AM, Aaron Culich [email protected]
wrote:

For the purposes of your course the local-SMTP method is probably
simplest
and most expedient, however as a general solution SES seems worthwhile
to
implement at a later time. The other items remaining on the TODO list
seem
to be a higher priority in my mind, but let me know what you think.


Reply to this email directly or view it on GitHub
<
https://github.com/ucberkeley/brc-experiments/issues/9#issuecomment-59655508>

.


Reply to this email directly or view it on GitHub
#9 (comment)
.

@aculich
Copy link
Contributor Author

aculich commented Oct 19, 2014

The email sending is decoupled from provisioning.py as a separate script sendcreds.py which is what you'd want to update to get the template functionality to use with smtlib/scf.b.e.

aculich added a commit that referenced this issue Oct 20, 2014
- [ ] send email via local-SMTP (assigned to @cpaciorek) instead of SES for now - [Issue #9](#9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants