Re: (gnus-inews-domain-name); insertion of Sender:

[Sudish Joseph <joseph@cis.ohio-state.edu>]

Stainless Steel Rat writes:
>>>>>> "SD" == Sten Drescher <stend@grendel.texas.net> writes:

SD> So Son-of-RFC 1036 is discarding its RFC 822 heritage on this
SD> issue?

> No, it superceeds RFC 822, rendering parts of it obsolete.  This is the

822 applies to mail messages, 1036 to news messages.  Neither one can
obsolete the other.  However, 1036 does refer back to 822 on several
issues.

> previous versions of themselves.  Look at the MIME and PEM RFCs sometime.

I don't know about PEM, but MIME certainly doesn't supercede RFC822;
for one thing, MIME deals with the format of the message body while
822 concerns itself with headers. 

SD> This is a problem for Gnus, since it needs to adhere to both
SD> standards.

> No, it needs to adhere to the most recently defined standard.  If it can
> also adhere to the earlier standards for backwards compatability then
> great, but in this case it is not required.

I agree with Sten.  Gnus must follow 822 for mail and 1036 for news.

Also, I agree with the original poster in this thread.  It's silly to
use a user-supplied string for Sender:, especially when Gnus isn't
checking this address in the manner that So1036 specifies.  Why not
simply use (system-name), throwing in the towel if this returns
gibberish.  If misconfiguration at the concerned site renders
system-name useless, Gnus has no way of providing a Sender: header
that satisfies So1036 (short of emulating sendmail)--so why insert
one?

-Sudish