9front - general discussion about 9front
 help / color / mirror / Atom feed
From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] upas email configuration
Date: Tue, 15 Feb 2022 15:50:59 -0800	[thread overview]
Message-ID: <DD889DD564869B253D55850EE095BA8F@gmail.com> (raw)
In-Reply-To: <3805422656F32E7A61C800CDFE8388C5@gmail.com>

Quoth phil9 <telephil9@gmail.com>:
> > >Here is /sys/log/smtp.fail
> > >
> > >ghob Feb 15 00:21:08 delivery '/net.alt/dns' does not exist (net!gmail.com) 
> > >ghob Feb 15 00:21:08 delivery '/net.alt/dns' does not exist (net!gmail.com) 
> > >ghob Feb 15 00:21:08 delivery '/net.alt/dns' does not exist (net!gmail.com) 
> > >
> > >tail /sys/log/mail
> > >ghob Feb 15 00:19:16 remote gmail.com!gunnells From glenda Tue Feb 15 00:19:16 -0800 2022 (gunnells@gmail.com) 192
> > >
> > >Any ideas what might be missing? I also setup a mx record at gandi.net. Gandi handles
> > >all of the DNS and an 'A' record points to the server. 
> > >
> > 
> > the error message is telling you dns lookup failed for some reason.
> 
> This message is actually very misleading. /net.alt/dns is the last (of many) thing(s) upas/smtp tries before erroring out so the actual error might be something totally different.
> I think the easiest way to debug this kind of issue is to redirect the output of upas/smtp in /mail/lib/remotemail. Also, adding -d to the command might give better insight.
> 
> --phil


so /net.alt/dns doesn't exist and I can't create it. Not sure I should create it anyways. 
seems like system will create it or something. 

-d is helpful i think. I have sent so many emails. I kind of need to clean out the queue and start over?

mxdial(net!gmail.com, , <nil>, mx)
sending /net/dns 'gmail.com mx'
sending /net/dns 'gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt1.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt2.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt3.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt4.gmail-smtp-in.l.google.com ip'
mx list: gmail-smtp-in.l.google.com	5	
mx list: gmail-smtp-in.l.google.com	5	74.125.197.26
mx list: alt1.gmail-smtp-in.l.google.com	10	
mx list: alt1.gmail-smtp-in.l.google.com	10	142.250.115.26
mx list: alt2.gmail-smtp-in.l.google.com	20	
mx list: alt2.gmail-smtp-in.l.google.com	20	64.233.171.26
mx list: alt3.gmail-smtp-in.l.google.com	30	
mx list: alt3.gmail-smtp-in.l.google.com	30	142.250.152.26
mx list: alt4.gmail-smtp-in.l.google.com	40	
mx list: alt4.gmail-smtp-in.l.google.com	40	172.253.113.26

mxdial trying gmail-smtp-in.l.google.com	[/net/net!74.125.197.26!smtp]
	failed interrupted
mxdial trying alt1.gmail-smtp-in.l.google.com	[/net/net!142.250.115.26!smtp]
	failed interrupted
mxdial trying alt2.gmail-smtp-in.l.google.com	[/net/net!64.233.171.26!smtp]
	failed interrupted
mxdial trying alt3.gmail-smtp-in.l.google.com	[/net/net!142.250.152.26!smtp]
	failed interrupted
mxdial trying alt4.gmail-smtp-in.l.google.com	[/net/net!172.253.113.26!smtp]
	failed interrupted
sending /net/dns 'gmail.com ip'
sending /net/dns 'gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt1.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt2.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt3.gmail-smtp-in.l.google.com ip'
sending /net/dns 'alt4.gmail-smtp-in.l.google.com ip'
mxdial trying gmail-smtp-in.l.google.com	[/net/net!74.125.197.26!smtp]
	failed interrupted
mxdial trying alt1.gmail-smtp-in.l.google.com	[/net/net!142.250.115.26!smtp]
	failed interrupted
mxdial trying alt2.gmail-smtp-in.l.google.com	[/net/net!64.233.171.26!smtp]
	failed interrupted
mxdial trying alt3.gmail-smtp-in.l.google.com	[/net/net!142.250.152.26!smtp]
	failed interrupted
mxdial trying alt4.gmail-smtp-in.l.google.com	[/net/net!172.253.113.26!smtp]
	failed interrupted
mxdial trying gmail.com	[/net/net!172.217.14.229!smtp]
	failed interrupted

  reply	other threads:[~2022-02-16 10:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15  8:42 thinktankworkspaces
2022-02-15  9:55 ` qwx
2022-02-15 12:49   ` sirjofri
2022-02-24  5:09     ` thinktankworkspaces
2022-02-24 11:05       ` hiro
2022-02-26 20:43         ` thinktankworkspaces
2022-02-15 15:22 ` Stanley Lieber
2022-02-15 17:08   ` Steve Simon
2022-02-15 19:05   ` phil9
2022-02-15 23:50     ` thinktankworkspaces [this message]
2022-02-17  7:24     ` thinktankworkspaces
2022-02-17  7:27     ` thinktankworkspaces

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=DD889DD564869B253D55850EE095BA8F@gmail.com \
    --to=thinktankworkspaces@gmail.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).