From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: null email address question [was: Re: [9front] [ports] updated zlib, libpng, libjpeg]
Date: Fri, 21 Aug 2020 10:55:21 -0700 [thread overview]
Message-ID: <20200821175521.GE23861@wopr> (raw)
In-Reply-To: <3a38e880-548f-48e0-baf8-57b45128775c@www.fastmail.com>
On Fri, Aug 21, 2020 at 06:47:53PM +0100, Ethan Gardener wrote:
> > NOTE: If you are using a mail server that is not RFC 2821/2822
> > compliant in that it rejects or discards emails with "NULL" addresses,
> > you will NOT be able to complete the registration process.
>
> is there ever a legitimate use for null addresses?
There are several such messages in various RFCs, mostly delivery status
and message disposition emails. They're sent with null reverse-paths to
prevent nondeliverable notificiation loops. The other place null
addresses show up is in emails with multiple delivery targets where
something broke during populating them like
To: you@example.com,me@example.com,,them@example.com,other@example.com
note the 'null address' between commas in the middle.
RFC2822 declares the latter to be obsolete but receivers must accept
them.
khm
next prev parent reply other threads:[~2020-08-21 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BB7ACCC2C36C421386B4BBD4EA97440F@ewsd.inri.net>
2020-08-21 17:47 ` Ethan Gardener
2020-08-21 17:55 ` Kurt H Maier [this message]
2020-08-21 20:38 ` Lyndon Nerenberg
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=20200821175521.GE23861@wopr \
--to=khm@sciops.net \
--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).