TECHNOLOGY: AntiSPAM tactic that Yahoo misses

Here’s a spam that I received at my Yahoo account. It purports to be from a Yahoo user id. BUT, if it didn’t originate entirely inside Yahoo, then Yahoo should be able to NUKE it before it hits my inbox. Seems simple to me?

*** begin quote ***

Return-Path: <jfrank@yahoo.com>

Authentication-Results: mta134.mail.ac4.yahoo.com from=yahoo.com; domainkeys=neutral (no sig)

Received: from 80.229.33.223 (EHLO esssrv01.eatonsquareschool.com) (80.229.33.223) by mta134.mail.ac4.yahoo.com with SMTP; Thu, 20 Nov 2008 21:25:19 -0800

Received: from User ([216.212.164.154]) by esssrv01.eatonsquareschool.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 21 Nov 2008 05:17:48 +0000

Reply-To: <jfrank@yahoo.com>

From:

“Frank”<jfrank@yahoo.com>

Add sender to Contacts

Subject: Question about Item – Respond Now

Date: Thu, 20 Nov 2008 23:24:41 -0600

MIME-Version: 1.0

Content-Type: text/html; charset=”Windows-1251″

Content-Transfer-Encoding: 7bit

Bcc:

Return-Path: jfrank@yahoo.com

Message-ID: <ESSSRV01f9hYDkngMUJ000029cf@esssrv01.eatonsquareschool.com>

Content-Length: 10368

*** end quote ***

# # # # #

Please leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s