Module Description
This module is used to send mails via Amazon SES. instead of usind Drupal's native mail system.
Advantages of this module
- You need not setup your own SMTP server.
- lesser configuration, just setup your AWS credentials and you are all set.
- This module sends email via Amazon SES by directly calling API.
How to install it
- Just like other module , donwload it via drush or FTP, and enable it.
Dependencies
Configuration
Follow these steps:
- Provide your AWS Security Credentials "admin/config/media/awssdk", it is must, so that this module can
send api request to your AWS account. For more details about AWS Credentials
read through http://docs.aws.amazon.com/general/latest/gr/aws-security-credentials.html.
Get your access key here https://portal.aws.amazon.com/gp/aws/securityCredentials. - Amazon SES requires that you verify your email address or domain, to confirm that you own it and to prevent others from using it. so you must verify your sender id. For this go
to "admin/config/aws-settings/aws-verify-ses-sender-id". If you don't have Production
Access to Amazon SES, you must verify recipient's mail addresses.
Project page
https://www.drupal.org/project/amazon_ses
Clone command
git clone --branch 7.x-1.x http://git.drupal.org/project/amazon_ses.git
Manual reviews of other projects
- https://www.drupal.org/node/2312403#comment-9012067
- https://www.drupal.org/node/2315539#comment-9034791
- https://www.drupal.org/node/2278193#comment-9055883
- https://www.drupal.org/node/2312955#comment-9056347
- https://www.drupal.org/node/2423361#comment-9656085
- https://www.drupal.org/node/2438453#comment-9663445
- https://www.drupal.org/node/2427623
Similar Modules
- SMTP module: sends mails via SMTP to Amazon SES
Upcoming Features
- Meaningful feedback, i.e. who has read mail, who spammed it, who have not received yet.
- Integration with https://drupal.org/project/simplenews module.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | aws_statistics.png | 38.59 KB | tkuldeep17 |
| #3 | aws_dkim.png | 63.48 KB | tkuldeep17 |
| #3 | aws_verify.png | 26.58 KB | tkuldeep17 |
| #3 | aws_access_key.png | 57.23 KB | tkuldeep17 |
Comments
Comment #1
tkuldeep17 commentedComment #2
mandar.harkare commentedDoing review on
Automated Review
(*)Please clear the code sniffer issues found by pareview.sh.
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
Comment #3
tkuldeep17 commentedAdd similar module region and update module description.
Comment #4
tkuldeep17 commented@mandar.harkare Thanks for reviewing my first module. I have fixed issued raised by you. But still I am seeing error pareview.sh. and not able to resolve it. So please help me here.
Comment #5
tkuldeep17 commentedComment #6
mandar.harkare commentedKuldeep,
Every time you commit your code, visit the above link, click on Repeat Review and click on Submit Branch button (make sure URL to your git repository is mentioned there).
Comment #7
PA robot commentedWe are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #8
tkuldeep17 commentedComment #9
tkuldeep17 commentedComment #10
tkuldeep17 commentedComment #11
mpdonadioAssigning to myself for next review.
Comment #12
mpdonadioIf that fails for whatever reason please get back to us and set this back to "needs review".
Comment #13
PA robot commentedClosing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #14
tkuldeep17 commentedComment #15
tkuldeep17 commentedUpdated module description.
Comment #16
tkuldeep17 commentedComment #17
klausiLooks like you you have not addressed the duplication question - people can just use https://www.drupal.org/project/smtp and set Amazon as SMTP server? Looks like your project page is not accurate?
Comment #18
tkuldeep17 commentedHi klausi,
Thanks for reviewing. I have updated module description once again, please see "Similar Module" and "Advantage of this Module" section. above, hope it will fix duplication problem.
Comment #19
klausiThe project page is wrong - you don't need to setup your own SMTP server, you can just set Amazon as your SMTP server. So you just have to set the credentials with the smtp module and you are all set, correct?
Comment #20
tkuldeep17 commentedHi klausi,
No, If you uses this module, you don't need to bother about smtp server not even Amazon as smtp server. Amazon SES sends mail in two ways:
so my module is using second method. You just need to enter AWS credentials which are required for using any Amazon service.
Comment #21
tkuldeep17 commentedComment #22
klausiYes, so it seems we already have a module which is working just fine with Amazon SES: the smtp module. Is there any benefit in using your module?
Comment #23
tkuldeep17 commentedhi klausi:
Thanks for replying..
If anyone sends mail by Amazon SES via SMTP interface, there are more configuration which has to done.
1. Client software that can communicate using Transport Layer Security (TLS). and so more. For detail please refer here.
And these configuration has to be done in Amazon UI interface.
Benefits of this module over smtp:
1. But in my module there is very less configuration, just need AWS credentials
2. It sends the mail by calling direct Amazon SES API.
3. Provides interface for verifying identities, list identities, DKIM settings and sending mail statistics.
PS: Above settings can be configured by Amazon UI. But I am providing simple drupal interface for it.
Future Scope:
1. After this release I am planing to show Feedback on mail i.e. who has read mail, who spammed it, who have not received yet.
2. Will show mail statistics in better graphics way.
3. Integrate with simple newsletter module.
Comment #24
tkuldeep17 commentedComment #25
klausiReview of the 7.x-1.x branch (commit 63cf8d0):
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #26
tkuldeep17 commented@klausi: Thanks a lot.
I will update my code as per your guidelines. And update this issue ASAP.. :-)
Comment #27
Ryan Palmer commented@tkuldeep17 has requested maintainer access to the amazon_ses module, which I discontinued development on due to there being better support for SMTP email sending (this is probably still the case, IMO). Using Amazon SES via SMTP does not require "your own SMTP server", but this point might be lost in translation. If he can resolve the issues outstanding with his submission, I'll be happy to grant it.
Comment #28
tkuldeep17 commentedAdding tag "PAReview: review bonus" again and updated issue with my more three module reviews.
Comment #29
tkuldeep17 commented@klausi: According to your feedback, I have updated my code. Module name is also rename with namesapce amazon_ses.
Test case has to be written yet. I will write ASAP.
@ryan: My module does not send mail via Amazon SES SMTP interface. Thats why module module does not require SMTP configuration. It sends mail by directly calling SES API.
Comment #30
klausiReview of the 7.x-1.x branch (commit d2791c2):
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. You have to get a review bonus to get a review from me.
manual review:
Otherwise I think this is close to ready.
@Ryan Palmer: can you grant tkuldeep17 access in the meantime so that he can push the code to the amazon_ses project?
Comment #31
tkuldeep17 commentedComment #32
tkuldeep17 commentedHi klausi:
Thank you so much for reviewing module so closely. :-)
I have updated code according to your feedback.
Comment #33
klausiCool, please move the code now into the amazon_ses repository.
Comment #34
naveenvalechacan we transfer ownership of Ryan's module to @tkuldeep17 #2432593: Offering to maintain Amazon SES. We have added him as co-maintainer to move this process along.
Comment #35
naveenvalechaComment #36
klausiCode is in the amazon_ses repository, so let's continue here.
Comment #37
tkuldeep17 commented@naveenvalecha @klausi: So much thanks for your guidance and quick response.
Now I have moved code to amazon_ses repo. So my sandbox module https://www.drupal.org/sandbox/tkuldeep/2311697 is now useless. So should I delete it. Please assist me what to do next.?
Comment #38
klausiYes, you should delete the old sandbox now to avoid confusion.
Comment #39
klausiGit errors:
But otherwise looks good to me now!
Assigning to naveenvalecha as he might have time to take a final look at this.
Comment #40
naveenvalechaRead efbd3ad...
directly pass the default value instead of passing through array because we don't have multiples enabled in select list.
No Blocker..
Thanks for your contribution, tkuldeep17!
I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #41
tkuldeep17 commentedThanks @klausi @naveenvalecha @ryan @mandar.harkare helping me..
@klausi @naveenvalecha: I will follow your feedback and suggestions. :-)