Allow SMTP API to take an array of Reply-To addresses

Edit Subject

We would like to provide a unique Reply-To address for each email that gets sent out. Currently we do so by delivering each email to SendGrid individually.

We are considering using the SMTP API to send one templatized email to many recipients at once, but the Reply-To header also needs to be templatized on our end and substituted on SendGrid's end for this to work.

Would you consider adding functionality to allow multiple Reply-To addresses to be specified in a similar way as multiple To addresses? Even better, perhaps you could allow substitutions in the headers themselves, to solve this problem for all possible headers?

3 people like
this idea +1

Promoted Response

EMPLOYEE

3

Demote

Remove

David Williams (Employee) December 17, 2010 18:23

Building on this idea, is there any interest in us adding "trackable" reply-to addresses? We can make the parse api identify those addresses and can post the category/unique args/recipient from the original message. Stats for replies & unique replies would also be possible.

EMPLOYEE

1

Edit

Delete

Remove

Official

Tim Jenkins (CTO) December 17, 2010 15:00

Thats a really great idea. It may be a bit of a hit to do substitution in all possible headers, but certainly the reply-to wouldn't be a problem. I'll add this to an upcoming release.

We already do substitutions in the subject, are there any other headers you think substitutions would be useful in?

Regards,
Tim

good point! good point! (undo)
- view 1 more comment
- Joachim De Lombaert December 17, 2010 17:44
  
  That's fine; I think Reply-To is the only header where this would be useful to us.
  
  Edit
  
  Delete
  
  Remove
- Cancel
- richardawest July 20, 2011 03:16
  
  Is is possible to allow the From address to accept substitutions as well? Has this been implemented?
  
  Edit
  
  Delete
  
  Remove
- Cancel
- david.williams (Employee) July 20, 2011 15:28
  
  It hasn't been implemented yet, but while I'm working on the trackable reply-to addresses, I'll make from/reply-to substitutable.
  
  Edit
  
  Delete
  
  Remove
- Cancel
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this idea?

Thats a really great idea. It may be a bit of a hit to do substitution in all possible headers, but certainly the reply-to wouldn't be a problem. I'll add this to an upcoming release. We already do substitutions in the subject, are there any other headers you think substitutions would be useful in? Regards, Tim

How does this make you feel? Add Image

I'm
e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated
Cancel
This reply was removed on 2010-12-17.
see the change log
- Cancel
EMPLOYEE

3

Edit

Delete

Remove

Official

David Williams (Employee) December 17, 2010 18:23

Building on this idea, is there any interest in us adding "trackable" reply-to addresses? We can make the parse api identify those addresses and can post the category/unique args/recipient from the original message. Stats for replies & unique replies would also be possible.

good point! good point! (undo)
- view 2 more comments
- Joachim De Lombaert December 17, 2010 22:27
  
  Yes, that's an excellent idea: add "reply tracking" which would closely follow the existing "click tracking" feature. (Email passes through your servers, increments stats, triggers Parse API POSTs, and is passed along to the original From or Reply-To destination. I guess all those pieces would be optional.)
  
  Our specific use case is similar to Facebook's "Reply To Comment" feature, where certain emails include a unique Reply-To address which is used to post on the user's behalf. We need the following core features:
  - validation of the user who is replying (to avoid spoofed comments)
  - "thread ID" or similar parameter (preferably uneditable by the user)
  
  We could do this by providing our own Reply-To addresses, which would include IDs that map to those fields we need. (Facebook uses a 64-character local part, formatted like: c+22q...nk1i@reply.facebook.com )
  
  That said, the trackable reply-to addresses feature you're suggesting seems really useful. Assuming the reply-to address cannot be guessed, the inclusion of the original recipient and unique args as part of the Parse API would satisfy the above requirements. I would be most interested in the reply stats, though, because it's rather difficult to track that ourselves and would fit nicely into your existing stats dashboard. The Parse API support would just be a bonus.
  
  Edit
  
  Delete
  
  Remove
- Cancel
- Paulius Uza July 13, 2011 23:45
  
  David, are the trackable reply-to addresses implemented? We would love to use those in our app.
  
  Edit
  
  Delete
  
  Remove
- Cancel
- david.williams (Employee) July 15, 2011 16:30
  
  It hasn't happened yet, but we have a high level design that should work. It seems like a fun project, so the next time we have an internal hack day I'll get working on it.
  
  Edit
  
  Delete
  
  Remove
- Cancel
- Paulius Uza July 15, 2011 20:02
  
  Great! Please post a reply here when you do, we would be very happy about this! Thanks!
  
  Edit
  
  Delete
  
  Remove
- Cancel
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this idea?

Building on this idea, is there any interest in us adding "trackable" reply-to addresses? We can make the parse api identify those addresses and can post the category/unique args/recipient from the original message. Stats for replies & unique replies would also be possible.

How does this make you feel? Add Image

I'm
e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated
Cancel
I’m excited

0

Edit

Delete

Remove

Official

artvankilmer September 20, 2011 22:29

Add reply tracking, much like open and click tracking, based on the Parse API.

Employee David Williams described this in an earlier comment:
"Building on this idea, is there any interest in us adding "trackable" reply-to addresses? We can make the parse api identify those addresses and can post the category/unique args/recipient from the original message. Stats for replies & unique replies would also be possible."

This reply was created from a merged topic originally titled
Reply Tracking.

Comment

good point! good point! (undo)
- Cancel
Edit Your Reply (some HTML allowed)
What's the status of this idea?

Add reply tracking, much like open and click tracking, based on the Parse API. Employee David Williams <a href="http://community.sendgrid.com/sendgrid/topics/allow_smtp_api_to_take_an_array_of_reply_to_addresses#reply_4214501" rel="nofollow">described this in an earlier comment</a>: "Building on this idea, is there any interest in us adding "trackable" reply-to addresses? We can make the parse api identify those addresses and can post the category/unique args/recipient from the original message. Stats for replies & unique replies would also be possible." This reply was created from a merged topic originally titled <a href="/sendgrid/topics/reply_tracking/changes" target="_blank">Reply Tracking</a>.

How does this make you feel? Add Image

I'm
e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated
Cancel

Reply to This Topic (some HTML allowed)
What's the status of this idea?

How does this make you feel? Add Image

I'm
e.g. happy, confident, thankful, excited sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned

About this Idea

Official Representatives

Products & Services

Tagged

The mood in here

Allow SMTP API to take an array of Reply-To addresses

Edit Subject

About this Idea

Official Representatives

Products & Services

Tagged

The mood in here

Allow SMTP API to take an array of Reply-To addresses Edit Subject

Allow SMTP API to take an array of Reply-To addresses

Edit Subject