From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: 9front@9front.org
Subject: Re: [9front] upas/smtp -h $fqdn not used for HELO dialogue
Date: Thu, 12 Nov 2015 13:49:06 +0900 [thread overview]
Message-ID: <FAED0B1E-4B30-453C-9C29-9599A898CA8D@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <4c4fcc00f5246af9833217b3223ae1d0@u2.inri>
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’t 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、sl@stanleylieber.com のメール:
>
>> smtp option “-h” is not for HELO host.
>>
>> 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.
>>
>> look rfc2821 in detail
>
> Thanks.
>
> 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.
>
> sl
next prev parent reply other threads:[~2015-11-12 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 4:12 sl
2015-11-12 4:49 ` arisawa [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-12 1:17 sl
2015-11-12 3:47 ` [9front] " arisawa
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=FAED0B1E-4B30-453C-9C29-9599A898CA8D@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).