|Google refusing spam reports?||D.Dancer||8/14/13 8:41 AM|
I'm having issues with spammers using gmail accounts and google refusing to accept spam reports, is there another means to inform google about spammers?
|Re: Google refusing spam reports?||bkc56||8/14/13 1:36 PM|
What do you mean "refusing"? All you do is click the "report spam" button. I'm not aware that there's anything to refuse.
|Re: Google refusing spam reports?||D.Dancer||8/14/13 2:53 PM|
Just so we can be on the same page.
My business email account gets spam from someone using a gmail email service.
My business does not "report spam" to google.
My business uses spamcop to report spam.
Spamcop reports that google is bouncing spam reports.
I use the following page:
And enter all the requested information about the abuser as requested by the page.
I press submit.
Page says: "Sorry, this is not a gmail message."
Mail's header that informs us where the message came from:
Considering that it it extremely impossible to forge a lookup from ARIN, again I ask:
|Re: Google refusing spam reports?||bkc56||8/14/13 3:28 PM|
My first thought is the headers are forged (common for spammers) and that's why the form doesn't not recognize it as a Gmail message, because it isn't. But I can't see the full headers so that's mostly a guess.
|Re: Google refusing spam reports?||D.Dancer||8/15/13 8:30 AM|
I've been reporting spam for many years, and from looking at so much freaking raw message sources, no, this is legit message from google:
Sample of message headers that google says "not our problem":
Note: All @ symbols have been padded with leading and trailing spaces to prevent another spam filter from triggering on this message board.
Note: 188.8.131.52 is the user's IP address and not the email server that sent this message, spamcop will report message to user's ISP and not to email server hosting service. You need to have your mailhost configuration set up properly for spamcop to report to email server.
Note: Message headers for tracking are stacked onto of prior headers as the message travels through servers, most recent server IP is on top. My mail server is reporting 184.108.40.206 as the last server the message came from.
Return-path: <rfranco3200 @ bcsdny.org>
(envelope-from <rfranco3200 @ bcsdny.org>)
for user @ business; Wed, 14 Aug 2013 10:12:24 +0000
Received: from ExchMB01.bcsdny.org ([220.127.116.11]) by na3sys009aob117.postini.com ([18.104.22.168]) with SMTP
ID DSNKUgtYBl0kuQZxjc3piksabHC6zfp/nX9v @ postini.com; Wed, 14 Aug 2013 03:12:23 PDT
Received: from ExchMB01.bcsdny.org ([fe80::60c3:3547:48da:8336]) by
ExchMB01.bcsdny.org ([fe80::60c3:3547:48da:8336%39]) with mapi; Wed, 14 Aug
2013 06:12:21 -0400
From: "Franco, Rozana" <rfranco3200 @ bcsdny.org>
To: "Franco, Rozana" <rfranco3200 @ bcsdny.org>
Date: Wed, 14 Aug 2013 06:12:20 -0400
Message-ID: <2529CED9B8E17D4EBD23259A7A432F2312E2A31184 @ ExchMB01.bcsdny.org>
References: <2529CED9B8E17D4EBD23259A7A432F2312E2A30E49 @ ExchMB01.bcsdny.org>
In-Reply-To: <2529CED9B8E17D4EBD23259A7A432F2312E2A30E49 @ ExchMB01.bcsdny.org>
empty body if desired to see what spamcop says.
|Re: Google refusing spam reports?||bkc56||8/15/13 8:53 AM|
Perhaps the submission form is only checking the TO/FROM info (which doesn't reference @gmail.com in the above example)?
I'm just not sure (obviously).
|Re: Google refusing spam reports?||D.Dancer||8/15/13 2:47 PM|
Which is my biggest gripe about this, as is, with them refusing to accept reports from spamcop, they are siding with the spammers. And they do not provide any means for us peons to notify them that we find their actions objectionable.
I seriously doubt anyone from google is bothering to read this message board, and most annoying is that this is the second or third time I've posted about this, the other posts were deleted for some unknown reason.
|Re: Google refusing spam reports?||bkc56||8/15/13 3:14 PM|
I've pointed Google at this thread. I have no idea if they will comment or not.
|Re: Google refusing spam reports?||Ersher||8/15/13 4:50 PM|
Thank you bkc56 for alerting me to this thread. It looks like the email address in question may be a Google Apps email account. If you want to report spam from an Apps account I would follow the process mentioned here: http://support.google.com/a/bin/answer.py?hl=en&answer=178266
|Re: Google refusing spam reports?||D.Dancer||8/15/13 6:14 PM|
I really do appreciate the time taken to point out that page and associated pages, however, it's not the solution.
Furthermore, if google is bouncing email sent by spamcop to it's own abuse email address for it's native properties, indicating that the address is unmonitored and therefore nobody cares, what indication do I have that any other abuse email address is monitored?
|Re: Google refusing spam reports?||bkennelly||8/15/13 9:34 PM|
The sender is, apparently, using an Exchange server, not Google, to send mail, so it is neither Gmail nor Google Apps, but the messages are being sent through Postini, which is a Google property. I will assume that the sender is using Postini as an outbound gateway, so it should be possible to report the abuse there.
|Re: Google refusing spam reports?||D.Dancer||8/16/13 10:28 PM|
Problem with using the abuse address's you quoted:
Finding IP block owner:
So, abuse is bouncing emails, now what?
|Re: Google refusing spam reports?||bkennelly||8/21/13 8:00 PM|
The real solution is for Spamcop to update their algorithms to recognise the Postini servers and report spam to the sender's domain.
|Re: Google refusing spam reports?||D.Dancer||8/25/13 10:18 PM|
Doesn't address the issue that google is bouncing abuse email's.
Google has become a spammer's haven because of that.
Doesn't matter what property or IP range, if it belongs to google, that is, the abuse lookup says "abuse[at]google.com", it's going to bounce.
Also, you do NOT report spam to the service that is being hosted, that's the spammer, never report spam to a spammer. You report spam to the hosting service.
|Re: Google refusing spam reports?||Barbara Payne||9/4/13 2:24 AM|
Hi, Anyone having problems from ivanba...@gmail.com ???? We at ddawebdesign.com are sick to death with him!!! or the robot!!
Why can Google not get this email removed??? This robot is spamming our customer forms constantly! We receive between 20 and 40 emails a day just from this one robot!
Can anyone help????
|Re: Google refusing spam reports?||bkennelly||9/5/13 8:40 AM|
On Sunday, August 25, 2013 10:18:54 PM UTC-7, D.Dancer wrote:
In this case, the hosting service is Cablevision Internet (IP 22.214.171.124). Google are not hosting, they are relaying. To report problems with the relay, you need to report it to the correct abuse address, <postini-a...@google.com>.
This message did not originate from Google or from a Google hosted email account. It originated from an Exchange server for the bcsdny.org domain, hosted by Cablevision.
|Re: Google refusing spam reports?||D.Dancer||9/9/13 1:44 PM|
That's the second tier of the headers, the message may have originated there, but that's not who you report to. You report spam to the mail server administrators that delivered the message. If you bothered to read the rest of the parse, you see:
1: Received: from ExchMB01.bcsdny.org ([126.96.36.199]) by na3sys009aob117.postini.com ([188.8.131.52]) with SMTP ID DSNKUgtYBl0kuQZxjc3piksabHC6zfp/nX...@postini.com; Wed, 14 Aug 2013 03:12:23 PDT
Meaning that the host for the mail server has been found, it has been determined that 184.108.40.206 is a mail server, and that 220.127.116.11 cannot be resolved to a unique hostname, therefore spamcop will report the spam to the owner of the mail server, which happens to be google.
I've been in the spam reporting and fighting business for way too long.
|Re: Google refusing spam reports?||bkennelly||9/9/13 2:07 PM|
On Monday, September 9, 2013 1:44:34 PM UTC-7, D.Dancer wrote:That's the second tier of the headers, the message may have originated there, but that's not who you report to. You report spam to the mail server administrators that delivered the message.
In general, yes, but you must use the correct reporting address. Have you tried it yet? <postini-a...@google.com>
But, when you have additional information, as in this case, you can modify your reporting procedures. Postini is a well known mail processing service that is acting as a relay, and the originating IP can be trusted. In addition to reporting it to the Postni abuse address, you should report it to the hosting service where the message originates.
|Re: Google refusing spam reports?||D.Dancer||9/16/13 8:50 AM|
SpamCop v 4.8.0.059 © 2013 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
Skip to Reports
Delivery-date: Mon, 16 Sep 2013 06:50:49 +0000
Received: from mail-la0-f41.google.com ([18.104.22.168]:47131)
by rs3.abstractdns.com with esmtps (TLSv1:RC4-SHA:128)
for x; Mon, 16 Sep 2013 06:50:48 +0000
Received: by mail-la0-f41.google.com with SMTP id ec20so2756046lab.14
for <x>; Sun, 15 Sep 2013 23:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
X-Received: by 10.152.22.198 with SMTP id g6mr23282484laf.5.1379311002208;
Sun, 15 Sep 2013 22:56:42 -0700 (PDT)
Received: by 10.114.77.202 with HTTP; Sun, 15 Sep 2013 22:56:41 -0700 (PDT)
Date: Sun, 15 Sep 2013 22:56:41 -0700
Subject: COSTELLO GREAT OPPORTUNITY FIND AS ATTACHED FOR MORE DETAIL.S
From: Alex Morgan <euroarab...@gmail.com>
Content-Type: multipart/mixed; boundary=089e0160bab052534204e679de81
View entire message
0: Received: from mail-la0-f41.google.com ([22.214.171.124]:47131) by rs3.abstractdns.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.80.1) (envelope-from <euroarab...@gmail.com>) id 1VLSe0-003p8U-0C for x; Mon, 16 Sep 2013 06:50:48 +0000
Hostname verified: mail-la0-f41.google.com
WebHostingBuzz received mail from sending system 126.96.36.199
Tracking message source: 188.8.131.52:
Routing details for 184.108.40.206
[refresh/show] Cached whois for 220.127.116.11 : arin-c...@google.com
ab...@google.com bounces (99 sent : 118 bounces)
Using best contacts
No reporting addresses found for 18.104.22.168, using devnull for tracking.
Message is 8 hours old
22.214.171.124 not listed in cbl.abuseat.org
126.96.36.199 not listed in dnsbl.sorbs.net
188.8.131.52 not listed in accredit.habeas.com
184.108.40.206 not listed in plus.bondedsender.org
220.127.116.11 not listed in iadb.isipp.com
|Re: Google refusing spam reports?||Fixered||9/18/13 6:45 PM|
I have same issue, abuse at google dot com appears to be refusing spam reports...
No reporting addresses found for 18.104.22.168, using devnull for tracking.
|Re: Google refusing spam reports?||Daniel Norton||9/19/13 12:17 PM|
Ditto. Until Google fixes this, I am rejecting email traffic from Google that is not on my whitelist.
|Re: Google refusing spam reports?||marzolian||9/19/13 3:30 PM|
Daniel, my spam is a speck of dust on a tip of an iceberg in an ocean of email. But I get almost nothing from Gmail users. The most frequent repeat offender is Yahoo, who (it seems) doesn't even take abuse reports any more. I report Gmail spammers on this page:
|Re: Google refusing spam reports?||Daniel Norton||9/20/13 10:20 AM|
I've actually stopped getting much Yahoo! spam recently and have suddenly started getting Google spam.
Yes, I’m aware of that absurd form that requires one to manually break apart the spam into five separate pieces in order to report it. I refuse to jump through pointless hoops that only serve to discourage spam reporting. It’s an evil tactic and Google should be ashamed for employing it.