Jump to content

Mailhost configuration problem, identified internal IP as source

Steve

By Steve
in Routing / Report Address Issues

Recommended Posts

Steve Advanced Member

Steve

Posted
Posted 
When trying to submit the below email for reporting, I get this result (bold text at bottom):
Quote

  


Delivered-To: x
Received: by 10.25.37.132 with SMTP id l126csp3793164lfl;
        Tue, 23 Jan 2018 02:10:54 -0800 (PST)
X-Google-Smtp-Source: AH8x2265/bZX2v/QVSqXULW0DoSFi19JMJg5WFLFQLRvsAMQBHqntc0C08rcUcK+vcNCasfJJoN5
X-Received: by 2002:a17:902:2468:: with SMTP id m37-v6mr5393739plg.398.1516702254128;
        Tue, 23 Jan 2018 02:10:54 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1516702254; cv=none;
        d=google.com; s=arc-20160816;
        b=rGLkIDXNYI1pc81+vs+/z5ihdNePYGmD0IPps1Q+XbJy4pW6fiXqQ2Mv9GJdAPb1Of
         oCEoWnBl/UOsYVAD3emIu7vq1opCpBp5PaxfVSZ9wkNEEdzwyDrkTLG07RNSnmPW3w2Q
         g7Zo44S13iZzKLWsIKoSN/nqO4AQ+Hgt518tkNXrTUC4uy7kUaBA2m2ApMNbMnnyTHIw
         CUTdu9yAqK+QGFNpUKBM6SGhkjiWs2QHaGm9OY6TVti9hozrP94EDqdqUx1E71PtnCP1
         N85MapdH0j2pJXUOLNgdFCoNjDqJJphx1DU+nfSSMEStu40TmanjKZ+JV6jRyrKPLk+q
         i81Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=importance:date:subject:from:to:mime-version:message-id
         :arc-authentication-results;
        bh=VVpOLp74pSTJ4TcldwFEjQmWDK329FPASobstSOqiqs=;
        b=nr9W15bkIUqCSqfDzZtG1iuIIhzdon6ctWgb08Eo30urtoKaF+/DlMSvTuAwkIYSXw
         vCc5s3XYPb6wim/rN1QZnZzAkvhI8yJZMaOzT9fHX4OIIsg0RJVszWtVFsEXdcJG9LQX
         k1++Cld1mibdXZ25zdJRjJ7L9NWP76ZXkXWkzdR0rt8cEMBZZxfvU5MafIKKWcm/0PUJ
         +mCOG2bVrvlmRaJKtl65vu1xs50R+VbFkhmDdAhE2sxGQx2NNSAa9GQpGnaoek8zWF8j
         eO9Ym9/Z3SbeOU116ZPtjsEZ+Gd0j+Q51nfWK8iR9ls/tDMF71oSC8/MePACLPEPWZZu
         Mykg==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of nejio-44@crest.ocn.ne.jp designates 153.149.230.36 as permitted sender) smtp.mailfrom=nejio-44@crest.ocn.ne.jp
Return-Path: <nejio-44@crest.ocn.ne.jp>
Received: from mbkd0135.ocn.ad.jp (mbkd0135.ocn.ad.jp. [153.149.230.36])
        by mx.google.com with ESMTP id b12si12932418pgu.734.2018.01.23.02.10.51;
        Tue, 23 Jan 2018 02:10:54 -0800 (PST)
Received-SPF: pass (google.com: domain of nejio-44@crest.ocn.ne.jp designates 153.149.230.36 as permitted sender) client-ip=153.149.230.36;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of nejio-44@crest.ocn.ne.jp designates 153.149.230.36 as permitted sender) smtp.mailfrom=nejio-44@crest.ocn.ne.jp
Received: from mf-smf-ucb018.ocn.ad.jp (mf-smf-ucb018.ocn.ad.jp [153.149.227.67]) by mbkd0135.ocn.ad.jp (Postfix) with ESMTP id EB1E460418F; Tue, 23 Jan 2018 18:57:07 +0900 (JST)
Received: from mf-smf-ucb018.ocn.ad.jp (mf-smf-ucb018 [153.149.227.67]) by mf-smf-ucb018.ocn.ad.jp (Postfix) with ESMTP id CDC6720628; Tue, 23 Jan 2018 18:57:07 +0900 (JST)
Received: from ntt.pod01.mv-mta-ucb026 (mv-mta-ucb026.ocn.ad.jp [153.149.142.100]) by mf-smf-ucb018.ocn.ad.jp (Switch-3.3.4/Switch-3.3.4) with ESMTP id w0N9v4iw007630; Tue, 23 Jan 2018 18:57:07 +0900
Message-Id: <2018___________________7630@mf-smf-ucb018.ocn.ad.jp>
Received: from smtp.ocn.ne.jp ([153.149.227.167]) by ntt.pod01.mv-mta-ucb026 with id 1lwx1x00S3dLKTM01lwxtF; Tue, 23 Jan 2018 09:57:07 +0000
Received: from smtp.ocn.ne.jp (114-43-183-171.dynamic-ip.hinet.net [114.43.183.171]) by smtp.ocn.ne.jp (Postfix) with ESMTPA; Tue, 23 Jan 2018 18:56:56 +0900 (JST)
MIME-Version: 1.0
To: x <x>, x <x>, x <x>, x <x>, x <x>, x <x>, x <x>
From: Nicole Babcock <nejio-44@crest.ocn.ne.jp>
Subject: 
Date: Tue, 23 Jan 2018 02:56:47 -0700
Importance: normal
X-Priority: 3
Content-Type: multipart/alternative; boundary="_2A44BB38-0FEA-42FE-5A0F-957714B89314_"

  


http://result.equitydelta.com
Nicole Babcock
Parsing header:

host 2002:a17:902:2468:0:0:0:0 (getting name) no name

0: Received: by 2002:a17:902:2468:: with SMTP id m37-v6mr5393739plg.398.1516702254128; Tue, 23 Jan 2018 02:10:54 -0800 (PST)

No unique hostname found for source: 2002:a17:902:2468:0:0:0:0

Possible forgery. Supposed receiving system not associated with any of your mailhosts

Will not trust this Received line.

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.

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.

 

 
 
How can this be fixed so that the emails get reported correctly? BTW, this address (2002:a17:902:2468:0:0:0:0), is registered to IANA.
 
Steve
Link to comment
Share on other sites
Lking What Life?

Lking

Posted
Posted

In the future please include the Tracking URL, and not the text.

Quote

SpamCop v 4.8.7 © 2018 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
https://www.spamcop.net/sc?id=z6437392727zd5176b494aaf328f9c8ad3ba8a7727ebz

Looking at a related thread,

It looks like gmail.com may have reconfigured their mailhost.  You need to log into your reporting account, click on the <Mailhosts> tab and follow the instructions. That should resolve the

Quote
Mailhost configuration problem, identified internal IP as source

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

 

error.  With that the correct source of your spam may be found.

Link to comment
Share on other sites
petzl T-shirt wearing out

petzl

Posted
Posted
12 hours ago, Steve said:

Not sure how to re-configure my gmail mailhost. There are no instructions there.

just create new email host name it gmail2 then send it 

once you get it from "SpamCop robot"  copy full headers and body click the link to paste in "Visit this address:" link

Also remove the link showing your hosts (security)

Link to comment
Share on other sites
petzl T-shirt wearing out

petzl

Posted
Posted
18 hours ago, Steve said:

Tried to add a new host using the current email gmail address I use for reporting spam naming it gmail 2 but it didn't show up.

 

Steve

Works for me? I named mine Gmail2

Link to comment
Share on other sites
  • 2 weeks later...
Steve Advanced Member

Steve

Posted
  • Author
Posted
On 1/29/2018 at 3:56 PM, petzl said:

Works for me? I named mine Gmail2

Mailhost I created (Gmail2) still not showing up in Mailhosts. This is really pissing me off!:( I had SC robot send the emails, I copied the headers and body and put them in their respective fields, submitted them all, but still nothing! If I try to do it via email, I get this error:

 

Quote

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers mangled

It appears that the sample you provided has been altered.  Often, extra
line-breaks are inserted by your software in an invalid format.  Part of
the reason for this proceedure is to ensure that you and your software are
submitting spam in an error-free format.  Please review the relevant FAQ
for your software and ensure you are following a proceedure which returns
intact spam content to SpamCop.

In this sample, the problem was found near the line:
AH8x224J72tFUzirSIWn1+UCtwglWcApcrwoVvEIYEdtDm64PAcKC2efQEMR0BBk9iAHP8VQ5wPf
X-Received: by 10.36.70.81 with SMTP id j78mr46833025itb.58.1517679826402;


This email was sent in response to your email:
Delivered-To: x
Received: by 10.25.123.18 with SMTP id w18csp963044lfc;
        Sat, 3 Feb 2018 09:43:46 -0800 (PST)
X-Google-Smtp-Source:
AH8x224J72tFUzirSIWn1+UCtwglWcApcrwoVvEIYEdtDm64PAcKC2efQEMR0BBk9iAHP8VQ5wPf
X-Received: by 10.36.70.81 with SMTP id j78mr46833025itb.58.1517679826402;
        Sat, 03 Feb 2018 09:43:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517679826; cv=none;
        d=google.com; s=arc-20160816;
        b=RcN3kMfHFwvxywTcjf6/lF/q8rBc4c0SilsJOxIP8R56rWAsmzFbHMcDFF028ZKOGA
         Uq4rQdzSWSJv0+h7kFHD5RyHTwjeehLuRi6V4qUGxIR/sjz/xfGXg9RGPCXCQXTp5XmZ
         m/IgOnVOmcFxdLX623+6oIXUCnQKLvotSC+i/IB437s9bpUDyxH6uLBbNXNNkSNufF8N
         YYK2jMl3IaPCIURlf8WcM13W9gsMe9Hx5IcxQ3aUi6C8exmk7fDTrQJMOCA3RgIsVgmF
         IkBz2H+wGhZPtoUwjG5uAAPXHP4zWPxrNLcE52EJCYwlUXwpeceGq1P0mTRrDyaIAStD
         X2hw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=arc-20160816;
        h=date:message-id:precedence:subject:to:from
         :arc-authentication-results;
        bh=UEWGKqTnMLHuLM3frApvtERWY7tZpxKKhcSggjE5f5I=;
        b=MUMCTvkSyeZUPMx5pRMyZIk9u/LHR5/csnBJdjRx6mh0z7phIinuMVEnvee+S90ezm
         zHJZ9Q31WljMFzuV85GTNvtqJxCoGJ7Bt0BeQrTjl9Dy2mA5YM2Bz+dGnTvOZ0FfT8Yz
         ixtdWSSw5is1BWNM7blqb3p6zwy8y3Xo7g8UOK5a+fMt/OvjvS7m9B2Hn4kYEz5BL11X
         f2DFON0QOmGbIDgzWzZuYwnW2xLpn2XjnGZJkTCRiN8CBfMLe7AeVdCdiBVyh3tbYib8
         rLf/Rh7pBhiqv6nPA6E6ygakdmAmoC+GJc7NcwsqZ9XGFRu1fDad0ygQeU7EsD+XMKpX
         Xzhw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
Return-Path: <service@admin.spamcop.net>
Received: from prod-sc-www03.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id z87si1684416ita.31.2018.02.03.09.43.45
        for x;
        Sat, 03 Feb 2018 09:43:46 -0800 (PST)
Received-SPF: pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
client-ip=184.94.240.112;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
Received: from [68.129.12.106] by spamcop.net with HTTP; Sat, 03 Feb
2018 17:43:45 GMT
From: SpamCop robot <mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net>
To: x
Subject:

[SpamCop] account configuration email
Precedence: list
Message-ID: <wh5a75f4d1g5677@msgid.spamcop.net>
Date: Sat, 03 Feb 2018 17:43:45 GMT
X-Mailer: https://www.spamcop.net/ v4.8.7

Hello SpamCop user,

This email contains special codes and tracking information to help SpamCop
figure out your specific email configuration.  Do not post this email in
public.  It contains confidential information related to the security of
your SpamCop account.

Please return this complete email, preserving full headers and the special
tracking codes below.  Visit this
address:https://www.spamcop.net/mcgi?action=mhreturn

Alternately, you may submit via email.  Forward the message as an
attachment to this address.  Or create a new message and paste this email
into it.  Either way, send it to to:
mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net

Some email software may only support one or the other of these submission
methods.  For information on your email software and to learn how to get
full headers see this FAQ:https://www.spamcop.net/fom-serve/cache/19.html

Special codes follow:
################################################################
X-SpamCop-Mx: alt1.gmail-smtp-in.l.google.com.
X-SpamCop-Mx-Ip: 74.125.124.27
X-SpamCop-Mh-Name: Gmail2
X-SpamCop-Recip: x
X-SpamCop-Unixtime: 1517679825
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
X-SpamCop-Randomness: r5gRKmhD4DthrMCe
X-SpamCop-Hash: 96f4b68810cc972152e252504eb582ae
################################################################

Quote

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers mangled

It appears that the sample you provided has been altered.  Often, extra
line-breaks are inserted by your software in an invalid format.  Part of
the reason for this proceedure is to ensure that you and your software are
submitting spam in an error-free format.  Please review the relevant FAQ
for your software and ensure you are following a proceedure which returns
intact spam content to SpamCop.

In this sample, the problem was found near the line:
AH8x224NOyDo135LJ+62YeUUt7iK/V444Trtt8tdg0pCmY0HJkGe4rQyJMU1p3U8v/ja4T0YnwvH
X-Received: by 10.176.5.70 with SMTP id 64mr36063624uax.87.1517679827592;

Email software FAQs:
<http://www.spamcop.net/fom-serve/cache/19.html>


Please do not respond to this email (replies are ignored).  If you need
help, please consult the SpamCop website ( <http://www.spamcop.net/> ).

This email was sent in response to your email:
Delivered-To: x
Received: by 10.25.123.18 with SMTP id w18csp963065lfc;
        Sat, 3 Feb 2018 09:43:47 -0800 (PST)
X-Google-Smtp-Source:
AH8x224NOyDo135LJ+62YeUUt7iK/V444Trtt8tdg0pCmY0HJkGe4rQyJMU1p3U8v/ja4T0YnwvH
X-Received: by 10.176.5.70 with SMTP id 64mr36063624uax.87.1517679827592;
        Sat, 03 Feb 2018 09:43:47 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517679827; cv=none;
        d=google.com; s=arc-20160816;
        b=vSZGnIT3Fb0enViasP+RE+iHuyAamvG2QzahnyjPq5mizPv0pVM0GQnvp76B+RNi/L
         TDtBQSQkrJ3CQl9n8j34d041+ISPWA4Zzx2qUGTiNcqq5bS8gf1FXpL/AR/yCkMZ4rwl
         +VgE7OVdrBWja5RDyp19/wG6Q/QZ2tpWq9/FF65NN5rAh/JGCoyKJFDtQ/c6/jSjMiRZ
         WFw3LtShNmjH8g2qRxlfBZ2ZTJM4CeMPAEkpNKHKmDKhM0CUTf5ruYIcJdKF+JkYUBym
         SYXttuQPuIw5n1CZk/scgZgBbspANMid5koq+8HY8xI9QL2Ow9yiOEzUQ9tcUFJLaPDH
         VfuQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=arc-20160816;
        h=date:message-id:precedence:subject:to:from
         :arc-authentication-results;
        bh=TY+T0lifqv2sNIUCcP0h115FwGXe0hs5IIXI5p+dpCI=;
        b=kaM3PHvZfDcpJW/kArxGgahWxdZbfvJo9ghQU6Lc7y62197Ghc4y+HYbSElBaPWyHE
         0f85z/Vpt8u8kVcChPyfUYhFUJtFvNgDLt4u5/fHiPOWSdRdbllKFV0rgU4dvODyP+TF
         /Stqiv3l42Jbom1GI0alnU7uvLbKzYFRx3+RGSW/3AO0dA4xBFIWCymHgJndZAwX7OiF
         ApbFS4ID/Y4DZJGSBFNA1znUJ0fHZb3Jeu56kWo7H+CzJ1mYu902d7RgiN+c92AC0j6M
         Q9Si+NkXinyl5OMKQn99etAToYqtR2uL1LYfFVLkMY8d2cjtRDyqHkN32FZkgJgpM9iR
         3j0A==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
Return-Path: <service@admin.spamcop.net>
Received: from prod-sc-www03.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id c7si2015084uad.229.2018.02.03.09.43.46
        for x;
        Sat, 03 Feb 2018 09:43:47 -0800 (PST)
Received-SPF: pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
client-ip=184.94.240.112;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
Received: from [68.129.12.106] by spamcop.net with HTTP; Sat, 03 Feb
2018 17:43:46 GMT
From: SpamCop robot <mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net>
To: x
Subject:

[SpamCop] account configuration email
Precedence: list
Message-ID: <wh5a75f4d2g5677@msgid.spamcop.net>
Date: Sat, 03 Feb 2018 17:43:46 GMT
X-Mailer: https://www.spamcop.net/ v4.8.7

Hello SpamCop user,

This email contains special codes and tracking information to help SpamCop
figure out your specific email configuration.  Do not post this email in
public.  It contains confidential information related to the security of
your SpamCop account.

Please return this complete email, preserving full headers and the special
tracking codes below.  Visit this
address:https://www.spamcop.net/mcgi?action=mhreturn

Alternately, you may submit via email.  Forward the message as an
attachment to this address.  Or create a new message and paste this email
into it.  Either way, send it to to:
mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net

Some email software may only support one or the other of these submission
methods.  For information on your email software and to learn how to get
full headers see this FAQ:https://www.spamcop.net/fom-serve/cache/19.html

Special codes follow:
################################################################
X-SpamCop-Mx: alt4.gmail-smtp-in.l.google.com.
X-SpamCop-Mx-Ip: 74.125.141.26
X-SpamCop-Mh-Name: Gmail2
X-SpamCop-Recip: x
X-SpamCop-Unixtime: 1517679825
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
X-SpamCop-Randomness: YPmxtbHyX60McXzw
X-SpamCop-Hash: 14795a9fbcc4a1cedce56399a96ea4d4
################################################################

Quote

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers mangled

It appears that the sample you provided has been altered.  Often, extra
line-breaks are inserted by your software in an invalid format.  Part of
the reason for this proceedure is to ensure that you and your software are
submitting spam in an error-free format.  Please review the relevant FAQ
for your software and ensure you are following a proceedure which returns
intact spam content to SpamCop.

In this sample, the problem was found near the line:
AH8x227Bg92s5SBfBTj2d/5ZEvqLUXDQVB9QAzLBhqfWLxK9V9Qn/xRRYcNjCxNvHPgnBfTECFIE
X-Received: by 10.55.155.209 with SMTP id d200mr68385657qke.272.1517679828619;

Email software FAQs:
<http://www.spamcop.net/fom-serve/cache/19.html>


Please do not respond to this email (replies are ignored).  If you need
help, please consult the SpamCop website ( <http://www.spamcop.net/> ).

This email was sent in response to your email:
Delivered-To: x
Received: by 10.25.123.18 with SMTP id w18csp963075lfc;
        Sat, 3 Feb 2018 09:43:48 -0800 (PST)
X-Google-Smtp-Source:
AH8x227Bg92s5SBfBTj2d/5ZEvqLUXDQVB9QAzLBhqfWLxK9V9Qn/xRRYcNjCxNvHPgnBfTECFIE
X-Received: by 10.55.155.209 with SMTP id d200mr68385657qke.272.1517679828619;
        Sat, 03 Feb 2018 09:43:48 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517679828; cv=none;
        d=google.com; s=arc-20160816;
        b=ZNpTnodvJZBbdke7mdHGfumrLC+A0HnWjh+5xp6Qg4Oz8+iSUwVZGIuE5qyC/0uH+K
         vdKSr2QN+MdKYwYJNL2wagCYeDgBhXnpJxa3uReOTDteWJh6D/8O9gnp1Auhqf5Ze3lH
         9SLbLQv2JEycAMorFaOpSBe6n5L5eUbpr6JryT6s1lmOeMGm/9LjM/Ho5jxI/8Bj0O68
         Jb2NDh8vVuqH2FO5NHD+DvWEGWjTypkAgfTPArY1UWCDS72EMxMtptfSvxFNF4fqf4Vx
         aimhYAZ9BbRaif3etnFzcMZuBvkihEP5C9VZ9AOhOWIkSmwhKdaJ1IQib+z/wQMSUXCT
         ozpQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=arc-20160816;
        h=date:message-id:precedence:subject:to:from
         :arc-authentication-results;
        bh=0+/oGqosWnTQkSdgSXy8F2Atkqn2ybrG+QTpqvwH6z8=;
        b=O3n563xAp0QfjgIiKi6SJszPdjVE6CKg/jMwx0P3e7t1pouBfwFPdiQ3fx8e0OnnWw
         Wru7Rlieq7e8XP8GEjbiiJpEEmsEilHSrW9CE1HTHKhKcIyE/83/8UHJoqjYDlzv05X9
         0aMXDKtKw+Z1UPsIAftbB9AO7xHHRwKM10MpU/+mOampUwQ7jOUSIfqfXGTjmpHwqBU2
         srm/X58ZthkhDXC1sEy3yOtRZaqMd2+macHCoQ8kFtF/sLeKUNuOmReheuuyH2S7vHlz
         XoKXkjmsAlx7KhEO8kW8HoKEYoOf68DgQQso7CeFhAqv+T4+1FjPVcd9Z2eablMavtJD
         rHjw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
Return-Path: <service@admin.spamcop.net>
Received: from prod-sc-www03.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id h55si4560060qtc.451.2018.02.03.09.43.48
        for x;
        Sat, 03 Feb 2018 09:43:48 -0800 (PST)
Received-SPF: pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
client-ip=184.94.240.112;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
Received: from [68.129.12.106] by spamcop.net with HTTP; Sat, 03 Feb
2018 17:43:47 GMT
From: SpamCop robot <mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net>
To: x
Subject:

[SpamCop] account configuration email
Precedence: list
Message-ID: <wh5a75f4d3g5677@msgid.spamcop.net>
Date: Sat, 03 Feb 2018 17:43:47 GMT
X-Mailer: https://www.spamcop.net/ v4.8.7

Hello SpamCop user,

This email contains special codes and tracking information to help SpamCop
figure out your specific email configuration.  Do not post this email in
public.  It contains confidential information related to the security of
your SpamCop account.

Please return this complete email, preserving full headers and the special
tracking codes below.  Visit this
address:https://www.spamcop.net/mcgi?action=mhreturn

Alternately, you may submit via email.  Forward the message as an
attachment to this address.  Or create a new message and paste this email
into it.  Either way, send it to to:
mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net

Some email software may only support one or the other of these submission
methods.  For information on your email software and to learn how to get
full headers see this FAQ:https://www.spamcop.net/fom-serve/cache/19.html

Special codes follow:
################################################################
X-SpamCop-Mx: alt3.gmail-smtp-in.l.google.com.
X-SpamCop-Mx-Ip: 173.194.68.27
X-SpamCop-Mh-Name: Gmail2
X-SpamCop-Recip: x
X-SpamCop-Unixtime: 1517679825
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
X-SpamCop-Randomness: 3rgi1u0SNrAcxtDC
X-SpamCop-Hash: 6965f4d261a8d1b0a5cafcc22772c8f5
################################################################

Quote

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers mangled

It appears that the sample you provided has been altered.  Often, extra
line-breaks are inserted by your software in an invalid format.  Part of
the reason for this proceedure is to ensure that you and your software are
submitting spam in an error-free format.  Please review the relevant FAQ
for your software and ensure you are following a proceedure which returns
intact spam content to SpamCop.

In this sample, the problem was found near the line:
AH8x227AVjnVFgCgYCCJrcVRXr4tacA3R8VmSP4HcUPaFxUYy8rYcgzOXue94LHcFQgi/fMMe5f9
X-Received: by 10.98.86.130 with SMTP id h2mr9493158pfj.208.1517679830210;

Email software FAQs:
<http://www.spamcop.net/fom-serve/cache/19.html>


Please do not respond to this email (replies are ignored).  If you need
help, please consult the SpamCop website ( <http://www.spamcop.net/> ).

This email was sent in response to your email:
Delivered-To: x
Received: by 10.25.123.18 with SMTP id w18csp963097lfc;
        Sat, 3 Feb 2018 09:43:50 -0800 (PST)
X-Google-Smtp-Source:
AH8x227AVjnVFgCgYCCJrcVRXr4tacA3R8VmSP4HcUPaFxUYy8rYcgzOXue94LHcFQgi/fMMe5f9
X-Received: by 10.98.86.130 with SMTP id h2mr9493158pfj.208.1517679830210;
        Sat, 03 Feb 2018 09:43:50 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517679830; cv=none;
        d=google.com; s=arc-20160816;
        b=GgQyq6qauGpXxU8wRFK7rPlp5b0Nvb9TFvLs69RO9uKGXj+mx0rZhTxgF4jo2q06yE
         Zfqh8z8FRs2rLT+mGANmBwRVFnRC/MasBAWjOPoS9eVKjqMfoD1/cWLF99pRz8Uj0ZfU
         wvv/9CiMfVcCUeCcu4lWQPbgNqOJ7qbIJsC6VViuWUc2Cd1dehtagwMpAodjWdK7tdmf
         GdrQwEyQUobBTUb5B1XSEoa7mYKexYshB+h4y20k5GdkKcDVY8KFR+HsHy3ZCcwY3jLX
         WBKJ2y0Z3jlwlgwZwam+uWvW5YfeslWuaJ2p6r9KIncjlbWgGR1k+MTu7r+ca7WuHrJ9
         /tnw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=arc-20160816;
        h=date:message-id:precedence:subject:to:from
         :arc-authentication-results;
        bh=IDS/lIGnhx9RhMgZ8kpAXqpCO7BzLcZ9CwhjXWP/2Ik=;
        b=ktwRc+5nzt5O0sHNnyVh45pZ3NJzOx7K2TKOictu1K9IH8fafIc16Dcjrk3AZWCWKr
         /eFmCNVHmhcuvgWhuOOo5mAy4NfDvUj/Y/o9ziPAsj0/T2mK4nWvZBr4aaKiHKGM3b3b
         FeaEHb0jb3Qs61XmZUkRHYr1CTmy6I5NuOxj6Z8ucdNOk/Vi5C3NS+Pz2eDEkpDbo7/d
         q6vKqkbkiqx/HDMTS0f8d8a3N5F5k3igb+MCQbquHQ2dDQqBTn/pq60Ik7LkPmt/+rly
         e9ahnm3SSTnC3L2WigK7T3SDji5miCjfRQFQ8QSWdhvr7S7hDTijpzGuN7zeSxb6e+eU
         kfNw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
Return-Path: <service@admin.spamcop.net>
Received: from prod-sc-www03.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id o11si1498068pgn.796.2018.02.03.09.43.49
        for x;
        Sat, 03 Feb 2018 09:43:50 -0800 (PST)
Received-SPF: pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
client-ip=184.94.240.112;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
Received: from [68.129.12.106] by spamcop.net with HTTP; Sat, 03 Feb
2018 17:43:49 GMT
From: SpamCop robot <mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net>
To: x
Subject:

[SpamCop] account configuration email
Precedence: list
Message-ID: <wh5a75f4d5g5677@msgid.spamcop.net>
Date: Sat, 03 Feb 2018 17:43:49 GMT
X-Mailer: https://www.spamcop.net/ v4.8.7

Hello SpamCop user,

This email contains special codes and tracking information to help SpamCop
figure out your specific email configuration.  Do not post this email in
public.  It contains confidential information related to the security of
your SpamCop account.

Please return this complete email, preserving full headers and the special
tracking codes below.  Visit this
address:https://www.spamcop.net/mcgi?action=mhreturn

Alternately, you may submit via email.  Forward the message as an
attachment to this address.  Or create a new message and paste this email
into it.  Either way, send it to to:
mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net

Some email software may only support one or the other of these submission
methods.  For information on your email software and to learn how to get
full headers see this FAQ:https://www.spamcop.net/fom-serve/cache/19.html

Special codes follow:
################################################################
X-SpamCop-Mx: gmail-smtp-in.l.google.com.
X-SpamCop-Mx-Ip: 74.125.28.27
X-SpamCop-Mh-Name: Gmail2
X-SpamCop-Recip: x
X-SpamCop-Unixtime: 1517679825
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
X-SpamCop-Randomness: KngV6LMJWgGMhVVJ
X-SpamCop-Hash: 61512c3eaa346c8b21510b19fcbd73b4
################################################################

 

Quote

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers mangled

It appears that the sample you provided has been altered.  Often, extra
line-breaks are inserted by your software in an invalid format.  Part of
the reason for this proceedure is to ensure that you and your software are
submitting spam in an error-free format.  Please review the relevant FAQ
for your software and ensure you are following a proceedure which returns
intact spam content to SpamCop.

In this sample, the problem was found near the line:
AH8x227scae0DerIwzcbrnRVN+hyZq22K6X+0Rx7h090niz9QhCtgkh44fBm1ok1io3KgTHsShe8
X-Received: by 10.129.43.86 with SMTP id r83mr28828327ywr.309.1517679829565;

Email software FAQs:
<http://www.spamcop.net/fom-serve/cache/19.html>


Please do not respond to this email (replies are ignored).  If you need
help, please consult the SpamCop website ( <http://www.spamcop.net/> ).

This email was sent in response to your email:
Delivered-To: x
Received: by 10.25.123.18 with SMTP id w18csp963088lfc;
        Sat, 3 Feb 2018 09:43:49 -0800 (PST)
X-Google-Smtp-Source:
AH8x227scae0DerIwzcbrnRVN+hyZq22K6X+0Rx7h090niz9QhCtgkh44fBm1ok1io3KgTHsShe8
X-Received: by 10.129.43.86 with SMTP id r83mr28828327ywr.309.1517679829565;
        Sat, 03 Feb 2018 09:43:49 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517679829; cv=none;
        d=google.com; s=arc-20160816;
        b=G6Z8ijF8DyJrnl9109j0rNIcwh9qfnihP+k/bz91gb//St+tuo3GYUPSPXe+w+VE5t
         +reIXg804Jr/YQ4CMwJvQkXUj510z8PrXb3XcWBZc/KJ4xAWV+rzF/fVjvOObYby28n/
         z0DFY/jUNEgp1XCFG/qeRjxXp3NIdP44oZEFCW5b4pNuGsw/zsQfeVkyI/MA5zNPpOKT
         RNc1BZuvXjxqmzN0p5xsPhDuUnFVoJXlXwi9h65rTpVRwaB/1jXCsweJWJJBGU+2yVKl
         +WIV4KQOcDvB7ADAMMYNe+EwW1PRxoMVGKaDROoDGZssmZD83DgS3F9WEHNX3Ed/MRCN
         w/XQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=arc-20160816;
        h=date:message-id:precedence:subject:to:from
         :arc-authentication-results;
        bh=u9x5fNYMJ9SD35+bCMzzrUvr90XuyC+/7EyPxLBaqRk=;
        b=ZobSODoVBF1Iol1MOdHZva/bvRmNgVWXG4gksk6/y+lyv0p2tJ2DSj7CMuqYwFptcE
         8XnDuZY237drkaDpklhdRAHRARXua7/fJpl7QnnQJUO8/6sTQAfsWWA04B6xDDFJhYsD
         WeCKBaJF9F3Enlt0krTewmEb3jATb7dB3i28XU7i3ubL2wzOySB3snZdCb6wmZ/AAfjd
         POcWH7YU6/1YxFYoHrmsfp4Z/7NBCljwBIsEFkUpGP145H6TG0pC5m4L5DG+yXWh8/9v
         0So1PFONnf2/svKCqDA8G9nxvUPSPKsLMCt9hnHvmaLAp2JeqmQ6lVarx5i4zdk4XqRT
         NQgA==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
Return-Path: <service@admin.spamcop.net>
Received: from prod-sc-www03.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id h15si424737ybm.368.2018.02.03.09.43.49
        for x;
        Sat, 03 Feb 2018 09:43:49 -0800 (PST)
Received-SPF: pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
client-ip=184.94.240.112;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of service@admin.spamcop.net
designates 184.94.240.112 as permitted sender)
smtp.mailfrom=service@admin.spamcop.net
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
Received: from [68.129.12.106] by spamcop.net with HTTP; Sat, 03 Feb
2018 17:43:48 GMT
From: SpamCop robot <mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net>
To: x
Subject:

[SpamCop] account configuration email
Precedence: list
Message-ID: <wh5a75f4d4g5677@msgid.spamcop.net>
Date: Sat, 03 Feb 2018 17:43:48 GMT
X-Mailer: https://www.spamcop.net/ v4.8.7

Hello SpamCop user,

This email contains special codes and tracking information to help SpamCop
figure out your specific email configuration.  Do not post this email in
public.  It contains confidential information related to the security of
your SpamCop account.

Please return this complete email, preserving full headers and the special
tracking codes below.  Visit this
address:https://www.spamcop.net/mcgi?action=mhreturn

Alternately, you may submit via email.  Forward the message as an
attachment to this address.  Or create a new message and paste this email
into it.  Either way, send it to to:
mhconf.Ez2CZ0s7jSOYgdKz@cmds.spamcop.net

Some email software may only support one or the other of these submission
methods.  For information on your email software and to learn how to get
full headers see this FAQ:https://www.spamcop.net/fom-serve/cache/19.html

Special codes follow:
################################################################
X-SpamCop-Mx: alt2.gmail-smtp-in.l.google.com.
X-SpamCop-Mx-Ip: 173.194.219.26
X-SpamCop-Mh-Name: Gmail2
X-SpamCop-Recip: x
X-SpamCop-Unixtime: 1517679825
X-SpamCop-Conf: Ez2CZ0s7jSOYgdKz
X-SpamCop-Randomness: kABEoNy156xdyRPO
X-SpamCop-Hash: ebb898e076ca80239bbd7a8ea11b5bc8
################################################################

 

I don't understand. I copied exactly as is from Gmail. Why would it be mangled? This happened for all emails I got from SC robot to set up Gmail 2. All 5 are included above for reference.

 

Steve

Link to comment
Share on other sites
petzl T-shirt wearing out

petzl

Posted
Posted
23 hours ago, Steve said:
On 1/30/2018 at 9:56 AM, petzl said:

Works for me? I named mine Gmail2

Mailhost I created (Gmail2) still not showing up in Mailhosts. This is really pissing me off!:( I had SC robot send the emails, I copied the headers and body and put them in their respective fields, submitted them all, but still nothing! If I try to do it via email, I get this error:

please delete your last post it discloses private infomation!

what sysyrm you using I use WIN10 with Opera browser.

In Gmail's webmail (which is what I use) you simply open email 

To the far right there is a down arrow. Click that for options

Click "Show original" 

on that page there is "Copy to Clipboard" link click it

Then go to the SpanCop link and past it in

 

Link to comment
Share on other sites
petzl T-shirt wearing out

petzl

Posted
Posted
1 hour ago, Steve said:

I am unable to. There is no delete button. I am using WIN10 with Chrome. I submitted everything. No new host has shown up.

 

Steve

jus click edit

Link to comment
Share on other sites
petzl T-shirt wearing out

petzl

Posted
Posted
9 hours ago, Steve said:

There's no edit button on my original post with the copies of the emails.

 

Steve

You need someone with you to show you.

DELETE YOUR PERSONAL INFORMATION YOU POSTED HERE!!!

EVERY POST YOU MAKE HERE HAS A EDIT BUTTON, edit your personal info out

 

Link to comment
Share on other sites
Lking What Life?

Lking

Posted
Posted

Sorry I was not watching that closely.  A person can not edit their post after about two hours.

i will go back through this thread and removed personal email addresses.  If I miss one let me know.

Link to comment
Share on other sites
Steve Advanced Member

Steve

Posted
  • Author
Posted
1 hour ago, Lking said:

Sorry I was not watching that closely.  A person can not edit their post after about two hours.

i will go back through this thread and removed personal email addresses.  If I miss one let me know.

Everything is good, Lking. Why is the forum set up that way? Shouldn't members be able to edit/delete their posts without restrictions?

 

Steve

Link to comment
Share on other sites
Lking What Life?

Lking

Posted
Posted
1 hour ago, Steve said:

Why is the forum set up that way? Shouldn't members be able to edit/delete their posts without restrictions?

From an individual's stand point full control of one's post seems reasonable.  From the forums point of view if anyone could at any time delete their post it could result in threads that don't make any sense, when previous post go missing or are edited to remove/change content.

A member can edit/delete their post for 120 minutes after posting ~~ an opportunity to re-read/correct errors or for author's remorse.

Link to comment
Share on other sites
  • 1 year later...
hughh Newbie

hughh

Posted
Posted
On 1/23/2018 at 12:48 PM, Steve said: 

When trying to submit the below email for reporting, I get this result (bold text at bottom):
 
 
How can this be fixed so that the emails get reported correctly? BTW, this address (2002:a17:902:2468:0:0:0:0), is registered to IANA.
 
Steve

I found that removing mail headers that begin "Arc-" made it possible once again to submit Gmail messages to SpamCop.

Hugh H.

Link to comment
Share on other sites
RobiBue Advanced Member

RobiBue

Posted
Posted
1 hour ago, hughh said:

I found that removing mail headers that begin "Arc-" made it possible once again to submit Gmail messages to SpamCop.

Hugh H.

that, as far as I know, is no longer needed to be done since the SC v5 update.

The gmail problem was solved with the update.

Outlook (hotmail, et.al.) is still not fixed though, but that is definitely on their end...

Link to comment
Share on other sites

Archived

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

Go to topic listing
×
×
  • Create New...