So much for "Message ID really can't be faked"

Ergh.

So much for the "Message ID can't be faked" theory that often promotes 
better structure in Spam filters.

I can't say I've seen it before but tonight I got one:

Message-ID: <[email protected]>


<sigh> Here are the headers for interest.  I changed "mydomain" for obvious 
reasons.  But harvesters aren't as intelligent as humans :)  Right ;)

If anyone has a TMDA rule to catch the below, I suspect it might be very 
useful this year.  I can see this is JUST the beginning of this kind of 
fraud header, having not personally seen (or noticed) it before.


Return-Path: <[email protected]>
Received: from llsb600-a02.servidoresdns.net (llsb600-a02.servidoresdns.net 
[82.223.190.40])
	by fep1.ah.net (8.12.11/8.12.11) with ESMTP id l0FBkCUj006050
	for <adam@mydomain>; Mon, 15 Jan 2007 22:46:13 +1100
Received: from 179.Red-81-45-246.staticIP.rima-tde.net 
(179.Red-81-45-246.staticIP.rima-tde.net [81.45.246.179])
	by smtp-02.servidoresdns.net (Postfix) with SMTP id 4FF6D3EB74
	for <adam@mydomain>; Mon, 15 Jan 2007 12:46:06 +0100 (CET)
X-Original-To: adam@mydomain
Delivered-To: adam@mydomain
Received: from [81.45.246.179] (port=46566 
helo=179.Red-81-45-246.staticIP.rima-tde.net)
         by fep1.ah.net with esmtp
         id 756032-756032-08
         for adam@mydomain; Mon, 15 Jan 2007 12:42:50 +0100 (EET)
Message-ID: <[email protected]>
From: "Marcie" <[email protected]>
To: "Dillon" <adam@mydomain>
Subject: cellular
Date: Mon, 15 Jan 2007 12:42:50 +0100 (EET)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_4EBD_01C7389A.48E191D0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180