From owner-freebsd-questions@freebsd.org Mon Mar 6 22:20:27 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 28B0FD008C2 for ; Mon, 6 Mar 2017 22:20:27 +0000 (UTC) (envelope-from johnl@iecc.com) Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "miucha.iecc.com", Issuer "StartCom Class 1 DV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B93781CC2 for ; Mon, 6 Mar 2017 22:20:26 +0000 (UTC) (envelope-from johnl@iecc.com) Received: (qmail 55894 invoked from network); 6 Mar 2017 22:20:25 -0000 Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 6 Mar 2017 22:20:25 -0000 Date: 6 Mar 2017 22:20:03 -0000 Message-ID: <20170306222003.26539.qmail@ary.lan> From: "John Levine" To: freebsd-questions@freebsd.org Subject: Re: Off topic: smtp HELO question In-Reply-To: <58BD9DC2.9020802@sneakertech.com> Organization: X-Headerized: yes Mime-Version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8bit 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 22:20:27 -0000 This really should go to the mailop mailing list. See https://chilli.nosignal.org/mailman/listinfo/mailop and don't be surprised if its TLS certificate is expired. When you send mail, Thunderbird is doing submission, not SMTP. They are similar, but they are not the same. Approximately 100% of submission clients behind NATs put some random name or IP as the EHLO name, and it doesn't matter. That's not your problem. >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. That would be, to put it mildly, stupendously broken. If they do that, their false positive rate will be something like 50%, including everything sent from Gmail. It would be a good idea to check again and see if perhaps they're doing something else and your problem is something else. Regards, John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. http://jl.ly