From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wopr.sciops.net ([216.126.196.60]) by ewsd; Fri Aug 21 13:55:27 EDT 2020 Received: (qmail 90595 invoked by uid 1001); 21 Aug 2020 10:55:21 -0700 Date: Fri, 21 Aug 2020 10:55:21 -0700 From: Kurt H Maier To: 9front@9front.org Subject: Re: null email address question [was: Re: [9front] [ports] updated zlib, libpng, libjpeg] Message-ID: <20200821175521.GE23861@wopr> Mail-Followup-To: 9front@9front.org References: <3a38e880-548f-48e0-baf8-57b45128775c@www.fastmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a38e880-548f-48e0-baf8-57b45128775c@www.fastmail.com> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: distributed stable plugin-oriented solution 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