"Gib Henry, Real People" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> I received 3 spams today, and all 3 had stale dates. The Received:
headers all showed that the e-mails originated today, but SpamCop said
(erroneously) that they were over 3 days old and therefore wouldn't process
them. Here's an example:
>
> Received: from mail.astralnetwork.com by realpeople.com (CommuniGate
> SMTP 3.1.4b) with ESMTP id S.3885357153nt for
> <[EMAIL PROTECTED]>; Fri, 27 Apr 2001 16:17:39 -0500
[snip]
> I think some clever spammers have figured out that back-dating their mail
is a good way around SpamCop. Could we ignore the claimed origin date/time
and use the most recent Received: date/time instead? Cheers,
spamcop does use the date from the first useful Received: line which it
finds...
the problem here is that your mailserver does not identify where it got the
email from... this can cause much more serious problems than an invalid
datestamp...
you should get your admin to fix the mail server so it stamps the IP address
of the sending server... currently spamcop is relying on the abused relay
server for the source address and the time... if the spammer was to connect
directly to your mail server to send the spam to you, then spamcop wouldn't
be able to track the source at all...
i'd go so far as to say you shouldn't use spamcop until the problem is
fixed - it would be quite possible for spamcop to end up looking at a
spammer's bogus header and sending reports to entirely the wrong place...
michael
spamcop user, not an admin
_______________________________________________
SpamCop-Help mailing list
[EMAIL PROTECTED]
http://news.spamcop.net/mailman/listinfo/spamcop-help
