Hmmm, I noticed your second line does not properly match the first one. Specifically the "by 0.0.0.0:2500" section does not match a mailchannels line of "inbound-egress-6.mailchannels.net". Something is strange where the headers do not see to match up. If nothing was lost, then this would be from an internal mailchannels user.
1: Received: from TrololoVPN ([UNAVAILABLE]. [163.172.137.93]) by 0.0.0.0:2500 (trex/5.18.10); Thu, 12 Nov 2020 21:07:09 +0000
No unique hostname found for source: 163.172.137.93
Possible forgery. Supposed receiving system not associated with any of your mailhosts
Will not trust this Received line.
Hi,
I work for MailChannels. We have a few internal MTA hops while processing incoming email in our inbound filtering service. At each hop, we add a Received header as per the RFCs. Some of the internal MTAs are on private IP addresses. The 0.0.0.0:2500 Received header is the first hop into our edge SMTP proxy. While it's not super cool to have an IP of 0.0.0.0, we don't believe it's inconsistent with the RFC.
But please, if we're doing it wrong, we want to fix this and would be keen to know what you all think is the correct way to add headers.
mail hosts does not recogize all mailchannels hosts
in Mailhost Configuration of your Reporting Account
Posted
Hi,
I work for MailChannels. We have a few internal MTA hops while processing incoming email in our inbound filtering service. At each hop, we add a Received header as per the RFCs. Some of the internal MTAs are on private IP addresses. The 0.0.0.0:2500 Received header is the first hop into our edge SMTP proxy. While it's not super cool to have an IP of 0.0.0.0, we don't believe it's inconsistent with the RFC.
But please, if we're doing it wrong, we want to fix this and would be keen to know what you all think is the correct way to add headers.
Thanks
Ken Simpson
MailChannels CEO