ietf-nntp RFC977bis w.r.t. authentication
sob at academ.com
Thu May 7 14:42:18 PDT 1998
> Since this list doesn't use Reply-To: headers properly, a reply-all goes
> to both the list, with additional copies to potentially _everyone_ who
> ever contributed to the thread to that point. This pisses off people,
> so they try to remove the other individuals in the reply-all. Which sometimes
> results in the ietf-nntp at academ.com address remaining a Cc and not
> a to or from.
The list can certainly set the "reply-to" headers to anything. I guess I
missed earlier mail from you requesting that the behavior of the list be
changed. I do apologize if I did. I have changed the configuration so
the list will put a "reply-to: ietf-nntp at academ.com" in the header now.
By the way, I was searching the RFCs and I couldn't find anywhere were
setting the "Reply-to" header in a mailing list was required. Could you
point that out to me? I'd hate to not use the "Reply-to" headers properly,
but if there is no RFC defining a requirement, I believe that there is no
"proper" requirement to set them.
Stan | Academ Consulting Services |internet: sob at academ.com
Olan | For more info on academ, see this |uucp: mcsun!academ!sob
Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.
More information about the ietf-nntp