Received: from localhost by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id FAA25679; Thu, 5 Oct 1995 05:27:49 -0400
Received: by CS.UTK.EDU (bulk_mailer v1.3); Thu, 5 Oct 1995 05:26:31 -0400
Received: from domen.uninett.no by CS.UTK.EDU with SMTP (cf v2.9s-UTK)
	id FAA25200; Thu, 5 Oct 1995 05:26:29 -0400
From: <Harald.T.Alvestrand@uninett.no>
Message-Id: <199510050926.FAA25200@CS.UTK.EDU>
Received: from domen.uninett.no by domen.uninett.no with SMTP (PP) 
          id <15014-0@domen.uninett.no>; Thu, 5 Oct 1995 10:25:46 +0100
X-Mailer: exmh version 1.6.2 7/18/95
To: Alan Barrett <barrett@iafrica.com>
cc: drums@cs.utk.edu
Subject: Re: support for Postmaster address
In-reply-to: Your message of "Wed, 04 Oct 1995 20:15:13 +0200." <Pine.NEB.3.91.951004200624.439Z-100000@daisy.ee.und.ac.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Thu, 05 Oct 1995 10:25:44 +0100
Sender: Harald.T.Alvestrand@uninett.no

I think the requirement should be:

- Any domain that apperason the right-hand side of the @ sign in a valid
  address MUST have a postmaster

- Any domain that is listed in an MX record MUST have a postmaster

- Any FQDN that is listed in a Received header SHOULD have a postmaster

Some "received" headers contain domains like "localhost"; I don't want
to require that postmaster@localhost makes sense.
And I couldn't on the spur of the moment find anything outlawing non-FQDN=
s
in Received: headers.

            Harald A