erlcloud_ses: add support for MessageRejected errors #210
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @motobob: once this is approved, I would like for us to pull it into alertlogic master. |
I missed this error code in my original implementation (mentioned [here](http://docs.aws.amazon.com/ses/latest/DeveloperGuide/ses-errors.html) in the AWS SES docs). I noticed it in a testing environment where SES wasn't configured. This makes erlcloud_ses return the error gracefully, instead of with an unceremonious `function_clause` error.
nalundgaard
force-pushed
the
add_ses_message_rejected
branch
from
3b2fe88
to
48cd7a6
Compare
ransomr
pushed a commit
that referenced
this pull request
Oct 1, 2015
erlcloud_ses: add support for MessageRejected errors
|
thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I missed this error code in my original implementation (mentioned here in the AWS SES docs). I noticed it in a testing environment where SES wasn't configured. This makes erlcloud_ses return the error gracefully, instead of with an unceremonious
function_clauseerror.