<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Why you should not use noreply@domain.com in your emails</title>
	<atom:link href="http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/</link>
	<description>We Make Email Delivery Easy</description>
	<lastBuildDate>Tue, 24 Jan 2012 23:23:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: timfalls</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-2897</link>
		<dc:creator>timfalls</dc:creator>
		<pubDate>Tue, 10 Jan 2012 20:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-2897</guid>
		<description>agreed! you have to give your customers/subscribers/etc *some* option to get in touch with you!  </description>
		<content:encoded><![CDATA[<p>agreed! you have to give your customers/subscribers/etc *some* option to get in touch with you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Regim</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-271</link>
		<dc:creator>Regim</dc:creator>
		<pubDate>Sat, 24 Jul 2010 09:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-271</guid>
		<description>What makes me crazy in these situations if they at least don&#8217;t mention an email address I can reply to and I have to figure that out by myself.</description>
		<content:encoded><![CDATA[<p>What makes me crazy in these situations if they at least don&rsquo;t mention an email address I can reply to and I have to figure that out by myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sendgrid</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-186</link>
		<dc:creator>sendgrid</dc:creator>
		<pubDate>Mon, 21 Jun 2010 20:08:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-186</guid>
		<description>Hi Gary, 
If you put the address in the Reply-to: field, we will pass that address in the &quot;to&quot; field.  In this case, the &quot;to&quot; POST field will be &quot;comment-8d7fe0883fab@mydomain.com &quot;. </description>
		<content:encoded><![CDATA[<p>Hi Gary,<br />
If you put the address in the Reply-to: field, we will pass that address in the &quot;to&quot; field.  In this case, the &quot;to&quot; POST field will be &quot;comment-8d7fe0883fab@mydomain.com &quot;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-182</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Tue, 25 May 2010 19:33:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-182</guid>
		<description>This looks really cool, but it is unclear to me how you would pass context information. Above you say: 
 
Companies can give unique email addresses to their users or use the same email address and include an unique identifier in the subject (such as ZenDesk) or in the body. 
 
What I&#039;d like to do if possible is to have the reply-to address be something like: 
 
comment-8d7fe0883fab@mydomain.com 
 
where the numeric &quot;8d7fe0883fab&quot; part is a unique identifier that specifies both (1) what &quot;conversation&quot; the user is replying to and (2) the user&#039;s specific email address; and, of course, have all of these emails invoke my site&#039;s web service. Now, I read your comment to say that you can include this unique identifier in the subject or body, but can you include it in the email address like this? And will the &quot;to&quot; field then have this complete email address? </description>
		<content:encoded><![CDATA[<p>This looks really cool, but it is unclear to me how you would pass context information. Above you say: </p>
<p>Companies can give unique email addresses to their users or use the same email address and include an unique identifier in the subject (such as ZenDesk) or in the body. </p>
<p>What I&#039;d like to do if possible is to have the reply-to address be something like: </p>
<p><a href="mailto:comment-8d7fe0883fab@mydomain.com">comment-8d7fe0883fab@mydomain.com</a> </p>
<p>where the numeric &quot;8d7fe0883fab&quot; part is a unique identifier that specifies both (1) what &quot;conversation&quot; the user is replying to and (2) the user&#039;s specific email address; and, of course, have all of these emails invoke my site&#039;s web service. Now, I read your comment to say that you can include this unique identifier in the subject or body, but can you include it in the email address like this? And will the &quot;to&quot; field then have this complete email address?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OverLinked &#187; People should be replying to your marketing emails</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-179</link>
		<dc:creator>OverLinked &#187; People should be replying to your marketing emails</dc:creator>
		<pubDate>Tue, 27 Apr 2010 14:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-179</guid>
		<description>[...] http://blog.sendgrid.com/28/why-you-should-not-use-noreplydomain-com-in-your-emails/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://blog.sendgrid.com/28/why-you-should-not-use-noreplydomain-com-in-your-emails/" rel="nofollow">http://blog.sendgrid.com/28/why-you-should-not-use-noreplydomain-com-in-your-emails/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sendgrid</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-147</link>
		<dc:creator>sendgrid</dc:creator>
		<pubDate>Sat, 06 Mar 2010 05:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-147</guid>
		<description>Yes, we retry for approximately 5 days.  The retry protocol works similarly to that of mail servers where the time between retries is incremented the more errors we get from your web server.  </description>
		<content:encoded><![CDATA[<p>Yes, we retry for approximately 5 days.  The retry protocol works similarly to that of mail servers where the time between retries is incremented the more errors we get from your web server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-145</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 05 Mar 2010 19:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-145</guid>
		<description>Will you retry on error, say if you receive an error 500? This is killer if we know that we are guaranteed not to lose email. </description>
		<content:encoded><![CDATA[<p>Will you retry on error, say if you receive an error 500? This is killer if we know that we are guaranteed not to lose email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sendgrid</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-106</link>
		<dc:creator>sendgrid</dc:creator>
		<pubDate>Mon, 22 Feb 2010 03:15:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-106</guid>
		<description>Yes you can use this if you are a Heroku customer.  You can take a look at a great example here: &lt;a href=&quot;http://nanceskitchen.com/2010/02/21/accept-incoming-emails-into-a-heroku-app-using-sendgrid/&quot; target=&quot;_blank&quot;&gt;&lt;a href=&quot;http://nanceskitchen.com/2010/02/21/accept-incomi...&lt;/a&gt;&quot; target=&quot;_blank&quot;&gt;http://nanceskitchen.com/2010/02/21/accept-incomi...&lt;/a&gt;&lt;/a&gt;  </description>
		<content:encoded><![CDATA[<p>Yes you can use this if you are a Heroku customer.  You can take a look at a great example here: <a href="http://nanceskitchen.com/2010/02/21/accept-incoming-emails-into-a-heroku-app-using-sendgrid/" target="_blank"></a><a href="http://nanceskitchen.com/2010/02/21/accept-incomi...</a>&#8221; target=&#8221;_blank&#8221;></a><a href="http://nanceskitchen.com/2010/02/21/accept-incomi..." rel="nofollow">http://nanceskitchen.com/2010/02/21/accept-incomi&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: liederf</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-100</link>
		<dc:creator>liederf</dc:creator>
		<pubDate>Sat, 20 Feb 2010 02:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-100</guid>
		<description>Will this be a part of any of the sendgrid add-on services for Heroku customers? </description>
		<content:encoded><![CDATA[<p>Will this be a part of any of the sendgrid add-on services for Heroku customers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan Fareed</title>
		<link>http://blog.sendgrid.com/why-you-should-not-use-noreplydomain-com-in-your-emails/comment-page-1/#comment-66</link>
		<dc:creator>Dylan Fareed</dc:creator>
		<pubDate>Thu, 11 Feb 2010 19:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sendgrid.com/?p=28#comment-66</guid>
		<description>This pretty much convinced me to start moving an app I am working on over to Send Grid immediately. If the execution is as good as I expect it to be, it makes SendGrid a no-brainer for most web apps. Awesome. </description>
		<content:encoded><![CDATA[<p>This pretty much convinced me to start moving an app I am working on over to Send Grid immediately. If the execution is as good as I expect it to be, it makes SendGrid a no-brainer for most web apps. Awesome.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

