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

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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
This episode of Dark Reading Radio looks at infosec security from the big enterprise POV with interviews featuring Ron Plesco, Cyber Investigations, Intelligence & Analytics at KPMG; and Chris Inglis & Chris Bell of Securonix.