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-2014-2627
Published: 2014-08-01
Unspecified vulnerability in HP NonStop NetBatch G06.14 through G06.32.01, H06 through H06.28, and J06 through J06.17.01 allows remote authenticated users to gain privileges for NetBatch job execution via unknown vectors.

CVE-2014-3009
Published: 2014-08-01
The GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 through 11.0 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 does not properly handle FRAME elements, which makes it easier for remote authenticated users to conduct ph...

CVE-2014-3302
Published: 2014-08-01
user.php in Cisco WebEx Meetings Server 1.5(.1.131) and earlier does not properly implement the token timer for authenticated encryption, which allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCuj81708.

CVE-2012-6651
Published: 2014-07-31
Multiple directory traversal vulnerabilities in the Vitamin plugin before 1.1.0 for WordPress allow remote attackers to access arbitrary files via a .. (dot dot) in the path parameter to (1) add_headers.php or (2) minify.php.

CVE-2014-2970
Published: 2014-07-31
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2014-5139. Reason: This candidate is a duplicate of CVE-2014-5139, and has also been used to refer to an unrelated topic that is currently outside the scope of CVE. This unrelated topic is a LibreSSL code change adding functionality ...

Best of the Web
Dark Reading Radio