Re: Help me to understand headers by N
N
Thu Nov 27 03:29:29 CST 2003
In article <zsaxb.13488$lm1.103474@wards.force9.net>,
postmaster@XnospamXpaulhsimon.plus.com says...
> I've received some SPAM, which had the following received lines in its
> headers (bottom two only shown);
It is as Ken says.
> Received: from c-24-9-246-141.client.comcast.net ([24.9.246.141])by
> BFLITEMAIL-KR4.bigfoot.com (LiteMail v3.03(BFLITEMAIL-KR4)) with SMTP id
> 24Nov2003_BFLITEMAIL-KR4_223300_73868345; Mon, 24 Nov 2003 20:59:36 -0500
> EST
>
> Received: from [16.30.46.104] by c-24-9-246-141.client.comcast.net with
> ESMTP id 36360197; Tue, 25 Nov 2003 11:53:43 -0300
>
> I'm trying to discover whether the first received header is false (in
> order to make me think that the IP address 16.30.46.104 was the original
> sender).
The first header is not false, but it is not a proper SMTP relay for
Comcast, either. It doesn't log the headers of incoming traffic in any
reliable way, so don't trust any subsequent Received: lines.
> How can I tell if it's false. What is the significance of an IP address
> which only appears in square brackets (like the first line) and one which
> is also within curved brackets (like the second ([24.9.246.141])). Is the
> first one false.
By figuring out if it is a proper MX server for the domain, "comcast.net".
If it isn't, then it likely can't be trusted. Do a Google on RFC 2821, and
you will learn more than you ever wanted to know about SMTP. But, normally,
the square brackets are optional, the parenthesis are required.
Incidentally, the "client.comast.net" name is an rDNS name, which pretty
much marks this as a residential customer. He probably has an unwanted
"guest", an open proxy which will accept connections, and pass them to
domain MX servers using SMTP. It is for this reason that AOL, among others,
rejects mail from such customers. This only affects a small percentage of
hobbyists, like me, who find our email blocked from their customers.
If you take a look at RFC 2821, you find anonymous is quite right; there is
a lot to learn about this SMTP stuff. Unless you are willing to buckle down
and learn something new, you are better off using MSOE's limited filtering,
finding a third party filter, and just hitting delete. It is not difficult,
but it takes time to sort it all out. Only you know if it will be worth your
time! ;)
--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint