From: "Paul Smedley" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 12280248 for ecs-isp@2rosenthals.com; Thu, 20 Feb 2025 15:57:11 -0500 Received: from [192.168.200.201] (port=55579 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.97.1) (envelope-from ) id 1tlDbQ-00000000263-1IkN for ecs-isp@2rosenthals.com; Thu, 20 Feb 2025 15:57:01 -0500 Received: from vps.smedley.id.au ([142.171.106.2]:44754) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1tlDbL-000000001QU-25R0 for ecs-isp@2rosenthals.com; Thu, 20 Feb 2025 15:56:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smedley.id.au; s=default; t=1740085011; bh=nY6mT5YyEmN0i9YMlOxtCV58/lKxHUSFHk/M1rJBj34=; h=Date:Subject:To:References:From:In-Reply-To:From; b=rTo6tj0CRa+A1Jrr2cfe6kpDaNwJ38kvTb3s23D5GVpFeSCe1HJ6QKyn78HFQHk44 qdYqs/HT9iqgHKmaBby6Hsh4GmhsF+tFUyVed4JD7J7OFQQE366vQJEW5BHuTQ5NTu dR/igPNcNxRTbVPafqtk6dZ7ONUOyWvnGSz5ncS/WVr95LQkMQPLr88ga0CqSRiesa toeOub9BMls4tzYX2h0+GzaMsVGSh0OOiacLjLn7HDZLxcsFilZ43+wrNhWJtqvWNw vqlWpWGHaBlfsETLy4YD4JtCqc/Vji+K/02AzooaSB9SCbnKOW7Hg0/Ycf+Ssi7x22 xp4X0ojF1h89Q== Received: from [IPV6:2400:a848:4041:0:4742:4772:d3b2:c7a5] (unknown [IPv6:2400:a848:4041:0:4742:4772:d3b2:c7a5]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by vps.smedley.id.au (Postfix) with ESMTPSA id 83EE2200FB for ; Fri, 21 Feb 2025 07:26:51 +1030 (ACDT) Message-ID: Date: Fri, 21 Feb 2025 07:26:41 +1030 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [eCS-ISP] Anyone else seeing issues today with AT&T and RDNS failures when sending? To: eCS ISP Mailing List References: Content-Language: en-AU In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hey Lewis, On 21/2/25 07:05, Lewis G Rosenthal wrote: > Hi, all... > > It's rare that I get an RDNS failure for one of my server IPs, as I > know I have (and have just confirmed again) valid RDNS records in my > providers' DNS. > > Today, att.net rejected mail from us to one of their subscribers with > a 550 5.7.1 error: > >   >     host ff-ip4-mx-vip1.prodigy.net [144.160.159.21] >     SMTP error from remote mail server after MAIL FROM: the 2rosenthals.com domain>: >     550 5.7.1 Connections not accepted from servers without a valid > sender domain.flph829 Fix reverse DNS for 50.73.8.217 > > > 50.73.8.217 is our Leesburg, VA public IP on Comcast's network (I > know; I'm so ashamed...we're in the only four square blocks in > downtown Leesburg where Verizon FiOS is *still* not available). The > RDNS record is: > > secmgr-va.2rosenthals.com > > (verified a few minutes ago at MX-Toolbox) > > I'm wondering if anyone else is having difficulty today. > Confirmed also that rdns works for your IP from the other side of the planet.. psmedley@ThinkPad-X13-Gen-1:~$ host 50.73.8.217 217.8.73.50.in-addr.arpa domain name pointer secmgr-va.2rosenthals.com. Cheers, Paul