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=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 4572 invoked from network); 12 Feb 2021 16:43:39 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 12 Feb 2021 16:43:39 -0000 Received: from oat.nine.sirjofri.de ([5.45.105.127]) by 1ess; Fri Feb 12 11:40:10 -0500 2021 Received: from sirjofri.de ([178.0.65.31]) by oat; Fri Feb 12 17:23:50 +0100 2021 Date: Fri, 12 Feb 2021 16:23:47 +0000 (UTC) From: sirjofri To: Pablo Tesari <9front@9front.org> Message-ID: <11c4b3d0-dac9-4150-99f1-859a5c03e7b4@sirjofri.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Correlation-ID: <11c4b3d0-dac9-4150-99f1-859a5c03e7b4@sirjofri.de> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: wrapper descriptor Subject: Re: [9front] Sending mail error Reply-To: 9front@9front.org Precedence: bulk 12.02.2021 16:59:34 Pablo Tesari : > Hi everybody, Welcome =F0=9F=99=82 > 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=20 multiple sources for setting up a mail server with upas, see my blog,=20 this mailing list (archive) and docs.9front.org. Configuring sending is=20 easier than receiving. Check your /mail/lib/remotemail file and your dns entries, and (in case=20 of gmail) your spam folder there. I recommend using an online mail tester= =20 (the one with the boat) for spam detection and potential=20 misconfiguration. > xxxx Feb 11 18:03:31 delivery '/net.alt/dns' does not exist=20 (net!gmail.com) This error is discussed about just recently. I think it was something=20 like, /net is first tested, and if that didn't succeed, /net.alt is used=20 silently. If you don't use /net.alt it fails, of course. I think there=20 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=20 time my sending mail works fine. In these rare cases I just sent the=20 (archived) mail again.