[SpamCop-List] Re: Forged header causing spamcop not to report

[Scott]

But it was only picked up by hotmail yesterday.  That would mean that 
regardless of where the message originated, hotmail was abused yesterday to 
send this message out, right?

Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; 
Wed, 19 Oct 2005 21:12:45 -0700

Speaking of hotmail, any word on when they plan to patch their system?  I've 
been getting tons of spam originating from their servers lately.

--
Scott


"Geoffrey Hyde" <g.hyde at bigpond.net.au> wrote in message 
news:dj80vv$snk$1 at news.spamcop.net...
> Essentially, it's because the spammers keep changing addresses.  An 
> address that is 3 days or older is already out-of-date, because the 
> spammer has ditched that one and moved onto another one, therefore 
> avoiding lost time securing a host to send spam from.
>
> If it's not a ditched address, SpamCop doesn't usually allow reporting of 
> it mainly because the routing information may have changed by then.  It's 
> a feature, not a bug.
>
> Please don't trust that x.y.z will always be at IP address 1.2.3.4 it may 
> change to w.y.z or any other similar name change, but might still 
> originate from IP address 1.2.3.4 or the host at 1.2.3.4 may have closed 
> that down to the spammer who simply moves onto a different IP range of 
> 2.2.3.4 for example, or any other not yet blacklisted address.
>
> Please note that this message has terms that have been oversimplified a 
> little, the real practice of acquiring, using, and discarding domain names 
> is a lot more complex.
>
> -- 
> Cheers ...
>
> Geoffrey Hyde
>
>
>
> "Scott" <sedellNOSPAM at misonix.com> wrote in message 
> news:dj80ca$s8m$1 at news.spamcop.net...
>>I tried to report this mail.  It appears to have a forged Received header 
>>with an older date.  Spamcop won't allow the message to be reported 
>>because it's too old.
>>
>> http://www.spamcop.net/sc?id=z817763553z45a42559e41589533bc126b3485d51eaz
>>
>> Bug in the system?
>> Scott
>>
>
>