From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from ar.aichi-u.ac.jp ([202.250.160.40]) by ur; Wed Nov 11 23:49:16 EST 2015
Received: from [192.168.0.249] ([123.1.17.136]) by ar; Thu Nov 12 13:49:06 JST 2015
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [9front] upas/smtp -h $fqdn not used for HELO dialogue
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <4c4fcc00f5246af9833217b3223ae1d0@u2.inri>
Date: Thu, 12 Nov 2015 13:49:06 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAED0B1E-4B30-453C-9C29-9599A898CA8D@ar.aichi-u.ac.jp>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: transactional responsive module-oriented TOR over YAML strategy template event
References: <4c4fcc00f5246af9833217b3223ae1d0@u2.inri>
To: 9front@9front.org
X-Mailer: Apple Mail (2.2104)

the relevant parts of rfc1034 is

4.1.1.1  Extended HELLO (EHLO) or HELLO (HELO)

   These commands are used to identify the SMTP client to the SMTP
   server.  The argument field contains the fully-qualified domain name
   of the SMTP client if one is available.  In situations in which the
   SMTP client system does not have a meaningful domain name (e.g., when
   its address is dynamically allocated and no reverse mapping record is
   available), the client SHOULD send an address literal (see section
   4.1.3), optionally followed by information that will help to identify
   the client system.  y The SMTP server identifies itself to the SMTP
   client in the connection greeting reply and in the response to this
   command.

4.1.3 Address Literals

   Sometimes a host is not known to the domain name system and
   communication (and, in particular, communication to report and repair
   the error) is blocked.  To bypass this barrier a special literal form
   of the address is allowed as an alternative to a domain name.  For
   IPv4 addresses, this form uses four small decimal integers separated
   by dots and enclosed by brackets such as [123.255.37.2], which
   indicates an (IPv4) Internet Address in sequence-of-octets form.  For
   IPv6 and other forms of addressing that might eventually be
   standardized, the form consists of a standardized "tag" that
   identifies the address syntax, a colon, and the address itself, in a
   format specified as part of the IPv6 standards [17].

I don=E2=80=99t know if Plan9 smtp server supports literal address
if the server does not have a meaningful domain name.

if supported, such mails may be blocked as SPAM.
it is safe you pass your mail to a legitimate smtp server.


> 2015/11/12 13:12=E3=80=81sl@stanleylieber.com =E3=81=AE=E3=83=A1=E3=83=BC=
=E3=83=AB=EF=BC=9A
>=20
>> smtp option =E2=80=9C-h=E2=80=9D is not for HELO host.
>>=20
>> hostdomain is used for FROM address, which is used if the recipient =
is non-existent.
>> FROM address may be different from HELO host.
>> while HELO host is the system address of the smtp server.
>>=20
>> look rfc2821 in detail
>=20
> Thanks.
>=20
> So, does upas have any facility for controlling the HELO
> dialogue? Consider what happens when a terminal, which is
> rarely endowed with a valid Internet DNS name, sends a
> mail with upas/smtp.
>=20
> sl