9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Mailing list mails completely lost?
Date: Fri, 25 Jun 2021 17:21:54 -0400	[thread overview]
Message-ID: <75418F19-3615-43AF-8BBF-532350ED207E@stanleylieber.com> (raw)
In-Reply-To: <YNYaI80ucF6HD5t5@wopr>

On June 25, 2021 2:02:11 PM EDT, Kurt H Maier <khm@sciops.net> wrote:
>On Fri, Jun 25, 2021 at 10:22:26AM -0400, Stanley Lieber wrote:
>> I still see a lot of:
>> 
>> 1ess Jun 25 10:15:09 delivery '/net.alt/dns' does not exist (net!bss-wf.de)
>> 
>> in the logs. this is not just you; many, many delivery attempts end up as similar entries in /sys/log/smtp.fail. I still don't know why this is happening. I'll try to rig some extra logging to see once and for all what is going on.
>
>Which DNS resolver are you querying?  I presume not 9cloud, but I used
>to have problems with assholes returning AAAA records that were useless.
>
>khm
>

we've been seeing similar behavior for a long time. that "'/net.alt/dns' 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.

a month or so ago, as an experiment, I switched from opendns.org servers to running a local resolver. 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=1ess dom=1ess.inri.net
ether=525400099935 ip=216.126.196.35                                                      
ipmask=255.255.255.0                                
ipgw=216.126.196.33                                    
auth=216.126.196.35                                    authdom=yoyodyne                               
#       dns=208.67.222.222                             
#       dns=208.67.220.220                                     
dns=216.126.196.35                                     
mx=1ess.inri.net pref=5                                
txtrr="v=spf1 mx -all"

that said, I'm not entirely sure what goes on between all the little programs involved in mail delivery that access dns, or how to track same.

I also don't understand why /net.alt isn't found, since /net is mounted over /net.alt each time in tcp25 and tcp587 *before* running any mail commands (btw, the listener that runs tcp25 and tcp587 runs as user upas, not as user none).

sl

  reply	other threads:[~2021-06-26  3:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-24 19:05 Tobias Heinicke
2021-06-24 19:37 ` Kurt H Maier
2021-06-24 19:51   ` Stanley Lieber
2021-06-24 22:21     ` ori
2021-06-24 22:46       ` igor
2021-06-24 23:29         ` Stanley Lieber
2021-06-25  5:11           ` theinicke
2021-06-25 14:22             ` Stanley Lieber
2021-06-25 18:02               ` Kurt H Maier
2021-06-25 21:21                 ` Stanley Lieber [this message]
2021-06-25 22:58                   ` Steffen Nurpmeso
2021-06-25 22:02               ` kvik
2021-07-25 19:01               ` Stanley Lieber
2021-07-25 22:31                 ` ori
2021-07-26  8:13                 ` hiro
2021-06-25  8:44           ` Tobias Heinicke
2021-06-25 18:58             ` theinicke
2021-06-26 13:19 ` cinap_lenrek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75418F19-3615-43AF-8BBF-532350ED207E@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).