tag:help.tenderapp.com,2008-11-12:/discussions/problems/204-reply-to-email-address-is-secret-tender-address-instead-of-custom-fromTender: Discussion 2014-01-31T23:35:55Ztag:help.tenderapp.com,2008-11-12:Comment/336902009-01-13T22:08:30Z2009-06-20T20:16:15ZReply-to Email Address is Secret Tender Address Instead of Custom From<div><p>That's so replies get linked to the original discussion. I'm
trying to come up with a way to use a standard reply address and
embed the tender discussion ID discreetly. Ideally it'd go in the
footer somewhere, but that part is stripped out by our email
processor so that replies only have the actual body of the
message.</p>
<p>Edit: I'm also considering using a custom
<code>x-tender-id</code> mail header too. That sounds easiest, but
I want to do some testing to ensure that it doesn't get stripped
out of messages while being forwarded and passed around.</p>
<p>Edit: Aaaand I just got advised against the custom header. I can
surely send emails with the header, but your email client won't add
it to the response.</p></div>ricktag:help.tenderapp.com,2008-11-12:Comment/336902009-01-13T23:29:20Z2009-06-20T20:16:16ZReply-to Email Address is Secret Tender Address Instead of Custom From<div><p>How about using the "In-Reply-To" header field. This contains
the "Message-Id" of the email being replied to and can, therefore,
be used for threading.</p></div>jbrittentag:help.tenderapp.com,2008-11-12:Comment/336902009-01-14T09:12:51Z2009-06-20T20:16:23ZReply-to Email Address is Secret Tender Address Instead of Custom From<div><p>Yea I looked at that too. This is on the table, but we have some
more crucial features in the pipeline too.</p></div>rick