From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) From: Anthony Sorace In-Reply-To: Date: Wed, 5 Nov 2014 12:40:24 -0500 Content-Transfer-Encoding: 7bit Message-Id: <9C58B6D5-AD15-4F4B-AF15-367BC37EE61B@9srv.net> References: <64562eef8a41a3bf4522cd750ac9d1a5@quintile.net> <20141031130919.PTgJzDSl%sdaoden@yandex.com> <00f41dd88b47a3c64637a4e184cbc332@ladd.quanstro.net> <20141031180930.b3WeLqGt%sdaoden@yandex.com> <237c85544512abf78cc131d9c8a526bc@ladd.quanstro.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] Setting up Mail in Acme on the Raspberry Pi. Topicbox-Message-UUID: 232c9ef8-ead9-11e9-9d60-3106f5b1d025 > I've been looking through the documentation and > the 9fans archive but I can't get a clear answer on > what to replace localhost.localdomain with. If the recipient's mail server is being strict (but within the bounds of the RFCs), that name is expected to be the real, externally-resolvable DNS name of the system you're sending from. The RFCs used to be more lax on that point, and some servers still are, but you shouldn't assume you'll be able to send to arbitrary endpoints unless you satisfy that.