Jump to content

Gmail to gmail: No source IP address found, cannot proceed


A.J.Mechelynck

Recommended Posts

spam from gmail to gmail cannot be reported: "No source IP address found, cannot proceed".

See example at http://www.spamcop.net/sc?id=z5238498027z4...e91c744df9d4c8z

Link to comment
Share on other sites

  • 7 months later...

I am getting this message when I try reporting a spam. It always is from the same person:

No source IP address found, cannot proceed.

Can anyone suggest what the problem might be?

Here is the header from my email client:

doctor g <cococo26[at]gmail.com>

To: doctor g <cococo26[at]gmail.com>

Bcc: A D <REMOVED...>

Delivered-To: d1a2m3i4e5n6[at]gmail.com

Received: by 10.76.10.227 with SMTP id l3csp46281oab; Wed, 26 Sep 2012 19:01:34 -0700 (PDT)

Received: from mr.google.com ([10.58.86.36]) by 10.58.86.36 with SMTP id m4mr1881885vez.14.1348711293760 (num_hops = 1); Wed, 26 Sep 2012 19:01:33 -0700 (PDT)

Received: by 10.58.86.36 with SMTP id m4mr1463878vez.14.1348711293555; Wed, 26 Sep 2012 19:01:33 -0700 (PDT)

Received: by 10.58.32.225 with HTTP; Wed, 26 Sep 2012 19:01:33 -0700 (PDT)

Return-Path: <cococo26[at]gmail.com>

Received-Spf: pass (google.com: domain of cococo26[at]gmail.com designates 10.58.86.36 as permitted sender) client-ip=10.58.86.36

Authentication-Results: mr.google.com; spf=pass (google.com: domain of cococo26[at]gmail.com designates 10.58.86.36 as permitted sender) smtp.mail=cococo26[at]gmail.com; dkim=pass header.i=cococo26[at]gmail.com

Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=cOQNeLPLh2uBUxwYXRe9z2TbP1a9m1HTS6SZAC9yRjU=; b=OucGoaOaBj56LHp+c/tdKJ1SvZZaX9LzZw8cvaEE3m9owtwZatHyVVcf9foK9eeWM4 Kd6eXdaKT+9qhjt5m03it9RHl4izf5YfXOXfk0Pqm3erQ0GBh7FuUqOW4W34AzMn2S/8 gsn2LXv/8XdefLV7pUUJCljoWD7dnO+mgR9pBTOgBlBb4BiCXwqL64I++BDKYIuYuKOM lX/2sL9OjyyWsj3/fyIXdC+WslUxjit5skPmxz5UsKUAnDshngCMPQCXzi9BXt8LD61D teMWdlzTbKlybxR9CtEdrpWu1mhvDTt5Zq4SeQjOLt5ZcW92Vq+TcThs75MC7BTtIloi Szlw==

Mime-Version: 1.0

In-Reply-To: <75599D17009E47EBAB5F7B40757FFD59[at]inspiron>

References: <75599D17009E47EBAB5F7B40757FFD59[at]inspiron>

Message-Id: <CA+ak6d822bx_bnhF00V0wf+uXiObDC_KqKvhQjrAURLYn0NE2Q[at]mail.gmail.com>

Content-Type: multipart/related; boundary=047d7b6d8d9e8e956b04caa551fd

Fwd: Fw: How to get to Mars

Link to comment
Share on other sites

It's probably because it's going from Gmail to Gmail, and so it using their internal server IPs, all starting with "10.etc." -- those aren't going to parse.

But, looking at what you're trying to report, it would seem just some sort of annoying messages from an annoying sender, perhaps, as opposed to the kind of "spam" that most of us would be reporting (pharma, phishing, etc.). Perhaps you could simply filter this person in your Gmail and be done with it? Or forward their messages directly to Google's abuse department?

DT

Link to comment
Share on other sites

Thanks David for taking the time to let me know the reason.

Annoying sender, yes! I dislike any spam! I will look into reporting such spam directly to gmail.

Cheers!

It's probably because it's going from Gmail to Gmail, and so it using their internal server IPs, all starting with "10.etc." -- those aren't going to parse.

But, looking at what you're trying to report, it would seem just some sort of annoying messages from an annoying sender, perhaps, as opposed to the kind of "spam" that most of us would be reporting (pharma, phishing, etc.). Perhaps you could simply filter this person in your Gmail and be done with it? Or forward their messages directly to Google's abuse department?

DT

Link to comment
Share on other sites

You're welcome. To me, not all unwanted email rises to the level of "spam," but as they say, YMMV. For example, there are several SpamCop reporters who appear to have agreed to receive email from various political entities (perhaps only implicitly, by supplying an email address on a petition and not reading the fine print), and then instead of unsubscribing, they report it as spam. I'm seeing a number of those email campaigns winding up in my "Held" folder, and when the sending IPs are on the SCBL, I sometimes take a look to see if it's due to report, spamtrap hits, or both.

This week, I've seen a server (from a source I have subscribed to) being listed on the SCBL for the last 46 hours due to a handful of reports from what appears to be only two reporters. I would prefer *not* to have the deliverability of messages from that organization reduced due to the apparently laziness of two SpamCop reporters, who should have simply unsubscribed. I think they're guilty of false reporting, and so I'm working with the company in question, providing information about this issue. My point is--lets all be careful NOT to report stuff that is NOT REALLY spam!

DT

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...