Jump to content
albert2

Google gmail not reportable again !!!!!

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" >

 

Edited by albert2
added more info

Share this post


Link to post
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...

 

Share this post


Link to post
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

 

 

 

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×