<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Comcast Blacklist Nightmare</title>
	<atom:link href="http://www.comcastblacklist.com/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://www.comcastblacklist.com</link>
	<description>Our Experience With the Infamous Comcast Blacklist</description>
	<lastBuildDate>Thu, 04 Jun 2009 17:21:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Comcast Blacklisting Resolved by a Tweet</title>
		<link>http://www.comcastblacklist.com/?p=17</link>
		<comments>http://www.comcastblacklist.com/?p=17#comments</comments>
		<pubDate>Thu, 04 Jun 2009 16:43:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Victim Stories]]></category>
		<category><![CDATA[central michigan university]]></category>
		<category><![CDATA[comcast blacklist]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.comcastblacklist.com/?p=17</guid>
		<description><![CDATA[Central Michigan University was blacklisted by Comcast when a student’s email account was compromised and used to distribute spam. Attempts via traditional methods to resolve the problem went unanswered. The school finally got Comcast’s attention with a post on the popular social networking site, Twitter.com:
On April 4, a Central Michigan University student&#8217;s e-mail account was [...]]]></description>
			<content:encoded><![CDATA[<p>Central Michigan University was blacklisted by Comcast when a student’s email account was compromised and used to distribute spam. Attempts via traditional methods to resolve the problem went unanswered. The school finally got Comcast’s attention with a post on the popular social networking site, Twitter.com:</p>
<blockquote><p>On April 4, a Central Michigan University student&#8217;s e-mail account was hacked into and after the spam was sent out, Comcast, a Michigan-based television and Internet provider, blocked all cmich.edu e-mail accounts.</p>
<p>The tweet that solved the problem was sent out by Information Technology Communications Manager Duane Kleinhardt on April 8 at 3:20 p.m. It stated &#8220;Cmich.edu e-mail is being blocked by Comcast. Call (989) 774-3662 for more info.&#8221;</p></blockquote>
<p>If this works for you or if you want a little help getting Comcast&#8217;s attention, be sure to comment on this article and  <a href="http://www.twitter.com/comcastblock" target="_blank">follow us on Twitter</a>&#8230; we&#8217;ll &#8220;re-tweet&#8221; for you!</p>
<p><a href="http://media.www.cm-life.com/media/storage/paper906/news/2009/04/17/News/It.Tweets.Its.Way.Off.Of.Spam.Blacklist-3715080.shtml">IT tweets its way off of spam blacklist &#8211; News</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.comcastblacklist.com/?feed=rss2&amp;p=17</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comcast Blocks Some Internet Traffic</title>
		<link>http://www.comcastblacklist.com/?p=10</link>
		<comments>http://www.comcastblacklist.com/?p=10#comments</comments>
		<pubDate>Fri, 19 Oct 2007 19:36:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[In the News]]></category>

		<guid isPermaLink="false">http://www.comcastblacklist.com/?p=10</guid>
		<description><![CDATA[Comcast Corp. actively interferes with attempts by some of its high- speed Internet subscribers to share files online, a move that runs counter to the tradition of treating all types of Net traffic equally.
The interference, which The Associated Press confirmed through nationwide tests, is the most drastic example yet of data discrimination by a U.S. [...]]]></description>
			<content:encoded><![CDATA[<p>Comcast Corp. actively interferes with attempts by some of its high- speed Internet subscribers to share files online, a move that runs counter to the tradition of treating all types of Net traffic equally.
<p>The interference, which The Associated Press confirmed through nationwide tests, is the most drastic example yet of data discrimination by a U.S. Internet service provider. It involves company computers masquerading as those of its users.
<p><a href="http://www.breitbart.com/article.php?id=D8SCEBLG0&amp;show_article=1">Comcast Blocks Some Internet Traffic</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.comcastblacklist.com/?feed=rss2&amp;p=10</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Georgia Tech victimized by Comcast</title>
		<link>http://www.comcastblacklist.com/?p=9</link>
		<comments>http://www.comcastblacklist.com/?p=9#comments</comments>
		<pubDate>Tue, 17 Jul 2007 01:58:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Victim Stories]]></category>

		<guid isPermaLink="false">http://www.comcastblacklist.com/?p=9</guid>
		<description><![CDATA[A Comcast customer and user of the mail servers of Georgia Institute of Technology in Atlanta reports that, as of 7/16/07, he is unable to receive email forwarded from GT to his Comcast mailbox.
]]></description>
			<content:encoded><![CDATA[<p>A Comcast customer and user of the mail servers of Georgia Institute of Technology in Atlanta reports that, as of 7/16/07, he is unable to receive email forwarded from GT to his Comcast mailbox.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.comcastblacklist.com/?feed=rss2&amp;p=9</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google Blacklisted by Comcast</title>
		<link>http://www.comcastblacklist.com/?p=8</link>
		<comments>http://www.comcastblacklist.com/?p=8#comments</comments>
		<pubDate>Fri, 13 Jul 2007 20:56:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Victim Stories]]></category>

		<guid isPermaLink="false">http://www.comcastblacklist.com/?p=8</guid>
		<description><![CDATA[As of 7/13/07, a number of mail servers for Google&#8217;s Gmail service are being blacklisted by Comcast. As difficult as it is to find a real person at Google, there is no way to estimate how long the blacklisting will last.
]]></description>
			<content:encoded><![CDATA[<p>As of 7/13/07, a number of mail servers for Google&#8217;s Gmail service are being blacklisted by Comcast. As difficult as it is to find a real person at Google, there is no way to estimate how long the blacklisting will last.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.comcastblacklist.com/?feed=rss2&amp;p=8</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>02/07: Caught In a Wide Net</title>
		<link>http://www.comcastblacklist.com/?p=1</link>
		<comments>http://www.comcastblacklist.com/?p=1#comments</comments>
		<pubDate>Tue, 06 Mar 2007 14:58:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Victim Stories]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[On February 26, 2007 at approximately 9:45 am, Comcast blacklisted the server of Shoestring Solutions, a small web host based in Atlanta, GA. The victim server is a dedicated server over which the victim had complete control. The following is a timeline of the victim&#8217;s actions to remove the block. (All times EST)
21:55 &#8211; confirmed [...]]]></description>
			<content:encoded><![CDATA[<p>On February 26, 2007 at approximately 9:45 am, Comcast blacklisted the server of Shoestring Solutions, a small web host based in Atlanta, GA. The victim server is a dedicated server over which the victim had complete control. The following is a timeline of the victim&#8217;s actions to remove the block. (All times EST)<span id="more-1"></span></p>
<p>21:55 &#8211; confirmed Comcast block. Submitted first of three requests to Comcast to be removed from blacklist via Comcast&#8217;s established procedures.</p>
<p>23:05, 00:07 &amp; 01:07 &#8211; received three denials of request to be removed from blacklist</p>
<p>23:55 &#8211; Enlisted help of server tech support to compile stats regarding spam originating from server</p>
<p><strong>2/27/07</strong></p>
<p>02:53 &#8211; server tech support reports that block occurred on 2/26 at approx. 09:45. Stats show that approx. 460 emails went from server to Comcast in 29-hour period prior to block (avg. 16/hour). Includes both legitimate and spam email, with none originating on server but simply being passed through email addresses of hosted domains.</p>
<p>03:54 &#8211; submitted email request to general tech support</p>
<p>04:00 &#8211; called Comcast support (404-266-2278). &#8220;John&#8221; said that he would pass support request to proper department after 6 am (dept. opens 7:30). Also provided Tier 2 support # &#8211; 877-561-9324</p>
<p>04:16 &#8211; received canned response; sent additional info (no response to date)</p>
<p>12:57 &#8211; Called Tier 2 support. Referred by barely understandable female with thick accent to blacklist_comcastnet@cable.comcast.com.</p>
<p>13:37 &#8211; sent blacklist removal request to blacklist_comcastnet@cable.comcast.com.<br />
15:31 &#8211; second second removal request</p>
<p>16:30 &#8211; called Tier 2 support. Told that response could take &#8220;24 to 78 hours.&#8221;</p>
<p>16:30 &#8211; sent third request to blacklist_comcastnet@cable.comcast.com</p>
<p><strong>2/28/07</strong></p>
<p>14:12 &#8211; sent fourth request by email</p>
<p>17:06 &#8211; confirmed continued block</p>
<p><strong>3/1/07</strong></p>
<p>11:45 &#8211; Called Tier 2 support again; spoke to &#8220;Andrew.&#8221; Transferred to Customer Security Assurance and Legal Response division, which is an endless voicemail loop with no way to file a blacklist removal request. Voicemail refers callers back to blacklist_comcastnet@cable.comcast.com.</p>
<p>11:50 &#8211; Called Tier 2 support again; spoke to &#8220;Orlando,&#8221; who refused to honor request to speak to supervisor. Sent us to same voicemail loop.</p>
<p>12:08 &#8211; Called Tier 2 support again. Female with thick accent provided direct # to abuse dept. (856-317-7272). Asked for supervisor; was placed on hold for 12 minutes. Told that supervisor was unavailable; placed on hold for five minutes. Final refusal to allow conversation with supervisor.</p>
<p>12:27 &#8211; sent fifth removal request by email</p>
<p>13:04 to 13:41 &#8211; sent email request for assistance to several Comcast corporate email addresses, public relations contacts; also to reporters who have written about blacklisting problem in past. Also posted details to Comcast support forums.</p>
<p>15:30 &#8211; interviewed by Chicago-area newspaper. Story expected</p>
<p>16:23 &#8211; call received from Shanti, local rep of Comcast corporate, who had been instructed to follow up as a result of one of our email complaints (probably to esl_corp@cable.comcast.com).  She provided her direct line  (770-559-7128) and committed to facilitating communication with support.</p>
<p>17:28 &#8211; received email inquiry from local media. Responded</p>
<p>17:36 &#8211; contacted by email from Customer Security Assurance (CSA, CSA_admin@cable.comcast.com). Contact initiated by Shanti; however, CSA would only provide phone number to CSA Voicemail Hell.<br />
17:38 &#8211; email from same source, asking for IP address</p>
<p>18:55 &#8211; phone call from Paul, CSA, who began investigation. Assigned ticket #2714541. Provided email for Symantec/BrightMail (investigation@review.symantec.com) although he said that a phone call to CSA Voicemail Hell would get a faster response (14 to 24 hours).</p>
<p>Paul said that our server was not blacklisted, but an entire range of IPs in which our server IP is located was blacklisted due to spam activity apparently associated with the domain GELINJANG.INFO. Because of range block, Paul was not authorized by Symantec to unlist our IP alone. He asked that we investigate the offending domain with our server host and contact CSA via Voicemail Hell (14 hour response&#8230; &#8220;things are slow right now&#8230;&#8221;).</p>
<p>19:11 &#8211; Paul called back, said that he expected to see Symantec tech in morning and would proactively address issue then.</p>
<p>20:28 &#8211; sent email update to Shoestring hosting clients</p>
<p><strong>3/2/07</strong></p>
<p>00:15 &#8211; received notification from server host that offending domain has been removed from IP range.</p>
<p>19:00 &#8211; Have not received any feedback from Paul. Left voice mail at 856-317-7272 with details regarding offending domain and another request for IP to be removed from blacklist.</p>
<p><strong>3/3/07</strong></p>
<p>18:05 &#8211; call from Yvonne, CSA, at 856-638-4000. She called to acknowledge voice mail; indicated that nothing would be done until Monday PM when Paul returns to work. Can call her at 856-638-4044 after 10:00 ET if no resolution by then.</p>
<p><strong>3/5/07</strong></p>
<p>08:45 &#8211; blacklist block still in place</p>
<p>11:25 &#8211; Left voicemail for Yvonne, number above, asking her to follow up, to make case her priority for the day.</p>
<p>15:41 &#8211; Received call from Paul, CSA. He said that mail was blocked due to high spam flow from GELINJANG.INFO, which was hosted in the same IP range as our server. He said that the &#8220;mail guys&#8221; would not even consider lifting block until the activity was stopped. Replied that a voice was left for him on 3/2/07 notifying him that the offending domain had been dumped by the host.</p>
<p>After a minute on hold, he returned to say that he would put in a request for the block to be lifted, but that it could take &#8220;at least a day&#8221; for it to be removed.</p>
<p>[Apparently, Paul did nothing between our conversation on 3/1 at 19:11 and this phone call. Another day was lost waiting for Paul, apparently an evening shift technician, to come back to work.</p>
<p>15:52 &#8211; left voice mail for Shanti, updating her on lack of progress</p>
<p>16:38 &#8211; Below email sent to csa_admin@cable.comcast.net and esl_corp@cable.comcast.net:</p>
<blockquote><p>To whom it may concern:</p>
<p>To date, Comcast has failed to resolve the blacklisting issue described in your CSA ticket #2714541 and documented by me online at www.shoestringwebs.com/comcast.htm.</p>
<p>My server continues to be blacklisted for sending email to Comcast servers; it has been blocked since 2/26 9:45 am even after it has been shown to Comcast representatives that the problem was not associated with my server nor any domain on it, but with another domain on a server in the same IP range; a domain that has been prevented from sending since at least 3/2/07 at 12:15 am.</p>
<p>In my latest contact with Comcast, a phone call from Paul in Customer Security Assurance, I learned not only that Comcast has failed to respond despite having the above information for three days, but that it may take &#8220;at least a day&#8221; for the block to be removed, if it is removed at all.</p>
<p>Because of Comcast&#8217;s lack of response and because I have little recourse otherwise, I will continue my efforts to publicize this situation so that my 900 clients who are also Comcast customers, as well as others will come to understand the depth of Comcast&#8217;s failure and act accordingly.</p></blockquote>
<p>17:01 &#8211; received following reply:</p>
<blockquote><p>This has been sent to our mail team for a removal of your IP from the blacklist.</p>
<p>Paul spoke with you earlier today about this request from you.</p>
<p>Please make note that the removal may take up to 24 hours and stated in your conversation with Paul.</p>
<p>Thank you,</p>
<p>CSA</p></blockquote>
<p><strong>3/6/07</strong></p>
<p>12 noon &#8211; confirmed by email that blacklisting still in place</p>
<p>18:52 &#8211; block confirmed lifted.</p>
<p><strong>3/7/07</strong></p>
<p>11:58 &#8211; received call from John, a local supervisor, to follow-up on issue. He said that blacklisting occurs &#8220;at the national level&#8221; and that local Comcast representatives have no more influence in blacklisting issues than do Comcast customers. At the &#8220;national level,&#8221; CSA technicians can do no more than submit an email or leave a voicemail for Symantec/Brightmail to resolve blacklisting issues.</p>
<p>John said that unresolved blacklisting issues are often escalated to him because the current public process is often ineffective. For that reason, he has collected direct contacts within the system to help resolve problems.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.comcastblacklist.com/?feed=rss2&amp;p=1</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
