parsing error with SC

SC can't parse this email I got from gmail. This is all the headers I got.
The error that SC gives is:

Parsing header:
No source IP address found, cannot proceed.
Add/edit your mailhost configuration
Finding full email headers
Submitting spam via email (may work better)
Example: What spam headers should look like
Nothing to do.

-----------------------------------

Delivered-To: sgrayban@gmail.com
Received: by 10.48.230.10 with SMTP id c10cs52119nfh;
        Fri, 16 Feb 2007 07:36:19 -0800 (PST)
Received: by 10.114.73.1 with SMTP id v1mr1781456waa.1171640172104;
        Fri, 16 Feb 2007 07:36:12 -0800 (PST)
Received: by 10.114.171.4 with HTTP; Fri, 16 Feb 2007 07:36:11 -0800 (PST)
Message-ID: <97446e610702160736s4ab9f441v98d51cd0978c6e7@mail.gmail.com>
Date: Fri, 16 Feb 2007 07:36:11 -0800
From: "Kristy R." <kristykristy2006@gmail.com>
To: kristykristy2006@gmail.com
Subject: Hello!
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_4801_30630966.1171640171984"

------=_Part_4801_30630966.1171640171984
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hey, thanks for the email =) I am def interested....i recently just moved to
the area for my work reason.  For me, I see as a start/change for the new
year and I'm definitely want to make the best of it.  Just moved in about
two weeks now and I'm cleaning up my place and doing some laundry.  I wish I
can write more but I gotta fold these laundry.. but if you are interested in
getting to know me more I have a homepage at
www.uniquechick.com<http://www.kristycheeks.com/>where you'll find
more stuff about me.
I'll probably be on my computer after folding these clothes.  I hope to chat
with you shortly.



Best Regards,

Kristy

------=_Part_4801_30630966.1171640171984
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<p class="MsoNormal" style="MARGIN: 0in 0in
0pt"><span style="FONT-SIZE: 10pt;
FONT-FAMILY: Arial">Hey, thanks for the email =) I am def
interested....i
recently just moved to the area for my work reason.<span
style="mso-spacerun:
yes">
&nbsp; </span>For me, I see as a start/change for the new year and
I'm
definitely want to make the best of it.<span style="mso-spacerun:
yes">&nbsp;
</span>Just moved in about two weeks now and I'm cleaning up my place and
doing some laundry.
<span style="mso-spacerun: yes">&nbsp; </span>I wish I
can write more but I
gotta fold these laundry.. but if you are interested in getting to know me
more I have a homepage at <a
href="http://www.kristycheeks.com/">www.uniquechick.com
</a> where you'll find more stuff about me.<span
style="mso-spacerun:
yes">&nbsp; </span>I'll probably be on my computer after
folding these
clothes.<span style="mso-spacerun: yes">&nbsp;
</span>I hope to chat with you
shortly.</span>
</p>
<p class="MsoNormal" style="MARGIN: 0in 0in
0pt"><span style="FONT-SIZE: 10pt;
FONT-FAMILY: Arial">&nbsp;</span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in
0pt"><span style="FONT-SIZE: 10pt;
FONT-FAMILY: Arial">Best Regards,</span></p>
<p class="MsoNormal" style="MARGIN: 0in 0in
0pt"><span style="FONT-SIZE: 10pt;
FONT-FAMILY: Arial">Kristy</span></p>

Housekeeping:  I'm posting this to spamcop.spam and spamcop with f/ups
to spamcop

IMO the spamcop.spam group is only for posting such as what you posted
with the headers and body of a mail, but not for discussing it -- 
because no one reads in spamcop.spam because it only contains spam.
And, there are better ways to show each other spam as well, but that's
another story.

Scott Grayban wrote:
> SC can't parse this email I got from gmail. This is all the headers I
> got. The error that SC gives is:
>
> Parsing header:
> No source IP address found, cannot proceed.

The problem the parser is having with the gmail headers is that when a
gmail goes from one gmail client to another, there are no 'proper'
Received tracelines.  A proper Received traceline has a Received:
fieldname and then the field values contain a 'from' field and a 'by'
field.  The gmail lines are not tracelines because they only contain a
'by' field.

I didn't know about that problem, so I sent myself a mail from one of my
gmail accounts to another;  and sure enough, there are no proper
Received tracelines in my experiment, just like your example.

This is a tracking url of your spam that you posted in .spam

http://www.spamcop.net/sc?id=z1226930406z832d4e2ee60577d46c9268f318b923adz

That method of demonstrating a spam to other people has a number of
advantages over posting it into spamcop.spam, and the tracker can be
posted into a discussion group and the item discussed there.

You get a tracker by submitting the spam to the parser and then copying
the tracking url before reporting or cancelling.  In this case there is
no option to report or cancel.


-- 
Mike Easter
kibitzer, not SC admin

Housekeeping:  I'm posting this to spamcop.spam and spamcop with f/ups
to spamcop

IMO the spamcop.spam group is only for posting such as what you posted
with the headers and body of a mail, but not for discussing it -- 
because no one reads in spamcop.spam because it only contains spam.
And, there are better ways to show each other spam as well, but that's
another story.

Scott Grayban wrote:
> SC can't parse this email I got from gmail. This is all the headers I
> got. The error that SC gives is:
>
> Parsing header:
> No source IP address found, cannot proceed.

The problem the parser is having with the gmail headers is that when a
gmail goes from one gmail client to another, there are no 'proper'
Received tracelines.  A proper Received traceline has a Received:
fieldname and then the field values contain a 'from' field and a 'by'
field.  The gmail lines are not tracelines because they only contain a
'by' field.

I didn't know about that problem, so I sent myself a mail from one of my
gmail accounts to another;  and sure enough, there are no proper
Received tracelines in my experiment, just like your example.

This is a tracking url of your spam that you posted in .spam

http://www.spamcop.net/sc?id=z1226930406z832d4e2ee60577d46c9268f318b923adz

That method of demonstrating a spam to other people has a number of
advantages over posting it into spamcop.spam, and the tracker can be
posted into a discussion group and the item discussed there.

You get a tracker by submitting the spam to the parser and then copying
the tracking url before reporting or cancelling.  In this case there is
no option to report or cancel.


-- 
Mike Easter
kibitzer, not SC admin

Does anyone know how to report spam from one gmail account to another gmail
account then?

I think google did this so that they couldn't be labled as a spam source from
there account holders and preventing spam reporting sites to block them.

If they are breaking the headers internally to do that it also violates the
RFC as well which can be seen as an MX abuse which could get them listed
anyways.


Mike Easter wrote:
> Housekeeping:  I'm posting this to spamcop.spam and spamcop with f/ups
> to spamcop
> 
> IMO the spamcop.spam group is only for posting such as what you posted
> with the headers and body of a mail, but not for discussing it -- 
> because no one reads in spamcop.spam because it only contains spam.
> And, there are better ways to show each other spam as well, but that's
> another story.
> 
> Scott Grayban wrote:
>> SC can't parse this email I got from gmail. This is all the headers I
>> got. The error that SC gives is:
>>
>> Parsing header:
>> No source IP address found, cannot proceed.
> 
> The problem the parser is having with the gmail headers is that when a
> gmail goes from one gmail client to another, there are no 'proper'
> Received tracelines.  A proper Received traceline has a Received:
> fieldname and then the field values contain a 'from' field and a 'by'
> field.  The gmail lines are not tracelines because they only contain a
> 'by' field.
> 
> I didn't know about that problem, so I sent myself a mail from one of my
> gmail accounts to another;  and sure enough, there are no proper
> Received tracelines in my experiment, just like your example.
> 
> This is a tracking url of your spam that you posted in .spam
> 
> http://www.spamcop.net/sc?id=z1226930406z832d4e2ee60577d46c9268f318b923adz
> 
> That method of demonstrating a spam to other people has a number of
> advantages over posting it into spamcop.spam, and the tracker can be
> posted into a discussion group and the item discussed there.
> 
> You get a tracker by submitting the spam to the parser and then copying
> the tracking url before reporting or cancelling.  In this case there is
> no option to report or cancel.
> 

Scott Grayban wrote:
> Does anyone know how to report spam from one gmail account to another
> gmail account then?

You can't do it with spamcop, because you can't make any changes to the
spam.  Gmail is the source of the spam in your example.  You could do a
manual report to gmail.  Or just feed it to gmail's spam system.  I
don't know what they do with that.

> I think google did this so that they couldn't be labled as a spam
> source from there account holders and preventing spam reporting sites
> to block them.

Google/gmail also doesn't tell the IP source of a client using the gmail
webmailer to spam or send a mail.  If I access gmail from an EL
connection and send a hotmail or spamcop subscriber a spam using the
gmail webmailer, the only IP which is available is that of gmail, not
the EL IP of the customer using the webmail.

> If they are breaking the headers internally to do that it also
> violates the RFC as well which can be seen as an MX abuse which could
get them
> listed anyways.

I'm not so sure those headers are officially broken.

Maybe google considers gmail to gmail inside their own network.  If you
are inside some corporate networks and just send a company mail to
another company employee, the mail doesn't leave the company's network
and doesn't have the same kind of routing headers.


-- 
Mike Easter
kibitzer, not SC admin