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

replyto causes error #6

Open
alexvpickering opened this issue Jan 20, 2018 · 2 comments
Open

replyto causes error #6

alexvpickering opened this issue Jan 20, 2018 · 2 comments
Labels

Comments

@alexvpickering
Copy link

alexvpickering commented Jan 20, 2018

The following works:

send_email("Test Email Body", subject = "Test Email", 
             from = "[email protected]", to = "[email protected]")

Adding replyto fails

send_email("Test Email Body", subject = "Test Email", 
             from = "[email protected]", to = "[email protected]", replyto="[email protected]")

With this warning:

Warning messages:
1: In sesPOST(body = query, ...) : Bad Request (HTTP 400).
2: In structure(r[["SendEmailResponse"]][["SendEmailResult"]][["MessageId"]],  :
  Calling 'structure(NULL, *)' is deprecated, as NULL cannot have attributes.
  Consider 'structure(list(), *)' instead.
packageVersion('aws.ses')
[1] ‘0.1.4’
@leeper leeper added the bug label Apr 17, 2018
@TomWeishaar
Copy link
Member

TomWeishaar commented Nov 1, 2018

Try it with an AWS-verified address as the replyto address. Amazon-SES replyto addresses have to be AWS-verified, just like from addresses. Amazon's customers have been complaining about this since 2011. Here's page 2 of the thread, which has the most recent requests to fix this.

@TomWeishaar
Copy link
Member

My previous comment was based on my experience with SMTP. When using the api, on the other hand, it appears replyto addresses do not need to be AWS-verified after all. However, there was a bug in the replyto code which is fixed in a pull request I'm about to make.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants