No unique hostname found for source: fd4d:6169:6c63:6f77:0:0:0:b

[svengo]

I am using the mailcow e-mail stack. Of course I learned the host and all forwarded adrresses. Spamcop has problems parsing the upper received-header which is internal. fd4d:x is an internal and unroutable address (RFC 4193). Interesting is the header underneath, from which the actual sending system can be seen.

Return-Path: <dkryan@wwdb.org>
Delivered-To: x
Received: from mail.svengo.net ([fd4d:6169:6c63:6f77::b])
	by 46850f6954c1 with LMTP
	id IPLuNUsVXmFsxAAAxGfoPw
	(envelope-from <dkryan@wwdb.org>)
	for <x>; Wed, 06 Oct 2021 23:29:47 +0200
Received: from cyan.elm.relay.mailchannels.net (cyan.elm.relay.mailchannels.net [23.83.212.47])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.svengo.net (Postcow) with ESMTPS id DC3D01C06D6
	for <x>; Wed,  6 Oct 2021 23:29:44 +0200 (CEST)

Parsing headers is interrupted:

host fd4d:6169:6c63:6f77:0:0:0:b (getting name) no name
0: Received: from mail.svengo.net ([fd4d:6169:6c63:6f77::b]) by 46850f6954c1 with LMTP id IPLuNUsVXmFsxAAAxGfoPw (envelope-from <dkryan@wwdb.org>) for <x>; Wed, 06 Oct 2021 23:29:47 +0200
No unique hostname found for source: fd4d:6169:6c63:6f77:0:0:0:b
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.

Re-learning the host does not work. I am currently removing the header as a workaround.

[petzl]

58 minutes ago, svengo said:

e-learning the host does not work. I am currently removing the header as a workaround.

First set-up "mailhosts"  by clicking mailhost tab (if you haven't done so)
SpamCop cannot parse email that is fed through a company/internal server

[svengo]

5 hours ago, petzl said:

First set-up "mailhosts"  by clicking mailhost tab (if you haven't done so)
SpamCop cannot parse email that is fed through a company/internal server

Normally SpamCop should ignore the internal redirects, right? It works fine otherwise, but not with this header.

Besides that, fd4d:6169:6c63:6f77::b is listed as "Relaying IPsv6" on the mailhost page.

[petzl]

6 hours ago, svengo said:

Normally SpamCop should ignore the internal redirects, right? It works fine otherwise, but not with this header.

Besides that, fd4d:6169:6c63:6f77::b is listed as "Relaying IPsv6" on the mailhost page.

Try 

 

6 hours ago, svengo said:

Normally SpamCop should ignore the internal redirects, right? It works fine otherwise, but not with this header.

Besides that, fd4d:6169:6c63:6f77::b is listed as "Relaying IPsv6" on the mailhost page.

Need a Tracking URL to look at
Before you submit it's on page top expired example below

SpamCop v 5.1.0 © 2020 Cisco Systems, Inc. All rights reserved.
Here is your TRACKING URL - it may be saved for future reference:
https://www.spamcop.net/sc?id=z6638897535zab568c7aa78b449e543f0c2ef2712cf7z
Skip to Reports

[svengo]

13 hours ago, petzl said:

Need a Tracking URL to look at

Here is a fresh one: https://www.spamcop.net/sc?id=z6725802547z647d3fef856246128a514ea93610cbaaz

Thanks in advance!

[petzl]

1 hour ago, svengo said:

Here is a fresh one: https://www.spamcop.net/sc?id=z6725802547z647d3fef856246128a514ea93610cbaaz

Thanks in advance!

Spew Comes from  54.240.8.61 email-abuse[AT]amazon[DOT]com
You need to post abuse from your email address Amazon reject or not reacting SpamCop reports

Ask them to reset password on device
>
Submitted: 10/7/2021, 5:41:51 PM +1100:
Sparkasse - Die neuen Tan-Verfahren
7144357508 ( http://staceyhenning.com/?U8YVFk6ixM ) To: info@intem.msk.ru
7144357506 ( 54.240.8.61 ) To: email-abuse@amazon.com

Submitted: 10/6/2021, 6:16:45 PM +1100:
Sparkasse - Die neuen Tan-Verfahren
7144110104 ( 54.240.8.61 ) To: email-abuse@amazon.com

Submitted: 10/4/2021, 10:54:15 AM +1100:
[ATN] Technical Debt, Content Marketing Analytics, Server Change (10/3)
7143682854 ( 54.240.8.61 ) To: email-abuse@amazon.com

Submitted: 10/4/2021, 8:08:21 AM +1100:
[ATN] Technical Debt, Content Marketing Analytics, Server Change (10/3)
7143666631 ( 54.240.8.61 ) To: email-abuse@amazon.com

Submitted: 9/27/2021, 10:08:38 PM +1000:
[ATN] Data Trends, AI Content Generation, Why I Love Data (9/26)
7142634940 ( https://necolas.github.io/normalize.css/ ) To: abuse@github.com
7142634939 ( http://awakenyourmarketing.com/r/727aa07560f06a... ) To: abuse@cloudflare.com
7142634938 ( 54.240.8.61 ) To: email-abuse@amazon.com

Submitted: 9/26/2021, 4:36:46 AM +1000:
Entrez automne 2021
7142416852 ( http://g.zamiart.com/sendy/l/HXVszBu0hLgTDb763j... ) To: abuse#amazonaws.com@devnull.spamcop.net
7142416851 ( 54.240.8.61 ) To: email-abuse@amazon.com

Edited October 8, 2021 by petzl

[svengo]

Thanks, @petzl!

I think that spamcop has a problem parsing this IPv6 header. The following header (report) is working:

Received: from mail.svengo.net ([172.22.1.253])
	by 2a0cd5e2be4c with LMTP
	id 84zRCI9BYWHnoAEA7uYd+g
	(envelope-from <0100017c63e80725-c16e8612-b94b-4532-82b4-6366020fae8d-000000@amazonses.com>)
	for <x>; Sat, 09 Oct 2021 09:15:27 +0200
Received: from a8-62.smtp-out.amazonses.com (a8-62.smtp-out.amazonses.com [54.240.8.62])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.svengo.net (Postcow) with ESMTPS id 206B61C06E4
	for <x>; Sat,  9 Oct 2021 09:15:25 +0200 (CEST)

 

[petzl]

1 hour ago, svengo said:

Thanks, @petzl!

I think that spamcop has a problem parsing this IPv6 header. The following header (report) is working:

SpamCop cannot segregate nail that has headers passed from a internal network
You have to o this manually from your own email