From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: Pablo Tesari <9front@9front.org>
Subject: Re: [9front] Sending mail error
Date: Fri, 12 Feb 2021 16:23:47 +0000 (UTC) [thread overview]
Message-ID: <11c4b3d0-dac9-4150-99f1-859a5c03e7b4@sirjofri.de> (raw)
In-Reply-To: <CALS0JdEPg5Kd-LwzfDTeOGSBuz=qbvkqspqBYxQWBEqVuF7m6g@mail.gmail.com>
12.02.2021 16:59:34 Pablo Tesari <pablotesari@gmail.com>:
> Hi everybody,
Welcome 🙂
> I'm fairly new to plan9 but I was trying to set up a 9front install on
> a vultr server to be able to send mail front there.
> For the configuration I copied rewrite.direct and replaced all
> "YOURDOMAIN" with mine in rewrite, remotemail and smtpd.conf.
Yeah, mail configuration is more than just one config file. There are
multiple sources for setting up a mail server with upas, see my blog,
this mailing list (archive) and docs.9front.org. Configuring sending is
easier than receiving.
Check your /mail/lib/remotemail file and your dns entries, and (in case
of gmail) your spam folder there. I recommend using an online mail tester
(the one with the boat) for spam detection and potential
misconfiguration.
> xxxx Feb 11 18:03:31 delivery '/net.alt/dns' does not exist
(net!gmail.com)
This error is discussed about just recently. I think it was something
like, /net is first tested, and if that didn't succeed, /net.alt is used
silently. If you don't use /net.alt it fails, of course. I think there
was some solution for this error, but I'm not sure about that.
sirjofri
PS: I know this error well because I get it sometimes, but most of the
time my sending mail works fine. In these rare cases I just sent the
(archived) mail again.
next prev parent reply other threads:[~2021-02-12 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 15:59 Pablo Tesari
2021-02-12 16:23 ` sirjofri [this message]
[not found] ` <CALS0JdHkomGQYSp8wHc50fZLPc=yPisoiEZAorhDc=vfTE9YpA@mail.gmail.com>
2021-02-12 22:19 ` Pablo Tesari
2021-02-12 16:32 ` telephil9
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=11c4b3d0-dac9-4150-99f1-859a5c03e7b4@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).