Steve Posted May 18, 2018 Posted May 18, 2018 I am able to parse said spam (Headers below), but it stops at Parsing header: How can I correct that? Headers are included. I did a whois and found the ISP responsible and reported it to them manually. Let's see if they take action against their subscriber. Steve Delivered-To: x Received: by 10.55.27.222 with SMTP id m29-v6csp8801729lfi; Thu, 17 May 2018 13:33:58 -0700 (PDT) X-Google-Smtp-Source: AB8JxZp8zZ9h1HZvIRXLiwYIHrWbByUwIg/wb8cVmHln27j3U2TCnavq4fOFUD4KrE66YfvhxZee X-Received: by 10.55.27.222 with SMTP id l70-v6mr2894860wma.96.1526589238124; Thu, 17 May 2018 13:33:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526589238; cv=none; d=google.com; s=arc-20160816; b=OWW4pBTW4xIeQT4z+ENfKQ41+sxZs3kIgUSmTXoq1lZxWcb4cV63c8FdgW2gqn1UIx H0SRHSUx7/qcEc5NPdOWJRL9jTT/vFHbWYiadjBstEIpZJHcE87JvPdGXRpuEwQB6vyA 3yLdeVuX3nNN/VOEunMRmU1Wqa61wazTEKL88U8S2QgUhw6p0aRJkdwmI9it15q5jgb8 qOGfNj9w9lpzlpeTmEwPxMrzoGj6H9GC05RjybSPhOAVPvbXnSVt5NygDiRb8Rue5Ml7 13mnTKPX6c/vZIFtESSXBShfXm44UiYGzz2BUHNJGZmGg59uGH2/OQ+LcGfYUD/Ywoe4 +sOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=reply-to:date:from:to:subject:content-description :content-transfer-encoding:mime-version:message-id :arc-authentication-results; bh=L5uQ3847lKTJi/kJp19g4fX3RH2jLJb88lusCo/eV7c=; b=LlkKcGOIU4wFoyk3oWaF+cfeAJA/fPUmp2klnW4laDVutyd8n2RzIfMFlYPtZlIBzE rfybGJb+F1Rm5nXfYAlwchWc0g1mbHH4kmbLNmWXBkU6Bb+5DOf0H+TznKhGnXJJpLzq Jmjx53BIhiep9bXKCUgbsEhYpvhmPBb5sJejfz+cbx9O5T5lCVibiQnZQBWvVYqCz9id DSkWl6KlEIMgS9WPvuLbBetV7V/45Gd2TOm+fW9ctA6obJPFAgH10+mydaEEQYL5aSbJ G93euR9PfdPBO6ulgHkahdC2Pwhe66OWsxZb/vLGJss3AXnJ/oOJk5zrfb8ZVy5EMBkO 4QTQ== ARC-Authentication-Results: i=1; mx.google.com; spf=fail (google.com: domain of info@lee.com does not designate 62.138.219.247 as permitted sender) smtp.mailfrom=info@lee.com; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=lee.com Return-Path: <info@lee.com> Received: from mail.desync001.de (mail.desync001.de. [62.138.219.247]) by mx.google.com with ESMTP id v1-v6si4975708wrm.195.2018.05.17.13.33.57 for <x>; Thu, 17 May 2018 13:33:58 -0700 (PDT) Received-SPF: fail (google.com: domain of info@lee.com does not designate 62.138.219.247 as permitted sender) client-ip=62.138.219.247; Authentication-Results: mx.google.com; spf=fail (google.com: domain of info@lee.com does not designate 62.138.219.247 as permitted sender) smtp.mailfrom=info@lee.com; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=lee.com Message-Id: <5afd________________________________________SING@mx.google.com> Received: from .desync001.de ([192.168.1.190]) by desync001.de.de with MailEnable ESMTP; Thu, 17 May 2018 22:28:51 +0200 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body Subject: Re:STOP CONTACTING THE WRONG OFFICE FOR YOUR FUND (EFCC RECOVERY FUND UNIT) To: x From: "Mr. Ibrahim Magu" <info@lee.com> Date: Thu, 17 May 2018 22:28:51 +0200 Reply-To: mrfrey_h.nelson@outlook.com X-ME-Bayesian: 0.000000
Lking Posted May 18, 2018 Posted May 18, 2018 If you would provide the TRACKING URL so that everyone could see all that the parser did, it would help us understand why the parser stopped.
petzl Posted May 18, 2018 Posted May 18, 2018 Gmail are stamping headers with network data (ARC) that confuses SpamCop which will fail if any doubt To get SpamCop to parse you have to cut what Gmail call ARC headers to and copy (from) include this line ARC-Authentication-Results: i=1; mx.google.com; past the cut "ARC" in submit notes. "pain in the ARC"
Steve Posted May 19, 2018 Author Posted May 19, 2018 Tracking URL: https://members.spamcop.net/sc?id=z6465604558z5ab95166bf3bae4516ce1f776a969a26z ARC-Authentication-Results: i=1; mx.google.com; spf=fail (google.com: domain of info@lee.com does not designate 62.138.219.247 as permitted sender) smtp.mailfrom=info@lee.com; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=lee.com I tried parsing the email with the above omitted and got this: Parsing header: This header is incomplete. Please supply the full headers of the spam you're trying to report. No source IP address found, cannot proceed.
petzl Posted May 19, 2018 Posted May 19, 2018 On 5/18/2018 at 10:32 PM, Steve said: Tracking URL: https://members.spamcop.net/sc?id=z6465604558z5ab95166bf3bae4516ce1f776a969a26z not the track url
Steve Posted May 22, 2018 Author Posted May 22, 2018 On 5/18/2018 at 1:39 PM, Lking said: If you would provide the TRACKING URL so that everyone could see all that the parser did, it would help us understand why the parser stopped. On 5/19/2018 at 2:34 AM, petzl said: not the track url But Lking said to, so I did.
Lking Posted May 22, 2018 Posted May 22, 2018 Quote SpamCop v 4.9.0 © 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=z6464596797z37da1acbf0f870c9c94be5152xxxxxxxx {id edited} Steve what you provided is not a tracking URL that any of the rest of us can use. Notice you provided a link from a different domain (https://members.spamcop.net) NOT https://www.spamcop.net
Recommended Posts
Archived
This topic is now archived and is closed to further replies.