Risk
6/28/2007
03:31 PM
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
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-1774
Published: 2015-04-28
The HWP filter in LibreOffice before 4.3.7 and 4.4.x before 4.4.2 and Apache OpenOffice before 4.1.2 allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted HWP document, which triggers an out-of-bounds write.

CVE-2015-1863
Published: 2015-04-28
Heap-based buffer overflow in wpa_supplicant 1.0 through 2.4 allows remote attackers to cause a denial of service (crash), read memory, or possibly execute arbitrary code via crafted SSID information in a management frame when creating or updating P2P entries.

CVE-2015-3340
Published: 2015-04-28
Xen 4.2.x through 4.5.x does not initialize certain fields, which allows certain remote service domains to obtain sensitive information from memory via a (1) XEN_DOMCTL_gettscinfo or (2) XEN_SYSCTL_getdomaininfolist request.

CVE-2014-6090
Published: 2015-04-27
Multiple cross-site request forgery (CSRF) vulnerabilities in the (1) DataMappingEditorCommands, (2) DatastoreEditorCommands, and (3) IEGEditorCommands servlets in IBM Curam Social Program Management (SPM) 5.2 SP6 before EP6, 6.0 SP2 before EP26, 6.0.3 before 6.0.3.0 iFix8, 6.0.4 before 6.0.4.5 iFix...

CVE-2014-6092
Published: 2015-04-27
IBM Curam Social Program Management (SPM) 5.2 before SP6 EP6, 6.0 SP2 before EP26, 6.0.4 before 6.0.4.6, and 6.0.5 before 6.0.5.6 requires failed-login handling for web-service accounts to have the same lockout policy as for standard user accounts, which makes it easier for remote attackers to cause...

Dark Reading Radio
Archived Dark Reading Radio
Join security and risk expert John Pironti and Dark Reading Editor-in-Chief Tim Wilson for a live online discussion of the sea-changing shift in security strategy and the many ways it is affecting IT and business.