Risk
6/28/2007
03:31 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Opening Up A Can Of Spam, I Mean Worms

When I wrote my story yesterday about a self-proclaimed anti-spam activist's feud with a company he accused of being a "spammer", I knew I was touching on a sensitive issue, but I didn't realize just how sensitive until today. Both sides took exception to the wording of passages in my story, particularly those that used the "s" word, and I'm sure that neither side will be looking to shake hands and laugh abou

When I wrote my story yesterday about a self-proclaimed anti-spam activist's feud with a company he accused of being a "spammer", I knew I was touching on a sensitive issue, but I didn't realize just how sensitive until today. Both sides took exception to the wording of passages in my story, particularly those that used the "s" word, and I'm sure that neither side will be looking to shake hands and laugh about this anytime soon.You don't need me to tell you that spam is a very big problem for IT departments and their users. Spam hogs bandwidth, transmits malware, and eats away at productivity. But it's arguably just as big a problem for a company to be accused of sending spam. As Oklahoma ISP Mark Mumma found, calling a company a "spammer" is a serious accusation with serious consequences. Mumma initially threatened to identify Omega Word Travel, a provider of online booking tools and flight tracking information, as a "spammer" on his various anti-spam Web sites, but instead, the courts say he defamed Omega, and he's now been ordered to pay that company $330,000 in damages.

There's a lot of he said/he said going back and forth between Mumma and Omega's legal team. Omega pointed out to me that they've spent a lot of money to successfully defend themselves against being labeled a "spammer" (something the courts agree that they're not). Mumma, meanwhile, isn't convinced, calling the header in Omega's marketing e-mails deceptive and claiming he never signed up to receive their e-mails.

The issues of unsolicited e-mails (or "spam"), e-mail lists, e-mail headers, compensation, defamation, and reputation all play a role in this case. Both sides agree that Omega is a legitimate business. Their primary disagreement is on the difference between marketing and spamming. The court has decided in this case -- in favor of Omega. But the line between the two can be vague.

I'm most curious at this point to know how much of a problem you perceive spam to be. How do you define spam, and is the problem growing? Be sure to weigh in with your thoughts.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web