Amazon has now removed the email address verification requirement of the Reply-To header. Sweet!
On Fri, Feb 4, 2011 at 12:53 PM, Dan Croak <dcr...@thoughtbot.com> wrote: > The only problem we've seen so far is not being able to use the Reply-To > header because THAT email address must be verified: > > https://forums.aws.amazon.com/thread.jspa?messageID=220892 > > That's the typical pattern where your app always sends email (never on > behalf of another user), but you set the "sending" user's email to the > "Reply-To" header so the receiver can just reply normally. > > We decided to remove the "Reply-To" feature for now. > > On Fri, Feb 4, 2011 at 12:51 PM, Dan Croak <dcr...@thoughtbot.com> wrote: > >> That doesn't appear to be true once you've moved out of their sandbox and >> into the production environment. I just tested this a few seconds ago, >> sending an email via Amazon SES from a Rails app to an email that has never >> received an SES email before. >> >> The user received only the email from my app, no opt-in email from Amazon. >> >> On Fri, Feb 4, 2011 at 12:21 PM, Miles Smith <mi...@vimae.com> wrote: >> >>> I've tried SES and it has an extremely crippling requirement: >>> >>> Every email must opt-in to recieve an email from SES. If you attempt to >>> authorize an email account, Amazon sends out a very non-descriptive, cryptic >>> (for normal users) message that states that "Amazon SES would like to send >>> email to you". It doesn't say anything about my app, nor did I find any way >>> of modifying the message that's sent. >>> >>> Still not ready to replace my current email solution with them for that. >>> :( >>> >>> On Fri, Feb 4, 2011 at 8:21 AM, Tim Fletcher <m...@tfletcher.com> wrote: >>> >>>> > 2) Any sign of a Ruby library? >>>> > Currently only .NET, Java and PHP wrappers. >>>> >>>> Yes, there's one here: >>>> https://github.com/drewblas/aws-ses >>>> >>>> This might help if you're using Rails 3: >>>> >>>> http://robots.thoughtbot.com/post/3105121049/delivering-email-with-amazon-ses-in-a-rails-3-app >>>> >>>> Cheers, >>>> Tim >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Heroku" group. >>>> To post to this group, send email to heroku@googlegroups.com. >>>> To unsubscribe from this group, send email to >>>> heroku+unsubscr...@googlegroups.com. >>>> For more options, visit this group at >>>> http://groups.google.com/group/heroku?hl=en. >>>> >>>> >>> >>> >>> -- >>> >>> >>> Miles Smith >>> *Owner/Lead Developer* >>> http://vimae.com/ >>> >>> This e-mail and any files transmitted with it are confidential and >>> intended solely for the use of the individual or individuals to whom the >>> e-mail is addressed. This e-mail and any files transmitted with it may >>> contain confidential, proprietary or legally privileged information. No >>> confidentiality or privilege is waived or lost by any mistransmission. If >>> you are not the intended recipient of this e-mail, please immediately notify >>> the sender and delete and/or destroy the e-mail (along with any files >>> transmitted with it) and all electronic or hard copies from your system. You >>> should not, directly or indirectly, use, disclose, distribute, print, or >>> copy any part of this message if you are not the intended recipient. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Heroku" group. >>> To post to this group, send email to heroku@googlegroups.com. >>> To unsubscribe from this group, send email to >>> heroku+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/heroku?hl=en. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
