From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/11431 Path: main.gmane.org!not-for-mail From: Per Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Default mail address Date: 21 Jun 1997 16:40:06 +0200 Organization: The Church of Emacs Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035151139 30193 80.91.224.250 (20 Oct 2002 21:58:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:58:59 +0000 (UTC) Cc: Justin Sheehy , Alan Shutko , ding@gnus.org Return-Path: Original-Received: from sandy.calag.com (root@sandy [206.190.83.128]) by altair.xemacs.org (8.8.5/8.8.5) with ESMTP id JAA17411 for ; Sat, 21 Jun 1997 09:32:28 -0700 Original-Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16]) by sandy.calag.com (8.8.5/8.8.5) with ESMTP id JAA30629 for ; Sat, 21 Jun 1997 09:33:01 -0700 Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by xemacs.org (8.8.5/8.8.5) with SMTP id LAA19041 for ; Sat, 21 Jun 1997 11:32:15 -0500 (CDT) Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Sat, 21 Jun 1997 16:40:29 +0200 Original-Received: (qmail 31466 invoked by uid 504); 21 Jun 1997 14:40:26 -0000 Original-Received: (qmail 31463 invoked from network); 21 Jun 1997 14:40:26 -0000 Original-Received: from elc1.dina.kvl.dk (130.225.40.228) by claymore.vcinet.com with SMTP; 21 Jun 1997 14:40:25 -0000 Original-Received: from zuse.dina.kvl.dk (zuse.dina.kvl.dk [130.225.40.245]) by elc1.dina.kvl.dk (8.6.12/8.6.4) with ESMTP id QAA13562; Sat, 21 Jun 1997 16:37:54 +0200 Original-Received: (abraham@localhost) by zuse.dina.kvl.dk (8.6.12/8.6.4) id QAA08845; Sat, 21 Jun 1997 16:40:06 +0200 Original-To: joda@pdc.kth.se (Johan Danielsson) X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM|8MBp/ In-Reply-To: joda@pdc.kth.se's message of "21 Jun 1997 15:48:53 +0200" X-Mailer: Gnus v5.4.56/Emacs 19.34 Original-Lines: 63 Original-Xref: altair.xemacs.org dgnus-list:1821 Xref: main.gmane.org gmane.emacs.gnus.general:11431 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:11431 joda@pdc.kth.se (Johan Danielsson) writes: > What is so good about adding a useless `address' as sender of the > message? For News, Son-of-RFC 1036 compliance: 6.4. Sender The Sender header identifies the poster, in the event that this differs from the author identified in the From header: Sender-content = From-content In the absence of Sender, the default poster is the author (named in the From header). NOTE: The intent is that the Sender header have a fairly high probability of identifying the person who really posted the article. The ability to specify a From header naming someone other than the poster is useful but can be abused. If the poster supplies a From header, the posting agent MUST ensure that a Sender header is present, unless it can verify that the mailing address in the From header is a valid mail- ing address for the poster. A poster-supplied Sender header MAY be used, if its mailing address is verifiably a valid mailing address for the poster; otherwise the posting agent MUST supply a Sender header and delete (or rename, e.g. to X-Unverifiable-Sender) any poster-supplied Sender header. NOTE: It might be useful to preserve a poster- supplied Sender header so that the poster can sup- ply the full-name part of the content. The mail- ing address, however, must be right. Hence, the posting agent must generate the Sender header if it is unable to verify the mailing address of a poster-supplied one. NOTE: NNTP implementors, in particular, are urged to note this requirement (which would eliminate the need for ad hoc headers like NNTP-Posting- Host), although there are admittedly some imple- mentation difficulties. A user name from an RFC 1413 server and a host name from an inverse map- ping of the address, perhaps with a "full name" comment noting the origin of the information, would be at least a first approximation: Sender: fred@zoo.toronto.edu (RFC-1413@reverse-lookup; not verified) While this does not completely meet the specs, it comes a lot closer than not having a Sender header at all. Even just supplying a placeholder for the user name: Sender: somebody@zoo.toronto.edu (user name unknown) would be better than nothing. Gnus should not create Sender for mail.