Jump to content
klappa

Spamcop cannot find source IP

Recommended Posts

5 hours ago, SpamStoolie said:

You are wasting our time.

Here is the tracking URL for the notification of your reply: https://www.spamcop.net/sc?id=z6463822062z8cea344e1ac8a0c262e9cf021e05903cz

It does not parse. — Mailhost configuration problem, identified internal IP as source

Here is a version which does parse: https://www.spamcop.net/sc?id=z6463822656za92385fcecb72345790cc09bcf381478z

What’s the difference? I removed this legitimate Received header:

Received: by 2002:a19:2203:0:0:0:0:0 with SMTP id i3-v6csp2712149lfi;
        Sun, 6 May 2018 22:35:22 -0700 (PDT)

This tool: https://toolbox.googleapps.com/apps/messageheader/  parses the message in its original form just fine. (Notice that it has parsed the offending header, identifying it as the final [Google] SMTP server to handle the message.)

# Delay From *     To * Protocol Time received  
0 2 sec localhost   ip-172-31-39-65.ec2.internal ESMTP 5/7/2018, 1:32:19 AM EDT  
1 3 mins ec2-54-164-168-129.compute-1.amazonaws.com. [Google] mx.google.com ESMTPS 5/7/2018, 1:35:21 AM EDT  
2     [Google] 2002:a50:db8c:: SMTP 5/7/2018, 1:35:21 AM EDT  
3 1 sec   [Google] 2002:a19:2203:0:0:0:0:0 SMTP 5/7/2018, 1:35:22 AM EDT

So, unless you believe that the SpamCop Forum is a spammer, inserting “spoofed headers” to confuse SpamCop in a very subtle way…

Yea! Spamcop should fix this! Every spam in gmail get's a parsing error.

Share this post


Link to post
Share on other sites
8 hours ago, SpamStoolie said:

Received: by 2002:a19:2203:0:0:0:0:0 with SMTP id i3-v6csp2712149lfi;
        Sun, 6 May 2018 22:35:22 -0700 (PDT)

No unique hostname found for source: 2002:a19:2203:0:0:0:0:0

That is correct they are spoofed  no hostname 

https://www.talosintelligence.com/reputation_center/lookup?search=2002:a19:2203:0:0:0:0:0#whois

remove the spoofed headers (pasting them in "comments") then it will parse?

Share this post


Link to post
Share on other sites
6 hours ago, klappa said:

Yea! Spamcop should fix this! Every spam in gmail get's a parsing error.

After removing spoofed headers I stopped getting spam with them?
I believed my gmail address has been "list washed" by spammer

Edited by petzl

Share this post


Link to post
Share on other sites
15 minutes ago, petzl said:

No unique hostname found for source: 2002:a19:2203:0:0:0:0:0

That is correct they are spoofed  no hostname 

https://www.talosintelligence.com/reputation_center/lookup?search=2002:a19:2203:0:0:0:0:0#whois

remove the spoofed headers (pasting them in "comments") then it will parse?

It is not “spoofed.” Remember, Google’s tool https://toolbox.googleapps.com/apps/messageheader/   identifies it as a Google server.

https://whois.arin.net/rest/net/NET6-2002-1/pft?s=2002%3Aa19%3A2203%3A0%3A0%3A0%3A0%3A0

2002::/16 is reserved for use in 6to4 deployments [RFC3056]

I understand that you want this to be the work of some ingenious spammer, and not a bug with SpamCop. I sympathize. Really, I do.

However… it is a bug.

Share this post


Link to post
Share on other sites
2 hours ago, SpamStoolie said:

However… it is a bug.

Easily fixed, SpamCop is a tool and will fail rather than report.  As it should, "we" don't want erroneous reports. 

Even if t is a IPV6 IP won't mean it is not spoofed. If one has the time removing these spoofed headers SpamCop gives a accurate parse.

Why is that so?

Edited by petzl

Share this post


Link to post
Share on other sites
3 hours ago, petzl said:

Easily fixed, SpamCop is a tool and will fail rather than report.  As it should, "we" don't want erroneous reports. 

Even if t is a IPV6 IP won't mean it is not spoofed. If one has the time removing these spoofed headers SpamCop gives a accurate parse.

Why is that so?

Yes, SpamCop parser is just a tool. But it is also a piece of software and software can b3 improved and should be improved when new issues pop up. Take this from a software developer.
How many times do we have to repeat that the headers are not spoofed? Same receiving addresses appear in all legitimate Gmail messages, so they are not spoofed.

I'd rather have a conversation with someone who knows the internals of the SpamCop setup.

As a proof of the issue, I just reported a real SPAM message but I was only able to do so by replacing the IPv6 address with mx.google.com . Here's the parse result: https://www.spamcop.net/sc?id=z6463956991zb94e10c6789e02261b2ccf5ce24b67cdz

Originally the first header was this:

Received: by 2002:a4f:d0c:0:0:0:0:0 with SMTP id 12-v6csp3518497ivn;
        Mon, 7 May 2018 15:19:34 -0700 (PDT)

That might be a better solution than removing the headers but still, it doesn't seem right.

And I have also confirmed that the headers are not spoofed by sending a message containing bare minimum of headers to my Gmail address form a mailserver I control.

Share this post


Link to post
Share on other sites
5 hours ago, Axellence said:

That might be a better solution than removing the headers but still, it doesn't seem right.

It's not right! you need to remove spoofed headers by cut & past then in notes

Abuse desks don't like one altering headers my last spoof just pasted all Gmail headers cutting out the spoofed part then once parsed putting those cut headers in notes

 Additional comments from recipient ]
X-Google-Smtp-Source: 
AH8x224uqG6EmUcfBYgUUgeXFVG8X7M7w5W/y8cGQeu6qelGfT+SEvNeSk
l7OwtDDHo5q1hWz5kT
X-Received: by 2002:a17:902:7c95:: with SMTP id y21-
v6mr18271267pll.243.1517248215276;
        Mon, 29 Jan 2018 09:50:15 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1517248215; cv=none;
        d=google.com; s=arc-20160816;
        
b=rEEv75F5u0pdFSKOVadtEjk7uJrCHelc0PyQpdByEDyjWWjuZAdEQzdb
Zas46sOavz
         
uq51pjdot+3JquNVN0ArIXIeJJew2WImCbj67CeH8ko2enKHNcnHlQ1EJD
dViFjkCSvW
         
h3yeMgOFqQvdv+kwXc+DD2D/1dVJgtV+zRwqNxbf6l3XouOpPm9OAvSBe1
LxCIl4+801
         
RhuvHrHmUiE/o/4qBrkkG98sZu/st4ucNXuFjBeFuIGOylzcgjk54wbEUR
sV6ln/17pW
         
n98BWquLG8kkXQdrvDvlSVhJX/6J7oqN2iar7/rKIoeAnaS0jFjkkBMarB
/vhun3z0MW
         bhVg==
ARC-Message-Signature: i=1; a=rsa-sha256; 
c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=content-transfer-encoding:mime-
version:subject:message-id:reply-to
         :from:date:arc-authentication-results;
        bh=+eTI5hmwWM+vKJlIEYpqSa+SlkHtoDA4l9SsJgC1tGw=;
        
b=hOw+HMMu1x1S7eUFnQM79pTuWFRcJBn4lEk/FyRJpWis8wxd8RSwrd1q
qwME2N+mob
         
Hi35I+9CK7jjE3se5bTIjjgs/phnbdSv/5sIymQuFxTOLWPwNK2WR2luHK
c0Rf2PpqT3
         
BepCqTZ7svwzP1ft10n4kUJxpwJDe3ZHRZ/9GsJZfibirT/TT9O+3yEdwn
3+8ZHmWwsp
         
EmhUGPM4kjpNy37Whc8gs+Lzlkgxqs+FfEAe+vBXLCOE5vj50tkwys2YYc
3dnFsluIGy
         
TT25JEqtd1iaFeQcYHuvN2AJkwOQfwgFeXg1hkdPTtRLAzDSElyMbEYK+B
1yCmQ7bLXy
         pyYA==

[ Offending message ]
ARC-Authentication-Results: i=1; mx.google.com;

 

Share this post


Link to post
Share on other sites
On 5/8/2018 at 5:11 AM, petzl said:

It's not right! you need to remove spoofed headers by cut & past then in notes 

OK, so, every few days, I try to register my mailhosts.

When I do, I get a message that looks (like) this. (Please note the Received header which you have identified as “spoofed.”)

Delivered-To: <x>
Received: by 2002:a19:d83:0:0:0:0:0 with SMTP id 125-v6csp6383584lfn;
        Thu, 17 May 2018 07:32:06 -0700 (PDT)
X-Google-Smtp-Source: AB8JxZp23Az631bA8MQAZ/uFdqAFDDp7R7FzV/qblUYT8nLzljEMk58zgKYvZqszfo6MO2I0EsQe
X-Received: by 2002:ac8:5192:: with SMTP id c18-v6mr5379711qtn.80.1526567526004;
        Thu, 17 May 2018 07:32:06 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1526567526; cv=none;
        d=google.com; s=arc-20160816;
        b=K+iQuklPNW7sT5Vs2dfWVzj4NbMo9sZhz1wFsWUm83eW56xDBwvu3EQjApWsW4dkyy
         iljo9dg2A+9WcovDSxiIUUbMeTJuqVnA7efdy/RRJfq6SCydalbVg6UoerJIDHh7J8+T
         n6ZsbATlp/csMYkriOPT1Py1TKkFKAiUhNYaLYZsz/ZI/jlOOp13OsMXBGip+hMu5gZ0
         Gcuvk+w0d9TmiFCLGmahnRJhiEp1ZviTsnVUUv1DLmDn0hzpa7sxfTlRN6/NDWdT36v3
         aqp0HIo1C/oy9bh6yBJAgwBWA8X2sPWsEP+y0nY4AUhJLehIz2h1uSlOcUETPHABHn6a
         ClaQ==
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=WmXazDtXP5yaO1aKPJQY2ErtqkzHsLEyxIlgk1Jb/HM=;
        b=lbMt0NhP0AZ1Y5AWzhpxCXQWQ9tbjKee1kcFswf4AxHuXsg8r0pGGtsWKL85ueyVRt
         7Q/usSp24aSYDE6rWyxYSH9KdSjRwgRqUvNqd/4kiccNSoW2azt/fqupS2sQwQdLy5Kh
         Xk3rNbyYhxGx2VxPOk4c0gyx3+IQFRPx1/pViBdlRp1XrQxg7lECxb/jRJlZhd3PJbXs
         pRj6w1sg055DtKBKgayYEJfyj2EFeOjLfXCZbvCLCvxgO0GWMhzYJTAwbJRKbHbUOi74
         dzw0hkVyl07hL5dMFjdEwKBS6PgAOQCVR+DwFRSLIluixmNdKxqx5MIJ03LrN8Pr2h0J
         Vw3w==
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-www01.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with SMTP id c8-v6si138274qvb.86.2018.05.17.07.32.05
        for <x>;
        Thu, 17 May 2018 07:32:05 -0700 (PDT)
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: eqSIzAlTSD1ifknY
From: SpamCop robot <mhconf.eqSIzAlTSD1ifknY@cmds.spamcop.net>
To: <x>
Subject: [SpamCop] account configuration email
Precedence: list
Message-ID: <wh5afd9265g7d9a@msgid.spamcop.net>
Date: Thu, 17 May 2018 14:32:05 GMT
X-Mailer: https://www.spamcop.net/ v4.9.0

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.eqSIzAlTSD1ifknY@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.aspmx.l.google.com.
X-SpamCop-Mx-Ip: 209.85.144.27
X-SpamCop-Mh-Name: <x>
X-SpamCop-Recip: <x>
X-SpamCop-Unixtime: 1526567525
X-SpamCop-Conf: eqSIzAlTSD1ifknY
X-SpamCop-Randomness: mcg5OLwTr0hykBeT
X-SpamCop-Hash: 8ec2a92c8077f35ecc3d8d834f7f12ff
################################################################


If I forward that, I get an error like this (please note again the Received header you identify as “spoofed.")

Delivered-To: <x>
Received: by 2002:a19:d83:0:0:0:0:0 with SMTP id 125-v6csp6402479lfn;
        Thu, 17 May 2018 07:50:21 -0700 (PDT)
X-Google-Smtp-Source: AB8JxZomUfqTAM7GD+i5tYxm2ddnxO4Wwiic6RzfDSGFR0eHRsIPW/5xstEKpdkIJd7aO9YwaFG9
X-Received: by 2002:a62:8d51:: with SMTP id z78-v6mr5451109pfd.69.1526568621263;
        Thu, 17 May 2018 07:50:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1526568621; cv=none;
        d=google.com; s=arc-20160816;
        b=d2u3OkVkCH6XDHW1JNHQQZiKyYmZNbnc/fByZmkxNLVvwhynzocaYz6ew87htzHp6c
         oTG5qn/0zB5tpajxMGNDhMQmFff1P1XL8F26BaI0EsTGXH/EkM4QgPF73p3YiGArtmmN
         j3eIlvlLDfUtpQlNPFbWHvh1OMOhIIrsd63xXG6DIoEff/+ltSpMgjK7x9meenCWJkvZ
         t9QfQdpdqcIExZgqwQR7gPSH1TTgI1CTn+T2vpHApo9a1hMsccPWHF7epg/JdWIHizTC
         Oarl0k1pBNE3HHZ1IWuSEd2qHNbTKSbHxgxzcxsCJAFCqY/t4eWhrKxgr+X7DxqzcKiw
         YAvA==
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:domainkey-signature
         :arc-authentication-results;
        bh=OSWthG/jA/05eL6MqeXGlFJ/L7sOJxjSqlxB4/vWK6k=;
        b=Jf7GC6uSFst9VhrL3YbOc0PvboY4so9O/R535FanCM+tQI1lV0UZNaezIGySg8SVV2
         wZZwm2EdflYMdcQmvGbLOYQABEY1/yDae/Qp2dGFSR32mfzjGYic1siqkPk44/ba2mr4
         YESdfDyCoCCyQWukB8pM9WUiEGWDfNexglv5HMNlTbMBkB03d/BFeCC4sZVp0/pFl9gB
         hCq8vS6CIAR5BtgHOZOdizStSbkafoiScQI+N5eH1cyVU6epEhvPIadAFkFHq4NQHTa1
         GVNld6h2Ry51D8AcK2ipsP5oNFEaCjdtVhKOtTtreNKQWM0rdgtHzsHyMlqbyaMZkuQy
         qckw==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of spamcop@devnull.spamcop.net designates 184.94.240.112 as permitted sender) smtp.mailfrom=spamcop@devnull.spamcop.net
Return-Path: <spamcop@devnull.spamcop.net>
Received: from vmx.spamcop.net (vmx.spamcop.net. [184.94.240.112])
        by mx.google.com with ESMTPS id a69-v6si5104351pli.391.2018.05.17.07.50.20
        for <x>
        (version=TLS1 cipher=AES128-SHA bits=128/128);
        Thu, 17 May 2018 07:50:21 -0700 (PDT)
Received-SPF: pass (google.com: domain of spamcop@devnull.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 spamcop@devnull.spamcop.net designates 184.94.240.112 as permitted sender) smtp.mailfrom=spamcop@devnull.spamcop.net
DomainKey-Signature: s=devnull; d=spamcop.net; c=nofws; q=dns;
  h=Received:From:To:Subject:Precedence:Message-ID:Date:
   X-Mailer;
  b=e2WJLtdb0PjCcJSh0a5HWI5cJHZzCCUbf7LRxKmj7R5wRZ0EhYlQUigX
   oeRQa2CetaUGXRpRVO4BDkXfSa8bYLCh8ytyIrwoWQl9shlWViIVDFK57
   Bs+mGHJ39dvaimP;
Received: from prod-sc-app002.sv4.ironport.com (HELO prod-sc-app002.spamcop.net) ([10.8.141.22])
  by prod-sc-smtp-vip.sv4.ironport.com with SMTP; 17 May 2018 07:50:19 -0700
From: SpamCop robot <spamcop@devnull.spamcop.net>
To: <x>
Subject: Spamcop account configuration: error
Precedence: list
Message-ID: <wh5afd96abg3397@msgid.spamcop.net>
Date: Thu, 17 May 2018 14:50:19 GMT
X-Mailer: http://www.spamcop.net/ v4.9.0

Hello SpamCop user,

Sorry, but SpamCop has encountered errors:

Headers not found.

It appears you did not provide all email headers.  Please consult this FAQ
for more information on getting full headers from your software, then try
again.

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



 

 

So, please, stop referring to legitimate headers, which SpamCop cannot process as “spoofed.” My question at this time is, “Is this SpamCop bug being worked on?”

Share this post


Link to post
Share on other sites
10 hours ago, SpamStoolie said:

When I do, I get a message that looks (like) this. (Please note the Received header which you have identified as “spoofed.”)

Yes this is nonsensical spam filtering jargon (spoof) that Gmail now adds to it's headers. Has nothing to do with received email headers, then next week Gmail are likely to change it again, The "ARC"  filtering has nothing to do with anyone but Gmail. They are not genuine recieved headers.

Share this post


Link to post
Share on other sites
16 hours ago, petzl said:

Yes this is nonsensical spam filtering jargon (spoof) that Gmail now adds to it's headers.

I see, you apparently use the word “spoof” differently from me. To me, “spoofing” implies an attempt to deceive. For example:

https://tools.ietf.org/html/rfc5321#section-7.1

 

Quote

 

7.1. Mail Security and Spoofing

SMTP mail is inherently insecure in that it is feasible for even fairly casual users to negotiate directly with receiving and relaying SMTP servers and create messages that will trick a naive recipient into believing that they came from somewhere else. Constructing such a message so that the "spoofed" behavior cannot be detected by an expert is somewhat more difficult, but not sufficiently so as to be a deterrent to someone who is determined and knowledgeable. Consequently, as knowledge of Internet mail increases, so does the knowledge that SMTP mail inherently cannot be authenticated, or integrity checks provided, at the transport level. Real mail security lies only in end-to-end methods involving the message bodies, such as those that use digital signatures (see RFC 1847 [43] and, e.g., Pretty Good Privacy (PGP) in RFC 4880 [44] or Secure/ Multipurpose Internet Mail Extensions (S/MIME) in RFC 3851 [45]).

 

 

The chief problem appears to be the first Received: header, and not the ARC headers. (i.e. if I remove this single Received: header, and leave the ARC headers the message is processed by SpamCop. If I do not remove the Received: header, SpamCop returns an error.) These Received: headers are in no way an attempt to deceive. They are simply not handled well by SpamCop. That is why I say they are not “spoofed.”

The Received: header is required, but its format is somewhat flexible:

 

https://tools.ietf.org/html/rfc5321#section-4.4

 

Quote

 

4.4. Trace Information

When an SMTP server receives a message for delivery or further processing, it MUST insert trace ("time stamp" or "Received") information at the beginning of the message content, as discussed in Section 4.1.1.4.

 

 

One might argue that Google is creating novel Received: headers, and SpamCop should not be expected to support them. However, this attitude is not realistic. If SpamCop does not support these headers, it becomes much less useful, approaching useless.

Share this post


Link to post
Share on other sites
3 hours ago, SpamStoolie said:

I see, you apparently use the word “spoof” differently from me. To me, “spoofing” implies an attempt to deceive. For example:

https://tools.ietf.org/html/rfc5321#section-7.1

What makes you think they are ARC headers? I don't see they are? “spoofing” to me is counterfeit, in this case gibberish, encrypted/coded network headers that only mean something to Google/Gmail spam filtering (a track maybe?) They start and there are a lot of them, just after Delivered-To:X[AT] X [DOT] com? Yes Gmail stamps rhetoric "ARC-Seal" 4 lines down on its network handling/processing. At any rate SpamCop cannot process them.
From experience Gmail will disable one's account if spammers cannot be reported and you therefore will get more and more spam going with false positives to Gmails spam folder. Once it hits 20 which was mine Gmail disable the account.

Edited by petzl

Share this post


Link to post
Share on other sites
30 minutes ago, petzl said:

What makes you think they are ARC headers?

https://tools.ietf.org/html/draft-ietf-dmarc-arc-protocol-14#section-2.1

 

Quote

 

2.1. The "ARC Set" of Header Fields

Each "ARC Set" consists of the following three new header fields:

  1. ARC-Authentication-Results (referred to below as "AAR"): virtually identical in syntax to an Authentication-Results field [RFC7601], this field records the results of all message authentication checks done by the recording ADMD at the time the message arrived. Additional information is placed in this field compared to a standard Authentication-Results field in order to support a more complete DMARC report;
  2. ARC-Message-Signature (referred to below as "AMS"): virtually identical in syntax to DKIM-Signature, this field contains the signature about the message header and body as they existed at the time of handling by the ADMD adding it (including any modifications made by the sealing ADMD); and
  3. ARC-Seal (referred to below as "AS"): highly similar in structure and format to a DKIM-Signature, this field applies a digital signature that protects the integrity of all three of these new fields when they are added by an ADMD, plus all instances of these fields added by prior ADMDs.

 

http://arc-spec.org/

 

Quote

 

Status of ARC

If you are a mailbox provider or mailing list operator, it is time to begin planning your ARC implementation.

The Authenticated Received Chain, or ARC, was adopted as an official work item of the IETF DMARC Working Group in June 2016, and the specification was last updated in December 2017. (Or check for more recent activity at this IETF page.)

Google has deployed ARC in their email services, code libraries and a test suite are freely available, one commercial MTA already includes ARC support, and patches for popular mailing list managers (MLMs) will be released shortly (early 2018). Links to these items are available on our Resources page.

What are the next steps for ARC?

If you are a mailbox provider or intermediary (mailing list operator, message forwarder), you should be planning your ARC implementation now (first half of 2018). Google has added ARC verification and sealing to their email services (Gmail, G Suite, and Google Groups). Several other companies will incorporate ARC into their products and services in the first half 2018.

Patches for the most popular mailing list managers (MLMs) will be available in the first quarter of 2018. Code libraries and modules are already available for those who need to integrate ARC functions into their systems. The commercial MTA MailerQ incorporates ARC, and the milters authentication_milter and OpenARC can be used to deploy ARC with the Postfix, Oracle Communications Messaging Server, and Sendmail MTAs.

 

Edited by SpamStoolie
Added ARC statements that Google has begun using ARC

Share this post


Link to post
Share on other sites
17 minutes ago, SpamStoolie said:

Not seeing sample headers just more gibber that seems to create more problems than it solves. Pointy-heads who implement bad ideas never set failure terms, in others words cancel a bad idea when its a proved failure (a list of defining failure).  Governments are a good example of bad practice keep pouring money into failures. Doubt if Gmail /google care about it's users or SpamCop unless enough turn to another email service. As always  "if something is free you are the product"

Edited by petzl

Share this post


Link to post
Share on other sites

I pointed you to the IETF draft. That explains all about the headers. Start here: https://tools.ietf.org/html/draft-ietf-dmarc-arc-protocol-14#section-3

Whether you like it or even understand it, Google is using ARC. And they are not alone: https://tools.ietf.org/html/draft-ietf-dmarc-arc-protocol-14#section-11

I personally feel ARC is a very good idea.

However, once again, the ARC headers do not appear to be the source of the problem here.

Edited by SpamStoolie
Added pointer to the Implementation Status section of the IETF draft for ARC

Share this post


Link to post
Share on other sites
3 minutes ago, SpamStoolie said:

However, once again, the ARC headers do not appear to be the source of the problem here.

Not that I can see what ARC headers look like only the claimed Gmail ARC headers that have made zero difference to me getting spam or receiving email but it has made it complicated to report spam

Share this post


Link to post
Share on other sites

The ARC headers are not the problem. The problem is that SpamCop does not process the initial Received: header (apparently) because it does not include a FQDN.

If I delete that header, things process. However, deleting that header is an annoyance. SpamCop needs to be fixed.

However, I am getting the distinct impression that no one is working on this problem.

If you would like to see sample ARC headers, check the IETF Draft: https://tools.ietf.org/html/draft-ietf-dmarc-arc-protocol-14#appendix-B

Edited by SpamStoolie
Added pointer to sample ARC headers

Share this post


Link to post
Share on other sites

I suggest everyone take a deep breath and relax for a minute or two or more.  This thread needs to focus on the technical issues, NOT individuals, individual understanding nor motives.

Do keep in mind that how to work with the tool(s) available is the purpose of this forum (Reporting Help) and that there is low probability that any changes will be made to the SpamCop parser to accommodate a draft standard or miss formatted header lines currently being inserted by gmail/google.

That is the view of a volunteer moderator not employed by SpamCop in anyway.

Share this post


Link to post
Share on other sites

You’re welcome.

Now, the question remains, “Is anyone working on this?”

If a developer would like help debugging, I’d be glad to help, if I can.

Share this post


Link to post
Share on other sites
2 minutes ago, SpamStoolie said:

Now, the question remains, “Is anyone working on this?”

 

50 minutes ago, Lking said:

there is low probability that any changes will be made to the SpamCop parser to accommodate a draft standard or miss formatted header lines currently being inserted by gmail/google.

 

Share this post


Link to post
Share on other sites
1 hour ago, SpamStoolie said:

If you are correct, then, I fear, SpamCop is mostly dead. 😢

So is email then

Share this post


Link to post
Share on other sites

I'm seeing this iPv6 address (fake Gmail header) not only in my spam messages but in legitamate Yahoo group mail as well. Here is an example of the legit email. There is no reason to report it because it is not spam. I have tried creating a new mail host to correct this problem to no avail. I use an IP address from a previously submitted spam email that i replaced with the iPV6 address and the emails parse correctly. Should I remove the 1st received line and see if that works?

 

Steve

 

Delivered-To: x
Received: by 2002:a19:166a:0:0:0:0:0 with SMTP id m103-v6csp308577lfi;
        Fri, 18 May 2018 20:52:31 -0700 (PDT)
X-Google-Smtp-Source: AB8JxZqZhKxgJPozDn7VlZDHQcvaO/mndBXJEXu+WkWepbo1UGAcSzdIXi+e7kcnx4t7rPiiz0ed
X-Received: by 2002:a37:1302:: with SMTP id d2-v6mr11116097qkh.258.1526701951382;
        Fri, 18 May 2018 20:52:31 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1526701951; cv=none;
        d=google.com; s=arc-20160816;
        b=fmz/DfU2KgjHK0Onblr49wH8EvYXnw4e39/i/XXtV94B2DMtPo0zJy3Nk2UJD0Konv
         18ndrd8U+Am8VORPURGyeLSIy9pu/QBCcZyW4UoOcfiYzx9pa/4ib90PE7wPpq3IOC+L
         2DRinVH6CY+yQXRRGt6qcFbNA3JVtDK/U8fIgOF6Dwuu/kih7BUGxgdQQboqHyDQDxZZ
         zoAhXzoKDbCoiDw+C3xgEp2WMxW4b7jQYXpjmdCuBr1NKs8Nzd/GG3Ss290opUhZn57b
         lctdgJk54tOPS95pM6uN8/6OErDVwDkYLytgjIGuH+SnT8mN2W1tUkQeMaeETt9HgVHx
         GOpA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=reply-to:subject:date:list-unsubscribe:precedence:list-id
         :delivered-to:mailing-list:mime-version:sender:from:to:message-id
         :dkim-signature:arc-authentication-results;
        bh=k01CHzPB/FoY7WSMqVUKE2h5MfGDrtUu3QB/Ei3eIm8=;
        b=tqmhv0W8NE2gRcvNncYUOLiIP9WbKnQougQA+hd0jXxKgSDEXipVlIFxixh8fm5SJm
         TRkdqtbh/CIDJhIje6K3gVXBJcwDnzoKG3bCiHnNLmUHdU1hNcfsBoupRkM5mrite/Ao
         zQu6zigfVtNCFYt3VMj8EDElOO7fVFPkOv7Xmak1PPzbrsdhPY/vhiFfH0a6MpSrBUEV
         Mz3il6EahwgQxtEq5W2E68WMMYfCwwA+uk/ltfbFCtBKGiH2pBU1uOWvxYMu8n62O/7w
         r8fzzJB+T6FDu0tPTJcKn2qe3J6v7ZaYqgiJ2UpVmdOIrm7UezH8lhBbly5041OpbNIe
         VhIw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@yahoogroups.com header.s=echoe header.b=e678n08E;
       spf=pass (google.com: domain of sentto-32753851-279706-1526701944-@returns.groups.yahoo.com designates 74.6.128.213 as permitted sender) smtp.mailfrom=sentto-32753851-279706-1526701944-@returns.groups.yahoo.com;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yahoogroups.com
Return-Path: <sentto-32753851-279706-1526701944-@returns.groups.yahoo.com>
Received: from sonic320-32.consmr.mail.bf2.yahoo.com (sonic320-32.consmr.mail.bf2.yahoo.com. [74.6.128.213])
        by mx.google.com with ESMTPS id n64-v6si8968028qkf.210.2018.05.18.20.52.30
        for <x>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 18 May 2018 20:52:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of sentto-32753851-279706-1526701944-@returns.groups.yahoo.com designates 74.6.128.213 as permitted sender) client-ip=74.6.128.213;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@yahoogroups.com header.s=echoe header.b=e678n08E;
       spf=pass (google.com: domain of sentto-32753851-279706-1526701944-@returns.groups.yahoo.com designates 74.6.128.213 as permitted sender) smtp.mailfrom=sentto-32753851-279706-1526701944-@returns.groups.yahoo.com;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=yahoogroups.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoogroups.com; s=echoe; t=1526701949; bh=k01CHzPB/FoY7WSMqVUKE2h5MfGDrtUu3QB/Ei3eIm8=; h=To:From:List-Id:List-Unsubscribe:Date:Subject:Reply-To:From:Subject; b=e678n08EObXHOHyU9pr4n0wbc4OpQaPSfDZH5UplSu4yv+07ErROkQMMGFiscyIKFB8G3iIHH5T1g0KjoM6izM3RJUrhIWzSWRsc4bG81ftAAj65uoBNtem5y/X12wYgp33JQk+hGdJXWeE9WTXghcVV32IyFEWAJ8U15mOoSvE=
Received: from sonic.gate.mail.ne1.yahoo.com by sonic320.consmr.mail.bf2.yahoo.com with HTTP; Sat, 19 May 2018 03:52:29 +0000
X-Yahoo-Newman-Id: 32753851-m279706
X-Sender: hera319@gmail.com
X-Apparently-To: tv-rain@yahoogroups.com
X-Received: (qmail 25731 invoked by uid 102); 19 May 2018 03:52:23 -0000
X-Received: from unknown (HELO mtaq5.grp.bf1.yahoo.com) (10.198.29.78)
  by m13.grp.bf1.yahoo.com with SMTP; 19 May 2018 03:52:23 -0000
X-Received: (qmail 21238 invoked from network); 19 May 2018 03:52:23 -0000
X-Received: from unknown (HELO mta1003.groups.mail.bf1.yahoo.com) (98.139.170.167)
  by mtaq5.grp.bf1.yahoo.com with SMTP; 19 May 2018 03:52:23 -0000
X-Received-SPF: pass (domain of gmail.com designates 74.125.82.54 as permitted sender)
X-YMailISG: IqgDyNcWLDu1rHzVLqZrvMwnJpU5fAgygFnIy2aNwA4hXtIa prSYIzralUss4_M8NV07Z.C1wxMEY_6DXxn651Rsdb4t6BEBYkWL6pf87iW9 wZ3f4Dapv4cEqcXEPhYZUxZiv0MujQELl_aK82gObY4hs.BXHjSoBjzGRo7v LFX9PxkyvCCDZO7mVujgYA3uyiM1aWhkjmG5vC0wBcyEwXmzbF.kSpXVQzRm 4aXtBSoJSoVrQ0YYUg0zKfCIPIsfTK4EXRUqC2Pjrkq_tSN5QGfG_O.tjBO6 AS_e9F5AmCYZsIZwfNw8vgHuIzqE3CsTILUhL5PPuY2uVHD__3nM_N65HQal GgykPzGlTxSu.KHTkWGnAte.b1KA35qAOjnV7STKCdub6Jvorc5XrBSYCBpz kvYG92IRqotK7kO.66x58X2z8wrDTY2E0PbPHjPGlJ91ZGIh4YWlkcFH5e9z ARaBAIYiWNEaTnUHHggQ2jv4.IN2ZiePKs3XFTvAbSt8YrQ_LDNYeZFEXGw6 WjwC7GBBN4t7JMRWWvlKhF7flNL.ro8dlt0gbClZ_6_Q4HjQsmKhMi1gzKsg FBBosQ1HSyPTd0JfqdubKvZoDhyDerj.HfZ8QJiP2gU3wJwr3GIC3C5jCiYe N3wY_.APdqGry8BOKPeTveOG37qPoqYuvbU5xSsly7o73vrLQda9no6EHuzU 66.MfaLxT.yrUn1jP9Cep84xcUlcEC6nUQjiC47SeKMhgZ9JEYHVdwS.HgTa CxkG08wiZs2ncEpcRLA51OqQPWIOAKuX1HIuhTRtSnWSrzv1ujOyvadPzs7B 31w3jHLNDKqMCKnaJSOQiCjan7TB.wO8OzIHe2wNlQBw4CgVDzPLN31Y7EBO eNuJwVGqljwNKyeJMOsQk2LNJvL5HYm4RdCvIOMNnBRUbfr8QI8WwG72IU9W 8XZrynTfhYs1YEItwe1x07IvIpDnp3NBJ.UV7dvFGZYyZE5C3JceXd5pduzW RsP4E2K06RVSpRXDgVmJ71s9IJil0A2OKItOxYArHz7Qz9P5Lv4Edd3iXg5x qkiluVuOA3RHiSPCTlaFHJBqmfk4tbrI_59.e6b8KZWGj8ZfPP.AxMuLtZB8 MlRG4Q7anHk6457h3yx2iP2.nA0atx6YOe30IGWUqkbnF_87uxqdtv4-
Authentication-Results: mta1003.groups.mail.bf1.yahoo.com
  from=gmail.com; domainkeys=neutral (no sig);
  from=gmail.com; dkim=pass (ok)
X-Received: from 127.0.0.1
  (EHLO mail-wm0-f54.google.com) (74.125.82.54)
  by mta1003.groups.mail.bf1.yahoo.com with SMTPS; Sat, 19 May 2018 03:52:22 +0000
X-Received: by mail-wm0-f54.google.com with SMTP id f8-v6so18338063wmc.4
        for <TV-Rain@yahoogroups.com>; Fri, 18 May 2018 20:52:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=nEgcCkOJ0rfGFKYEG6lzhdKfBKTw0dlvXiESyORuBwk=;
        b=UNdGnoztnBb+2bgVjopE/yM2xFeVXUwlXXHtmeclJaIyZ+vdQoBsiStzwdV72flH9t
         WpOtdsureUzsxyRWDsyMkZWY1tQj7P2qfAPofFqFFbcB2/UYD8K/PkBExQc/zAPGJnSZ
         XqqG3QCT3UxV/IUugR95D9MmA9m4IU4Qigg+tffN0G6SlFFukHLYuclJ0qisiP++jtqY
         m9fBdQ1Y/fnRohsIsN0PIaEApMq9KrB7vy4AQAWmLMkSbIetAub3T1EyafTBTHWQNM0F
         8UaYlVgLORxEWZtCf6/1DpDz3NuVWBOjI7BJV2oJHbUjxmLn9/3F4EixullBMsPOXLhs
         bIsg==
X-Gm-Message-State: ALKqPwcLItEyx0pIQDTmrl5npUx44Cu0y2udpu81C1o8Edd1vQ5kjb9u XEzyTs8CTSdssIZK8Mfp7A1i4Sen2GPaan/AwEuFwA==
X-Received: by 2002:a50:c119:: with SMTP id l25-v6mr14820412edf.188.1526701941189; Fri, 18 May 2018 20:52:21 -0700 (PDT)
X-Received: by 10.80.142.201 with HTTP; Fri, 18 May 2018 20:52:20 -0700 (PDT)
Message-ID: <CAKXyOF=5MoHzyzv_WWpV-Jdo-4oqBTt9TQRn-gAqayKRctRh6Q@mail.gmail.com>
To: undisclosed-recipients:;
X-Originating-IP: 98.139.170.167
X-Original-From: Candygirl <hera319@gmail.com>
From: "Candygirl hera319@gmail.com [TV-RAIN]" <TV-RAIN@yahoogroups.com>
X-Yahoo-Profile: psp_addict4life
Sender: TV-RAIN@yahoogroups.com
MIME-Version: 1.0
Mailing-List: list TV-RAIN@yahoogroups.com; contact TV-RAIN-owner@yahoogroups.com
Delivered-To: mailing list <TV-RAIN@yahoogroups.com>
List-Id: <TV-RAIN.yahoogroups.com>
Precedence: bulk
List-Unsubscribe: <mailto:TV-RAIN-unsubscribe@yahoogroups.com>
Date: Fri, 18 May 2018 23:52:20 -0400
Subject: [TV-RAIN]- TV - In Contempt S01E05-06 [1 Attachment]
X-Yahoo-Newman-Property: groups-email-tradt-m
Reply-To: TV-RAIN@yahoogroups.com
Content-Type: multipart/mixed; boundary="000000000000e204db056c86fe7b"

--000000000000e204db056c86fe7b
Content-Type: multipart/related; boundary="000000000000e204da056c86fe7a"

--000000000000e204da056c86fe7a
Content-Type: multipart/alternative; boundary="000000000000e204d8056c86fe79"

--000000000000e204d8056c86fe79
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Season 1, Episode 5 =E2=80=93 Necessary Force (Air Date: May/16/18)

Gwen and Tracy struggle to deal with events from their past when they
defend a mother accused of child abuse. Charlie deals with the aftermath of
his unfair arrest.



https://mega.nz/#!H7Q0lYxQ!KZCMeuKOjCdp0Hm199e36og2nt1A0YCjI2TfcJQq9X8



Season 1, Episode 6 =E2=80=93 Banned (Air Date: May/16/18)
Gwen uses an extra-judicial strategy to outwit an overzealous judge.
Bennett invites Gwen to his wedding shower, where she discovers Bennett=E2=
=80=99s
true feelings about her.



https://mega.nz/#!v3RCiDxS!NtAv1Lp5AvvOHxwZAuGlZryHkJ78B1dsPvKsvNwduUI

--000000000000e204d8056c86fe79
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable





<head>

<style type=3D"text/css">
<!--

/* start of attachment style */
       .ygrp-photo-title{
         clear: both;
         font-size: smaller;
         height: 15px;
         overflow: hidden;
         text-align: center;
         width: 75px;
       }
       div.ygrp-photo{
         background-position: center;
         background-repeat: no-repeat;
         background-color: white;
         border: 1px solid black;
         height: 62px;
         width: 62px;
       }

       div.photo-title=20
         a,
         div.photo-title a:active,
         div.photo-title a:hover,
         div.photo-title a:visited {
           text-decoration: none;=20
       }

       div.attach-table div.attach-row {
         clear: both;
       }

       div.attach-table div.attach-row div {
         float: left;
         /* margin: 2px;*/
       }

       p {
         clear: both;
         padding: 15px 0 3px 0;
=09 overflow: hidden;
       }

       div.ygrp-file {
         width: 30px;
         valign: middle;
       }
       div.attach-table div.attach-row div div a {
         text-decoration: none;
       }

       div.attach-table div.attach-row div div span {
         font-weight: normal;
       }

       div.ygrp-file-title {
         font-weight: bold;
       }
 /* end of attachment style */
        -->
        </style>
        </head>
<html>
<head>
<style type=3D"text/css">
<!--
#ygrp-mkp {
  border: 1px solid #d8d8d8;
  font-family: Arial;
  margin: 10px 0;
  padding: 0 10px;
}

#ygrp-mkp hr {
  border: 1px solid #d8d8d8;
}

#ygrp-mkp #hd {
  color: #628c2a;
  font-size: 85%;
  font-weight: 700;
  line-height: 122%;
  margin: 10px 0;
}

#ygrp-mkp #ads {
  margin-bottom: 10px;
}

#ygrp-mkp .ad {
  padding: 0 0;
}

#ygrp-mkp .ad p {
  margin: 0;
}

#ygrp-mkp .ad a {
  color: #0000ff;
  text-decoration: none;
}
-->
</style>
</head>
<body>



<!-- |**|begin egp html banner|**| -->

<br><br>

<!-- |**|end egp html banner|**| -->


<div dir=3D"ltr"><img src=3D"cid:ii_jhcup5g20_163768152e22f3c7" width=3D"47=
2" height=3D"154"><br><br><div>


















<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><span>=C2=A0</span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif">Season
1, Episode 5 =E2=80=93 Necessary Force (Air Date: May/16/18)<span></span></=
span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif">Gwen
and Tracy struggle to deal with events from their past when they defend a
mother accused of child abuse. Charlie deals with the aftermath of his unfa=
ir
arrest.<span></span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><span>=C2=A0</span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><a href=3D"https://mega.nz/#!H7Q0lYxQ!KZCMe=
uKOjCdp0Hm199e36og2nt1A0YCjI2TfcJQq9X8" style=3D"color:blue;text-decoration=
:underline">https://mega.nz/#!H7Q0lYxQ!KZCMeuKOjCdp0Hm199e36og2nt1A0YCjI2Tf=
cJQq9X8</a><span></span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><span>=C2=A0</span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif">Season
1, Episode 6 =E2=80=93 Banned (Air Date: May/16/18)<br>
Gwen uses an extra-judicial strategy to outwit an overzealous judge. Bennet=
t
invites Gwen to his wedding shower, where she discovers Bennett=E2=80=99s t=
rue feelings
about her.<span></span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><span>=C2=A0</span></span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;line-height:normal;=
font-size:11pt;font-family:Calibri,sans-serif"><span style=3D"font-size:9pt=
;font-family:Tahoma,sans-serif"><a href=3D"https://mega.nz/#!v3RCiDxS!NtAv1=
Lp5AvvOHxwZAuGlZryHkJ78B1dsPvKsvNwduUI" style=3D"color:blue;text-decoration=
:underline">https://mega.nz/#!v3RCiDxS!NtAv1Lp5AvvOHxwZAuGlZryHkJ78B1dsPvKs=
vNwduUI</a><span></span></span></p>





<br></div></div>




<!-- |**|begin egp html banner|**| -->

<br>


<br>

<!-- |**|end egp html banner|**| -->


<div width=3D"1" style=3D"color: white; clear: both;"/>__._,_.___</div>

  =09<a style=3D"text-decoration:none; color: #2D50FD;" href=3D"https://gro=
ups.yahoo.com/neo/groups/TV-RAIN/attachments/948523067;_ylc=3DX3oDMTJyZGw5Y=
3NuBF9TAzk3MzU5NzE0BGdycElkAzMyNzUzODUxBGdycHNwSWQDMTcwNTAzNTI5MQRzZWMDYXR0=
YWNobWVudARzbGsDdmlld09uV2ViBHN0aW1lAzE1MjY3MDE5NDQ-">View attachments on t=
he web</a>
 =20
    <div id=3D"fromDMARC" style=3D"clear:both; margin-top: 10px;">
         <hr style=3D"height:2px ; border-width:0; color:#E3E3E3; backgroun=
d-color:#E3E3E3;">
         Posted by: Candygirl <hera319@gmail.com>         <hr style=
=3D"height:2px ; border-width:0; color:#E3E3E3; background-color:#E3E3E3;">
    </div>
<!-- Start Recommendations -->
<!-- End Recommendations -->


<!-- |**|begin egp html banner|**| -->

<br><br>
<tt>
To our Wonderful Members who support us, we would be lost without you!&nbsp=
; <BR>
            &nb=
sp;            =
           YOU are the re=
ason we are the BEST!<BR>
<BR>
            &nb=
sp;            =
      ~TV-RAIN Owners & Organizing Team~</tt>
<br><br>

<!-- |**|end egp html banner|**| -->



<!-- |**|begin egp html banner|**| -->

  <img src=3D"http://geo.yahoo.com/serv?s=3D97476590/grpId=3D32753851/grpsp=
Id=3D1705035291/msgId=3D279706/stime=3D1526701944" width=3D"1" height=3D"1"=
> <br>

<!-- |**|end egp html banner|**| -->

 =20
<!-- |**|begin egp html banner|**| -->

<br>



  =20
    =20
=20
        <!-- |**|begin egp html banner|**| -->
        <div id=3D"ygrp-vital" style=3D"background-color: #f2f2f2; font-fam=
ily: Verdana; font-size: 10px; margin-bottom: 10px; padding: 10px;">

        <span id=3D"vithd" style=3D"font-weight: bold; color: #333; text-tr=
ansform: uppercase; "><a href=3D"https://groups.yahoo.com/neo/groups/TV-RAI=
N/info;_ylc=3DX3oDMTJmZmFlYWIyBF9TAzk3MzU5NzE0BGdycElkAzMyNzUzODUxBGdycHNwS=
WQDMTcwNTAzNTI5MQRzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzE1MjY3MDE5NDQ-" style=3D"t=
ext-decoration: none;">Visit Your Group</a></span>

     <ul style=3D"list-style-type: none; margin: 0; padding: 0; display: in=
line;">
                                                    </ul>
  </div>


<div id=3D"ft" style=3D"font-family: Arial; font-size: 11px; margin-top: 5p=
x; padding: 0 2px 0 0; clear: both;">
  <a href=3D"https://groups.yahoo.com/neo;_ylc=3DX3oDMTJla2VwbjV0BF9TAzk3ND=
c2NTkwBGdycElkAzMyNzUzODUxBGdycHNwSWQDMTcwNTAzNTI5MQRzZWMDZnRyBHNsawNnZnAEc=
3RpbWUDMTUyNjcwMTk0NA--" style=3D"float: left;"><img src=3D"http://l.yimg.c=
om/ru/static/images/yg/img/email/new_logo/logo-groups-137x15.png" height=3D=
"15" width=3D"137" alt=3D"Yahoo! Groups" style=3D"border: 0;"/></a>
  <div style=3D"color: #747575; float: right;"><a href=3D"https://i=
nfo.yahoo.com/privacy/us/yahoo/groups/details.html" style=3D"text-decoratio=
n: none;">Privacy</a><a href=3D"mailto:TV-RAIN-unsubscribe@yahoogro=
ups.com?subject=3DUnsubscribe" style=3D"text-decoration: none;">Unsubscribe=
</a><a href=3D"https://info.yahoo.com/legal/us/yahoo/utos/terms/" s=
tyle=3D"text-decoration: none;">Terms of Use</a> </div>
</div>

<!-- |**|end egp html banner|**| -->

  </div> <!-- ygrp-msg -->

  =20


  <br>

<!-- |**|end egp html banner|**| -->


<div style=3D"color: white; clear: both;"/>__,_._,___</div>
</body>

</html>

--000000000000e204d8056c86fe79--
--000000000000e204da056c86fe7a
Content-Type: image/png; name="image.png"
Content-Disposition: inline; filename="image.png"
Content-Transfer-Encoding: base64
Content-ID: <ii_jhcup5g20_163768152e22f3c7>
X-Attachment-Id: ii_jhcup5g20_163768152e22f3c7


--000000000000e204da056c86fe7a--
--000000000000e204db056c86fe7b
Content-Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document; name="In Contempt.docx"
Content-Disposition: attachment; filename="In Contempt.docx"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_jhcuu2bw1


--000000000000e204db056c86fe7b--

 

Share this post


Link to post
Share on other sites

I suspect ARC if used correctly supposed to delete emails that do not match the sending IP (from domain)? Not intended for sorting

The ONLY ones accurate at this (deleting) are CISCO senderbase spam filter that comes with their servers.

Edited by petzl

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

×