<?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: Spammers Beware: We&#8217;re on Guard</title>
	<atom:link href="http://blog.softlayer.com/2007/spammers-beware-were-on-guard/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/</link>
	<description>A Behind the Scenes Look at the Best Hosting Provider in the World</description>
	<lastBuildDate>Fri, 24 May 2013 11:59:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-47469</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Wed, 17 Apr 2013 20:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-47469</guid>
		<description>Thanks for letting us know, Dan. If you can send an email to abuse@softlayer.com with &quot;malware&quot; and &quot;rootkit&quot; in the subject line and the details of what you&#039;re seeing, our team will investigate and take action to remove the violating content.</description>
		<content:encoded><![CDATA[<p>Thanks for letting us know, Dan. If you can send an email to <a href="mailto:abuse@softlayer.com">abuse@softlayer.com</a> with &#8220;malware&#8221; and &#8220;rootkit&#8221; in the subject line and the details of what you&#8217;re seeing, our team will investigate and take action to remove the violating content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-47466</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Wed, 17 Apr 2013 19:24:09 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-47466</guid>
		<description>This is NOT about a spam email.  However, it appears that your IP is infecting 
with a rootkit, as both Chrome and ie10 are constantly being blocked by MBAM for an outgoing
.exe.  So, not only do you have spammers, you have malware.</description>
		<content:encoded><![CDATA[<p>This is NOT about a spam email.  However, it appears that your IP is infecting<br />
with a rootkit, as both Chrome and ie10 are constantly being blocked by MBAM for an outgoing<br />
.exe.  So, not only do you have spammers, you have malware.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrews</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-46894</link>
		<dc:creator>andrews</dc:creator>
		<pubDate>Fri, 08 Mar 2013 18:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-46894</guid>
		<description>The problem with responding to spam reports is that most people reporting them are not going to be ticked to receive the reply: we got your report but the spammer is a good customer, and he blames his customer, so nothing will be done.

The alternative, an untruthful reply, might work for a while.  But eventually people are going to realize that the replies are not reflective of reality.  That would not be good, either.

All in all, I think their policy of ignoring reports is probably the best consistent with their business model of hosting spammers and blaming someone else.</description>
		<content:encoded><![CDATA[<p>The problem with responding to spam reports is that most people reporting them are not going to be ticked to receive the reply: we got your report but the spammer is a good customer, and he blames his customer, so nothing will be done.</p>
<p>The alternative, an untruthful reply, might work for a while.  But eventually people are going to realize that the replies are not reflective of reality.  That would not be good, either.</p>
<p>All in all, I think their policy of ignoring reports is probably the best consistent with their business model of hosting spammers and blaming someone else.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-46893</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Fri, 08 Mar 2013 17:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-46893</guid>
		<description>That&#039;s a great question, Ross. The crux of your point seems to rest on assumption that replying to each spam complaint would require marginal effort, but that&#039;s not true in this case.

Scenario: A user has a shared hosting plan through a hosting reseller. That hosting reseller rents the server housing that shared hosting plan from a SoftLayer customer who provides server management. The shared hosting user&#039;s account is compromised, and a spammer uses it to send one spam email message to 10,000 people. If 1% of those 10,000 people sends an abuse report to abuse@softlayer.com, the abuse queue grows by 100 emails for one issue.

When the abuse team gets those emails, they contact our customer about the abusive behavior. Our customer contacts their customer, and their customer contacts the user whose account was used to send the spam message. Action is taken to make sure the account is secured, so the user tells their hosting reseller who tells our customer who tells us that the problem has been resolved. In the span of time for all of that to happen, the abuse team has been notifying other customers about similar reports, and when a report isn&#039;t resolved in the window the abuse team provides, our representatives have to take action to disable the offending server (which in a hosting reseller&#039;s case could affect hundreds or thousands of innocent clients). 

To respond to each of the 100 abuse reports we received about the one message from one domain on our network, the abuse representative would need to find our customer&#039;s response, find all abuse reports related to that resolved issue and respond to each. The marginal time that it takes to do all of that adds up quickly at scale, and that activity would eat into the time our team could devote to processing new abuse complaints and following up with customer responses to abuse reports we&#039;ve filed on their account. 

In reality, the compromised account in this scenario would probably have sent more than one spam message before it was found and investigated, and each message would have its own abuse complaints, so the challenge snowballs.

I agree that it would be courteous to reply to each report when the issue is resolved, but doing so would affect the abuse team&#039;s ability to operate efficiently. I don&#039;t process hundreds of abuse reports about the same issue, so when one is forwarded to me, I&#039;m able to get an update internally that I can share in a reply. As a department, the abuse department has to set expectations based on the service they can provide consistently and efficiently, and the process of determining what those expectations can be is far from arbitrary.

Is that context helpful?</description>
		<content:encoded><![CDATA[<p>That&#8217;s a great question, Ross. The crux of your point seems to rest on assumption that replying to each spam complaint would require marginal effort, but that&#8217;s not true in this case.</p>
<p>Scenario: A user has a shared hosting plan through a hosting reseller. That hosting reseller rents the server housing that shared hosting plan from a SoftLayer customer who provides server management. The shared hosting user&#8217;s account is compromised, and a spammer uses it to send one spam email message to 10,000 people. If 1% of those 10,000 people sends an abuse report to <a href="mailto:abuse@softlayer.com">abuse@softlayer.com</a>, the abuse queue grows by 100 emails for one issue.</p>
<p>When the abuse team gets those emails, they contact our customer about the abusive behavior. Our customer contacts their customer, and their customer contacts the user whose account was used to send the spam message. Action is taken to make sure the account is secured, so the user tells their hosting reseller who tells our customer who tells us that the problem has been resolved. In the span of time for all of that to happen, the abuse team has been notifying other customers about similar reports, and when a report isn&#8217;t resolved in the window the abuse team provides, our representatives have to take action to disable the offending server (which in a hosting reseller&#8217;s case could affect hundreds or thousands of innocent clients). </p>
<p>To respond to each of the 100 abuse reports we received about the one message from one domain on our network, the abuse representative would need to find our customer&#8217;s response, find all abuse reports related to that resolved issue and respond to each. The marginal time that it takes to do all of that adds up quickly at scale, and that activity would eat into the time our team could devote to processing new abuse complaints and following up with customer responses to abuse reports we&#8217;ve filed on their account. </p>
<p>In reality, the compromised account in this scenario would probably have sent more than one spam message before it was found and investigated, and each message would have its own abuse complaints, so the challenge snowballs.</p>
<p>I agree that it would be courteous to reply to each report when the issue is resolved, but doing so would affect the abuse team&#8217;s ability to operate efficiently. I don&#8217;t process hundreds of abuse reports about the same issue, so when one is forwarded to me, I&#8217;m able to get an update internally that I can share in a reply. As a department, the abuse department has to set expectations based on the service they can provide consistently and efficiently, and the process of determining what those expectations can be is far from arbitrary.</p>
<p>Is that context helpful?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Golder</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-46884</link>
		<dc:creator>Ross Golder</dc:creator>
		<pubDate>Thu, 07 Mar 2013 23:57:53 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-46884</guid>
		<description>So what&#039;s the problem with responding directly to spam reports once resolved?

It doesn&#039;t take a second and it&#039;s a common courtesy to reply to someone who has reported an issue to you. Normal, civilised people would expect a reply. What makes you think we should reset *our* expectations?!

The attitude that the general public that should adapt their to SoftLayer rather than the other way around, plus the fact that I see more than just a handful of spamcop reports heading to SoftLayer, only perpetuates the impression that SoftLayer really don&#039;t give an abuse team at all and don&#039;t give a ***t about preventing spam.

If we send a report to your official abuse reporting address and don&#039;t get a response, why would we waste further time looking through forums trying to get another e-mail address to report it to? Sharing your personal address in a forum for such a purpose is admirable, but doesn&#039;t address the problem - that your company doesn&#039;t *appear* to be taking the original reports seriously.

I think it&#039;s SoftLayer&#039;s expectations that need to be &#039;reset&#039;!

--
Ross</description>
		<content:encoded><![CDATA[<p>So what&#8217;s the problem with responding directly to spam reports once resolved?</p>
<p>It doesn&#8217;t take a second and it&#8217;s a common courtesy to reply to someone who has reported an issue to you. Normal, civilised people would expect a reply. What makes you think we should reset *our* expectations?!</p>
<p>The attitude that the general public that should adapt their to SoftLayer rather than the other way around, plus the fact that I see more than just a handful of spamcop reports heading to SoftLayer, only perpetuates the impression that SoftLayer really don&#8217;t give an abuse team at all and don&#8217;t give a ***t about preventing spam.</p>
<p>If we send a report to your official abuse reporting address and don&#8217;t get a response, why would we waste further time looking through forums trying to get another e-mail address to report it to? Sharing your personal address in a forum for such a purpose is admirable, but doesn&#8217;t address the problem &#8211; that your company doesn&#8217;t *appear* to be taking the original reports seriously.</p>
<p>I think it&#8217;s SoftLayer&#8217;s expectations that need to be &#8216;reset&#8217;!</p>
<p>&#8211;<br />
Ross</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Hazard</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-46878</link>
		<dc:creator>Kevin Hazard</dc:creator>
		<pubDate>Thu, 07 Mar 2013 15:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-46878</guid>
		<description>In most cases, the SoftLayer abuse team does not *reply* to reports sent to abuse@softlayer.com or reports provided by SpamCop ... That does not mean that the abuse team does not *respond* to those reports, but if you&#039;re waiting to get a personal email response to a spam message you forwarded to our abuse team, it&#039;s important that your expectations be reset.

Understanding that one of our representatives will not be sending you an email reply, you should still see action taken on your complaint. I&#039;ve shared my email address ten times in this comment thread with the promise that I&#039;ll help in any way that I can, but it would appear that each new comment effectively disregards the previous comments that have been posted. Again, if you&#039;ve submitted abuse complaints to SpamCop or the SoftLayer abuse team directly and you haven&#039;t seen results, please forward the report you submitted to those authorities to khazard@softlayer.com.</description>
		<content:encoded><![CDATA[<p>In most cases, the SoftLayer abuse team does not *reply* to reports sent to <a href="mailto:abuse@softlayer.com">abuse@softlayer.com</a> or reports provided by SpamCop &#8230; That does not mean that the abuse team does not *respond* to those reports, but if you&#8217;re waiting to get a personal email response to a spam message you forwarded to our abuse team, it&#8217;s important that your expectations be reset.</p>
<p>Understanding that one of our representatives will not be sending you an email reply, you should still see action taken on your complaint. I&#8217;ve shared my email address ten times in this comment thread with the promise that I&#8217;ll help in any way that I can, but it would appear that each new comment effectively disregards the previous comments that have been posted. Again, if you&#8217;ve submitted abuse complaints to SpamCop or the SoftLayer abuse team directly and you haven&#8217;t seen results, please forward the report you submitted to those authorities to <a href="mailto:khazard@softlayer.com">khazard@softlayer.com</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrews</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-46864</link>
		<dc:creator>andrews</dc:creator>
		<pubDate>Thu, 07 Mar 2013 01:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-46864</guid>
		<description>No, they do not respond to spamcop reports.  I have submitted many, and to date no response has been had.  I will, however, point out that softlayer do continue to send out spam after they finish ignoring the reports.</description>
		<content:encoded><![CDATA[<p>No, they do not respond to spamcop reports.  I have submitted many, and to date no response has been had.  I will, however, point out that softlayer do continue to send out spam after they finish ignoring the reports.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Golder</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-44107</link>
		<dc:creator>Ross Golder</dc:creator>
		<pubDate>Sun, 28 Oct 2012 11:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-44107</guid>
		<description>Do you respond to SpamCop reports? I have been reporting spam from the domain &#039;cheekymailvouchers.co.uk&#039;, three times a day to my main address and to a mailing list I run, which they seem to have harvested from somewhere. It has been coming in for over a week now, on Saturdays and Sundays too. I&#039;ve had no response to any of my reports.</description>
		<content:encoded><![CDATA[<p>Do you respond to SpamCop reports? I have been reporting spam from the domain &#8216;cheekymailvouchers.co.uk&#8217;, three times a day to my main address and to a mailing list I run, which they seem to have harvested from somewhere. It has been coming in for over a week now, on Saturdays and Sundays too. I&#8217;ve had no response to any of my reports.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve1209</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-40341</link>
		<dc:creator>Steve1209</dc:creator>
		<pubDate>Tue, 19 Jun 2012 22:54:28 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-40341</guid>
		<description>David,

All my SPAM on Softlayer is a result of Tumblr.com spam Blogs, it makes me think SOMEHOW softlayer could BLOCK all of them but they don&#039;t seem to be able to!!!</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>All my SPAM on Softlayer is a result of Tumblr.com spam Blogs, it makes me think SOMEHOW softlayer could BLOCK all of them but they don&#8217;t seem to be able to!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.softlayer.com/2007/spammers-beware-were-on-guard/comment-page-1/#comment-40339</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 19 Jun 2012 20:03:19 +0000</pubDate>
		<guid isPermaLink="false">http://theinnerlayer.softlayer.com/2007/spammers-beware-were-on-guard/#comment-40339</guid>
		<description>Steve,

The mail I&#039;m getting is regular old email spam coming from Softlayer IPs, not related to Tumblr.

On the brighter side, it looks like posting here has gotten some attention, so perhaps the spam will finally stop.

David</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>The mail I&#8217;m getting is regular old email spam coming from Softlayer IPs, not related to Tumblr.</p>
<p>On the brighter side, it looks like posting here has gotten some attention, so perhaps the spam will finally stop.</p>
<p>David</p>
]]></content:encoded>
	</item>
</channel>
</rss>
