<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/kasi77/marks/tag/email">
<title>Public marks from user kasi77 with tag email</title>
<description>Public marks from user kasi77 with tag email</description>
<link>http://blogmarks.net/user/kasi77/marks/tag/email</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058261427"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058060930"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1057880156"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1898014"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/135966"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058261427">
<title>10 historical software bugs with extreme consequences | Royal Pingdom</title>
<link>http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/</link>
<description>One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</description>
<dc:date>2009-04-05T19:11:18Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>software, load, email, gmail, it, bug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/05/ce0e604ac851c7e71feaf1730e58a26c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://royal.pingdom.com/2009/03/19/10-historical-software-bugs-with-extreme-consequences/">10 historical software bugs with extreme consequences | Royal Pingdom</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">One of the latest software errors that had widely noticed consequences was Google’s Gmail outage in February. The problem in that case was, according to Google, a bug in the software that distributed load between its different data centers.

The Gmail outage only resulted in people not having access to their email for a few hours. No one got killed. Nothing exploded. It was an inconvenience, and while it was a significant inconvenience for some of Gmail’s users, it was still just that: an inconvenience.

This article is about some of the more dire consequences of software errors through the years. Incidents that make the Gmail outage seem rather trivial.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gmail">gmail</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/it">it</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058261427">Copy</a> | 
<a href="http://blogmarks.net/link/3144363">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058060930">
<title>Royal Pingdom » One single web host was behind 75% of all email spam</title>
<link>http://royal.pingdom.com/2008/11/13/one-single-web-host-was-behind-75-of-all-email-spam/</link>
<description></description>
<dc:date>2008-11-16T16:13:25Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>web, email, spam</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://royal.pingdom.com/2008/11/13/one-single-web-host-was-behind-75-of-all-email-spam/"><img border="0" src="http://blogmarks.net/screenshots/2008/11/16/8573712619e08ee9760a21d178ab007c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://royal.pingdom.com/2008/11/13/one-single-web-host-was-behind-75-of-all-email-spam/">Royal Pingdom » One single web host was behind 75% of all email spam</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spam">spam</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058060930">Copy</a> | 
<a href="http://blogmarks.net/link/2969520">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1057880156">
<title>A Guide to CSS Support in Email</title>
<link>http://www.campaignmonitor.com/css/</link>
<description>Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.

We've put together this CSS support in email clients guide to save you the time and trouble of figuring it out for yourself. With 21 different sets of results, all the major email systems are covered, both desktop applications and webmail.</description>
<dc:date>2008-06-15T07:29:44Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>css, html, emailing, email</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.campaignmonitor.com/css/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/03/a2da7e9c1beafb25249af5f2d6586eed.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.campaignmonitor.com/css/">A Guide to CSS Support in Email</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2808024">13 other(s)</a> 
<p class="description">Designing an HTML email that renders consistently across the major email clients can be very time consuming. Support for even simple CSS varies considerably between clients, and even different versions of the same client.

We've put together this CSS support in email clients guide to save you the time and trouble of figuring it out for yourself. With 21 different sets of results, all the major email systems are covered, both desktop applications and webmail.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/emailing">emailing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057880156">Copy</a> | 
<a href="http://blogmarks.net/link/2808024">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1898014">
<title>POMPAGE - Emails HTML - Dompter la bête</title>
<link>http://www.pompage.net/pompe/emails-html-dompter-la-bete/</link>
<description>Si vous êtes malchanceux et que le PDG utilise Lotus Notes mais veut que le design de l'email s'affiche partout de la même manière, tableaux et styles en ligne vous attendent. </description>
<dc:date>2007-01-31T06:46:06Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>E-mailing, groupe:clever-age, mailing, email, css, html, design, newsletter</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.pompage.net/pompe/emails-html-dompter-la-bete/"><img border="0" src="http://blogmarks.net/screenshots/2009/02/18/52ff81bd39b6408ec4787e439dd8af04.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.pompage.net/pompe/emails-html-dompter-la-bete/">POMPAGE - Emails HTML - Dompter la bête</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1619330">28 other(s)</a> 
<p class="description">Si vous êtes malchanceux et que le PDG utilise Lotus Notes mais veut que le design de l'email s'affiche partout de la même manière, tableaux et styles en ligne vous attendent. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/E-mailing">E-mailing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/groupe%253Aclever-age">groupe:clever-age</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mailing">mailing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/newsletter">newsletter</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1898014">Copy</a> | 
<a href="http://blogmarks.net/link/1619330">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/135966">
<title>YouSendIt | Email large files quickly, securely, and easily!</title>
<link>https://www.yousendit.com/</link>
<description>send large file 'via' email</description>
<dc:date>2005-08-16T14:13:51Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>email, file, large, 1 gb</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://www.yousendit.com/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/08/16/0a3e402441e38cb7f2d55b751baa5676.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://www.yousendit.com/">YouSendIt | Email large files quickly, securely, and easily!</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/197810">4 other(s)</a> 
<p class="description">send large file 'via' email</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/email">email</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/file">file</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/large">large</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/1%2Bgb">1 gb</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=135966">Copy</a> | 
<a href="http://blogmarks.net/link/197810">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>