From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_03_06 autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 29249 invoked from network); 26 Jun 2021 03:19:18 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 26 Jun 2021 03:19:18 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 1ess; Fri Jun 25 17:40:01 -0400 2021 Received: from [127.0.0.1] ([107.207.65.229]) by 5ess; Fri Jun 25 17:21:56 -0400 2021 Date: Fri, 25 Jun 2021 17:21:54 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: References: <1FC08B4E4797C194AE4949ACB7B0D467@bss-wf.de> <9A009966-F20C-49DF-A9F1-C2128929D06B@stanleylieber.com> Message-ID: <75418F19-3615-43AF-8BBF-532350ED207E@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: optimized overflow-preventing ORM over SQL blockchain injection storage Subject: Re: [9front] Mailing list mails completely lost? Reply-To: 9front@9front.org Precedence: bulk On June 25, 2021 2:02:11 PM EDT, Kurt H Maier wrote: >On Fri, Jun 25, 2021 at 10:22:26AM -0400, Stanley Lieber wrote: >> I still see a lot of: >>=20 >> 1ess Jun 25 10:15:09 delivery '/net=2Ealt/dns' does not exist (net!bss-= wf=2Ede) >>=20 >> in the logs=2E this is not just you; many, many delivery attempts end u= p as similar entries in /sys/log/smtp=2Efail=2E I still don't know why this= is happening=2E I'll try to rig some extra logging to see once and for all= what is going on=2E > >Which DNS resolver are you querying? I presume not 9cloud, but I used >to have problems with assholes returning AAAA records that were useless= =2E > >khm > we've been seeing similar behavior for a long time=2E that "'/net=2Ealt/dn= s' does not exist" error shows up *a lot* in the logs, frequently for hosts= that do exist and whose hostnames do resolve on the command line=2E a month or so ago, as an experiment, I switched from opendns=2Eorg servers= to running a local resolver=2E it goes like this: # should work with only -n, but doing so breaks domain resolution for the = local system ndb/dns -nrs and in /lib/ndb/local: sys=3D1ess dom=3D1ess=2Einri=2Enet ether=3D525400099935 ip=3D216=2E126=2E196=2E35 = =20 ipmask=3D255=2E255=2E255=2E0 =20 ipgw=3D216=2E126=2E196=2E33 =20 auth=3D216=2E126=2E196=2E35 authdom=3Dy= oyodyne =20 # dns=3D208=2E67=2E222=2E222 =20 # dns=3D208=2E67=2E220=2E220 =20 dns=3D216=2E126=2E196=2E35 =20 mx=3D1ess=2Einri=2Enet pref=3D5 =20 txtrr=3D"v=3Dspf1 mx -all" that said, I'm not entirely sure what goes on between all the little progr= ams involved in mail delivery that access dns, or how to track same=2E I also don't understand why /net=2Ealt isn't found, since /net is mounted = over /net=2Ealt each time in tcp25 and tcp587 *before* running any mail com= mands (btw, the listener that runs tcp25 and tcp587 runs as user upas, not = as user none)=2E sl