LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (1095 bytes) , application/pgp-signature (291 bytes)
Print Reply
Mime-Version:
1.0
Sender:
LISTSERV give-and-take forum <[log in to unmask]>
Date:
Thu, 28 Aug 1997 12:15:52 -0400
Reply-To:
LISTSERV give-and-take forum <[log in to unmask]>
Subject:
From:
Content-Transfer-Encoding:
7bit
In-Reply-To:
Your message of "Wed, 27 Aug 1997 16:05:56 MDT." <[log in to unmask]>
Content-Type:
multipart/signed; boundary="==_Exmh_-1176354216P"; micalg=pgp-md5; protocol="application/pgp-signature"
Comments:
To: "Michael Loftis(ADMIN)" <[log in to unmask]>
On Wed, 27 Aug 1997 16:05:56 MDT, you said:
> Mostly sites seem to be using this to tell where mail comes from
> exclusively.  If it doesn't resolve (as in the case of a blank) then it
> doesn't get there.

Supporting MAIL FROM:<> is *REQUIRED* by RFC1123, section 5.2.9.  This
is a  clarification of RFC821, section  4.1.2.   It's how mail daemons
send  back errors in a way  guaranteed not to loop  (think about if it
came back with a non-null MAIL FROM - you could get two mailer daemons
sending each other error messages).

I've gotten sufficiently fed up with  sites that are that unclued that
I'm in the process of writing auto-flame  scripts for Procmail to deal
with it when Listserv sends me the bounce message.

I would suspect that mail from a  list always has  the MAIL FROM: set,
but mail that has 'From: listserv@hostname' in the RFC822 headers will
go  out with a null MAIL  FROM.   However, Eric or   Nathan is free to
correct me on this ;)

--
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech




ATOM RSS1 RSS2