Jump to content

Google gmail not reportable again !!!!!


albert2

Recommended Posts

Hello,

i posted earlier topic about this & so did others

http://forum.spamcop.net/topic/26014-reporting-issues-reason-fake-headers/?tab=comments#comment-115138

http://forum.spamcop.net/topic/14536-mailhost-configuration-problem-identified-internal-ip-as-source/?tab=comments#comment-91162

http://forum.spamcop.net/topic/25761-gmail-how-to/?tab=comments#comment-114543

http://forum.spamcop.net/topic/25970-ongoing-mail-host-problems-with-gmail/?tab=comments#comment-114972

And there are probably more threads about this.

 

However there seems to be another problem now with the headers from mails send to one's gmail address. 

After getting response to earlier threads which included a solution, being to remove the 2nd (& 3th) line(s) but now again it keeps saying :

Mailhost configuration problem, identified internal IP as source

Mailhost:
Please correct this situation - register every email address where you receive spam

No source IP address found, cannot proceed.

 

I will include an example header, hope someone finds a problem that can be solved; The purple lines i have removed like i did before, however removing these lines alone is not working anymore, so there has to be something else wrong in the header. I also tried removing both the purple & orange lines as to me they show similarity in context, but this still gave the same reporting error.

 

Delivered-To: Myemailadress@gmail.com

Received: by 2002:a50:b7ca:0:0:0:0:0 with SMTP id i10csp5151139ede;

        Sat, 1 Dec 2018 17:15:24 -0800 (PST)

X-Google-Smtp-Source: AFSGD/VI8tuKT3hgMGo/T6S9J8LV0TUxad03me5GvNAuGZejcdMuPXnBVRTwwBxZSUpM31Vdv/no

X-Received: by 2002:a1c:dc86:: with SMTP id t128mr3835008wmg.42.1543713324132;

        Sat, 01 Dec 2018 17:15:24 -0800 (PST)

ARC-Seal: i=1; a=rsa-sha256; t=1543713324; cv=none;

        d=google.com; s=arc-20160816;

        b=ZjoExNwS/Cd42bU1MPTyvwhCBWrkmj21HosYpPuD8rKcK9nMIk/JRXVKS31x9svwCP

         uh17Wr6f81AKC8MMjI9OP2nJ+qb8GBr4ZNgxyNBGZ3e/8yKYMA0u0mdau4i3CrL1V4af

         qJcozrLFErbQgu5BlAi/WYM2P2wGIOq7sboKw9Z6mEBzJgQia1Vq4/9T7SU17h78Zrfp

         yhr9fd94O4C6O19s/lfU9pYDXnQ5uYb0o5ZEFmo74vM9zi82ICaIa+5idimdj7cW0W/F

         +JAN/c8OqmRu37yHu1tSuiM+T/mXh1D4euLhNvv1MDzrthhMBLxWspxhvQFRnW2OM35q

         QbOg==

ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;

        h=reply-to:message-id:to:subject:date:from:list-unsubscribe;

        bh=tV2Z7qlInGr+tkIvDOpGOMUcaRSUGjKRdHuidxgCaZA=;

        b=iYLDu9LpQglGro+spovOEaVi9qcRniqP26ffMkI7d8gQlEdWkVd2Yl0/IRfv9g5qAM

         uGbj91gF4xAC3BqIZZxhd9BcqbjEbYNjs5727g6PZ2/dmW9qHgQkpiMYSL6qvgULqGSJ

         9Ty9p3yEH3Y9ppqkKYVbEHr1iqTtIqO2pBNi96fO6NaZZOtUOC3tiDy4lSoal4fdu2Up

         HxuFivBndRbd9SXJwhqA+W1i2GWn0altEOAydB0FYnTxMr65OVVwXdpRGCcolGHNBKwk

         qGs46E4SzkGNl4/FP0clXdpXtdbR+ATOn61JdgAV2+pRKDs7HEUyPeCkaXLK/8RgpdLW

         jbQA==

ARC-Authentication-Results: i=1; mx.google.com;

       spf=softfail (google.com: domain of transitioning bounceemail@google.com does not designate 176.9.188.228 as permitted sender) smtp.mailfrom=BounceEmail@google.com

Return-Path: <BounceEmail@google.com>

Received: from damismanetry.com (damismanetry.com. [176.9.188.228])

        by mx.google.com with ESMTP id r12si7335605wrm.207.2018.12.01.17.15.24

        for <Myemailadress@gmail.com>;

        Sat, 01 Dec 2018 17:15:24 -0800 (PST)

Received-SPF: softfail (google.com: domain of transitioning bounceemail@google.com does not designate 176.9.188.228 as permitted sender) client-ip=176.9.188.228;

Authentication-Results: mx.google.com;

       spf=softfail (google.com: domain of transitioning bounceemail@google.com does not designate 176.9.188.228 as permitted sender) smtp.mailfrom=BounceEmail@google.com

Received: from damismanetry.com (127.0.0.1) by damismanetry.com id h0cp2o16lt0h for <albert2@gmail.com>; Sat, 1 Dec 2018 20:15:23 -0500 (envelope-from <BounceEmail@google.com>)

Received: from s.okazik.pl (s.okazik.pl. 216.244.76.116)

List-Unsubscribe: <HK-ewiufqtkol-__Random_nm[5,l]-b2ce6mg22ipujrjn74rz733ns747n3x4nt1by8hfgfnb9va6@damismanetry.com>

From:Emma.<xipdr@IA1H.veronica.br>

Date: Tue, 22 May 2018 17:39:47 -0400 (EDT)

Subject:  You sent me photos ?

To: <YZZSWPO@pn6cmts.uk>

Message-Id: <PWAYQA-RYUGVUDWDACIWGXOZZXAGGSNLWPCNP@cisco.com>

X-EMMAIL: Myemailadress@gmail.com

Content-Type: text/html

Reply-To: sarah <info@4biancili.org.uk>

 

Please stop sending me your pictures.

Thanks,

 

<img src="http://4biancili.org.uk/kTIl.php?nn=82itk__o22fakeCampaignNV_1ifn.snslfel1.A018trfize01f5v7rv_r3.1959c2c4cTgybzBqZjc00m4NPa"  widht="1" height="1" >

 

Link to comment
Share on other sites

mine reports without problems:

https://www.spamcop.net/sc?id=z6504258765z2c686bd18ea5c5a2c21ec63c840b3fbbz

if you could provide the tracking URL (like the one I provided above) it would be easier to see the problem.

I used the lines you provided for a test, and it parses it correctly...
(removed spaced lines from headers and added X- to Received: line. See comment in parse of test link).

I must admit, I do not use the Mailhost configuration. I report manually/submit via email attachments, so that might be your issue...

 

Link to comment
Share on other sites

I did some testing after your reply.

 

I tried removing my Mailhost config, but that didn't work. So after doing Mailhost config again it suddenly worked again.

I do inde manually report on the website by pasting my spamsource & then removing Google's internal IPv6.

Before i used to send spamcop a mail which contained multiple spam mails in source format but as i can't alter the source this way i had to go to manual reporting (thank spamcop for NOT providing a solution)

Don't expect Google to bring a solution, Google seems to dislike if not hate spamcop & certainly  isn't interested in providing support to spamcop users.

Can you suggest me another lasting & trustworthy free email address supplier which will not try to irritate spamcop users ?

 

PS: Thanks Google for being crappy , untrustworthy, unsupportive Mail service

 

 

 

Link to comment
Share on other sites

On 12/5/2018 at 10:44 AM, albert2 said:

So after doing Mailhost config again it suddenly worked again.

The problem I see with IPv6 is for it to do away with NAT, it has opened up for hundreds of internal networks.  SpamCop seems to remember only a select set of IP addresses with mailhosts.  This means that there could be 2^72 hosts hiding behind a network.  When some people scale up their data centers, they just add more servers instead of fixing the quality of the servers.

Link to comment
Share on other sites

  • 3 weeks later...

I'm one of the forum members posting this problem as referenced in Albert2's Dec. 2 post above. See:

http://forum.spamcop.net/topic/25970-ongoing-mail-host-problems-with-gmail/?tab=comments#comment-114972

Like albert2, the workaround was fine until a few weeks ago (removing the "Received: by..." line(s) from the original full header and spam body, then pasting it into the comments section before hitting the "Process spam" button). 

I used to do this by simply copying the full header and spam body into Apple's TextEdit program as a plain text file, making the edit, then pasting into SC's report spam form. Hope I'm describing this clearly. Again, it worked fine for several months. But now I see what I was seeing before when SC parses the header. Screen shot attached. 

01spamcop-parsing.png.8235b99a1628e3013c14ed42265fbefc.png

My mailhost configuration appears to be correct. It probably doesn't matter, but the only other change I made on my end was upgrading from macOS 10.13.4 to macOS Mojave 10.14.2 (latest build). 

I'm following this thread in hopes to find a workaround that works again. Thanks in advance for any tips that help me report spam forwarded from my Gmail account. Google seems unwilling or unable to make things simple and clean. Sigh. 

If it's helpful, here's the tracking URL generated by SC when I attempted to report the latest Gmail spam.

https://www.spamcop.net/sc?id=z6509941447z78a17f98c019adb8dcd454feb439f9ccz

Thanks again and happy 2019: A new year full of hope and promise — and free from spam. 

 

Link to comment
Share on other sites

15 minutes ago, Art101 said:

f it's helpful, here's the tracking URL generated by SC when I attempted to report the latest Gmail spam.

https://www.spamcop.net/sc?id=z6509941447z78a17f98c019adb8dcd454feb439f9ccz

Thanks again and happy 2019: A new year full of hope and promise — and free from spam. 

remove this line

X-Received: by 2002:a5d:660e:: with SMTP id n14mr29805602wru.19.1546161368641;

then it works if you can mark it as phishing all spam

https://www.spamcop.net/sc?id=z6509955159z47f3673f640081f71a9089e0d8df55dcz

Link to comment
Share on other sites

Thanks petzl, but that didn't work on my end. No joy. After removing the line you suggested, I still see the "nothing to do" message when trying to report Gmail spam.

Good news today: The mail host for my "real" address lets me block entire domains. Google does not. I blocked all incoming mail with anything that includes @hetzner.co.za ... clearly an evil or compromised rogue domain. That won't completely stop the Gmail garbage, but it's a start. 

The Internet is easily the most important advance in human communication since the invention of the printing press (around the year 1440 CE). Unfortunately, the 'net is now highjacked by the worst aspect of human nature: Unbridled greed.

Thanks for your tip; I'll keep an eye on this thread for more news and possible solutions. 

Link to comment
Share on other sites

22 hours ago, Art101 said:

Good news today: The mail host for my "real" address lets me block entire domains. Google does not. I blocked all incoming mail with anything that includes @hetzner.co.za ... clearly an evil or compromised rogue domain. That won't completely stop the Gmail garbage, but it's a start.

My ISP/primary email provider has a similar option available, which can be useful. One thing to watch, however, is that sometimes there are limits to how many domains that are blocked.

Link to comment
Share on other sites

2 hours ago, lisati said:

My ISP/primary email provider has a similar option available, which can be useful. One thing to watch, however, is that sometimes there are limits to how many domains that are blocked.

Thanks, lisati. Good info. FYI: My primary email provider (Hostbaby) places no limit on how many domains I can block. Is this a great world, or what? 

Happy new year to all SpamCop members and users... a new year full of hope and promise (and free from spam).

fb-12-29-18.jpg.10f6e27f05eb81c62e8fd52360ab6df0.jpg

Link to comment
Share on other sites

5 hours ago, Art101 said:

Thanks, lisati. Good info. FYI: My primary email provider (Hostbaby) places no limit on how many domains I can block. Is this a great world, or what? 

Happy new year to all SpamCop members and users... a new year full of hope and promise (and free from spam).

fb-12-29-18.jpg.10f6e27f05eb81c62e8fd52360ab6df0.jpg

Art101,

https://www.virustotal.com/en/domain/hetzner.co.za/information/

&

https://www.virustotal.com/en/file/0a69fd51979d402b66a6b07bb78561a62731b0ca7eb1027363c1967c69734c5a/analysis/

may interest you, although, now you've blocked it (good work!) you may not care.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...