Path: ...!weretis.net!feeder6.news.weretis.net!tncsrv06.tnetconsulting.net!tncsrv09.home.tnetconsulting.net!.POSTED.omega.home.tnetconsulting.net!not-for-mail
From: Grant Taylor <gtaylor@tnetconsulting.net>
Newsgroups: news.admin.misc
Subject: Re: Poster's IP in headers
Date: Thu, 14 Mar 2024 21:28:46 -0500
Organization: TNet Consulting
Message-ID: <ut0bou$ug9$3@tncsrv09.home.tnetconsulting.net>
References: <usv360$cls$3$arnold@news.chmurka.net>
 <ut0bkn$ug9$2@tncsrv09.home.tnetconsulting.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Fri, 15 Mar 2024 02:28:46 -0000 (UTC)
Injection-Info: tncsrv09.home.tnetconsulting.net; posting-host="omega.home.tnetconsulting.net:198.18.1.140";
	logging-data="31241"; mail-complaints-to="newsmaster@tnetconsulting.net"
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <ut0bkn$ug9$2@tncsrv09.home.tnetconsulting.net>
Bytes: 1632
Lines: 19

On 3/14/24 21:26, Grant Taylor wrote:
> But does anyone other than you / your organization have any legitimate 
> need for that in the open?

This is why I have the following in the Received: header of emails that 
pass through my MSA:

Received: from Contact-TNet-Consulting-Abuse-for-assistance ...

If someone needs to know where my servers got the message from, they can 
contact me and request the information.

N.B. My understanding is that what I've done is perfectly RFC compliant 
in that it's a really weird host name, but still technically a host 
name.  }:-)



-- 
Grant. . . .