<?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: Images in E-Mail</title>
	<atom:link href="http://www.harmaninteractive.com/2005/11/02/images-in-e-mail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.harmaninteractive.com/2005/11/02/images-in-e-mail/</link>
	<description>Enhancing Revenue and Relationships through Integrated Marketing and Development</description>
	<lastBuildDate>Mon, 01 Feb 2010 19:26:05 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arka</title>
		<link>http://www.harmaninteractive.com/2005/11/02/images-in-e-mail/comment-page-1/#comment-8</link>
		<dc:creator>Arka</dc:creator>
		<pubDate>Fri, 24 Mar 2006 08:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.242.199/~harmanin/?p=86#comment-8</guid>
		<description>This is a common problem caused by privacy safeguards in modern email clients. Remember the dreaded Web Bug? All these images load from a web server somewhere, potentially allowing the sender to track when and if the email was opened. Spammers use this data to track if the email address is indeed &quot;live&quot;. One way to solve the dilemma is to send the message as a multipart-mixed email (content type multipart/mixed), with a HTML and a text part clearly labeled with the respective MIME types. This way, email clients with HTML mail disabled can show the text part of the message. Providing ALT information for images is very important as well -- they are often displayed even though the image may be blocked.</description>
		<content:encoded><![CDATA[<p>This is a common problem caused by privacy safeguards in modern email clients. Remember the dreaded Web Bug? All these images load from a web server somewhere, potentially allowing the sender to track when and if the email was opened. Spammers use this data to track if the email address is indeed &#8220;live&#8221;. One way to solve the dilemma is to send the message as a multipart-mixed email (content type multipart/mixed), with a HTML and a text part clearly labeled with the respective MIME types. This way, email clients with HTML mail disabled can show the text part of the message. Providing ALT information for images is very important as well &#8212; they are often displayed even though the image may be blocked.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

