From owner-freebsd-questions@freebsd.org Mon Mar 6 19:53:21 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EAFDCFC028 for ; Mon, 6 Mar 2017 19:53:21 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from douhisi.pair.com (douhisi.pair.com [209.68.5.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 305611F20 for ; Mon, 6 Mar 2017 19:53:20 +0000 (UTC) (envelope-from quartz@sneakertech.com) Received: from [192.168.0.1] (pool-72-74-34-8.bstnma.fios.verizon.net [72.74.34.8]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by douhisi.pair.com (Postfix) with ESMTPSA id 5C1E53F531 for ; Mon, 6 Mar 2017 14:53:19 -0500 (EST) Message-ID: <58BDBE2F.90207@sneakertech.com> Date: Mon, 06 Mar 2017 14:53:19 -0500 From: Quartz MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Off topic: smtp HELO question References: <58BD94BD.9020405@sneakertech.com> <1350d47b-5723-5171-3cd9-27e9b02aeb8b@FreeBSD.org> <58BD9DC2.9020802@sneakertech.com> <20170306184357.60de652b@gumby.homeunix.com> In-Reply-To: <20170306184357.60de652b@gumby.homeunix.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Mar 2017 19:53:21 -0000 >> I do use TLS, but what I'm trying to debug is not so much that the >> email service *I* use checks, but that the final receiving server >> scans through the headers and flags anything with a NAT address. > > > It's probably not that. I suggest you try: > > https://www.mail-tester.com/ > > it may reveal what the problem is, unless it's just a BOFH on the > receiving end doing something very odd. I get a 7/10 (apparently because I never set a SPF to hook my mail service to my domain?).