Most websites have a contact form for visitors to fill out a message that is then e-mailed to the owner or support contact for the website.
When working with a Rails app that will be hosted in a cloud environment that does not supply outbound email delivery it can be convenient to use a Gmail (or Google Apps) account at first for outbound delivery.
The trouble is that Google’s SMTP server will rewrite the email address set in the email message to match the address of the account. You can add verified alias emails to your Gmail account, but obviously you cannot do that for all of your website visitors’ addresses.
Suppose your website’s account is email@example.com and you do something like the following in your application’s mailer:
When you get the message it will be from firstname.lastname@example.org and not from email@example.com. Worse, if you did not think to include a copy of the sender’s email in the body of the message you will have no record of who sent it. That’s just not good!
The easiest solution is to set the reply-to header like this:
Now the emails from your website will still be from [email protected], but when you hit reply in your e-mail client your message will be addressed to firstname.lastname@example.org. So you can reply without any extra work.
I hope this helps.
After posting this, I learned that you can also use the :reply_to symbol as documented in ActionMailer http://api.rubyonrails.org/classes/ActionMailer/Base.html#method-i-mail.
Lots of options :–)
I wanted to add, some might find the syntax for symbols in Ruby a little tricky. :reply-to will not work, but both
are exactly the same. For instance in Rails Console or IRB instance the following will return true: