Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Persson <pp@pfawww.pp.se>
Cc: ding@ifi.uio.no
Subject: Re: Mail without `From:' lines
Date: 06 May 1996 19:30:28 +0200	[thread overview]
Message-ID: <87wx2pu2tn.fsf@pfawww.pp.se> (raw)
In-Reply-To: Per Abrahamsen's message of 06 May 1996 18:01:15 +0200

Per Abrahamsen <abraham@dina.kvl.dk> writes:

   >>>>> "PP" == Per Persson <pp@pfawww.pp.se> writes:

   PP> It's not up to the mailinglist to add a "From: " header.

   I think the mailing list should reject such submissions, but I suspect
   most mailing lists will add a `From: ' header based on the envelope if
   you actually try.

These are the relevant headers from your mail;

>From ding-request@ifi.uio.no  Mon May  6 19:13:59 1996
Sender: abraham@dina.kvl.dk
From: Per Abrahamsen <abraham@dina.kvl.dk>

1) the list adds an appropriate "From " header.
2) your MUA or your MTA adds a "Sender: " header, in perfect
   conditions this should be done by the MTA.
3) your MUA adds a "From: " header--if missing, the MTA might do it.

An MUA should use option three first, then option two if three is
missing which is shouldn't be.

An MUA should NOT use the "From " header, just as it shouldn't use the
"Return-Path: " header. The "From " header isn't added by the MUA or
the MTA, it's actually added my the MDA. 

This isn't really relevant to this mailinglist, it should be fought
over on comp.mail.headers. IMHO, GNUS should NOT use a header which is
likly to return something you don't want to use, at least not without
querying the user first.

-- 
Bahnhof; http://www.bahnhof.se/      <pp@bahnhof.se> | a   difference   of
  (work) phone(voice/fax):      +46 18 100899/103737 | opinion is possible
 PFAWWW; http://pfawww.pp.se/pp/   <pp@pfawww.pp.se> | ^. .^     anum meum  
 (!work) phone(voice)    :             +46 18 247473 | ( @ )       aperies


  reply	other threads:[~1996-05-06 17:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-03 11:45 Kai Grossjohann
1996-05-03 18:31 ` Lars Magne Ingebrigtsen
1996-05-03 22:58   ` Sudish Joseph
1996-05-06  8:44     ` Kai Grossjohann
1996-05-06 11:12       ` Per Persson
1996-05-06 12:00         ` Per Abrahamsen
1996-05-06 12:12           ` Per Abrahamsen
1996-05-06 15:59           ` Per Persson
1996-05-06 16:01             ` Per Abrahamsen
1996-05-06 17:30               ` Per Persson [this message]
1996-05-06 17:45                 ` Per Abrahamsen
1996-05-06 20:12                   ` Per Persson
1996-05-07  5:38                     ` Per Abrahamsen
1996-05-06 17:46                 ` Stainless Steel Rat
1996-05-06 16:42             ` Stainless Steel Rat
1996-05-03 23:11   ` Sudish Joseph
1996-05-04  0:39     ` Sudish Joseph
1996-05-04  1:37     ` Per Abrahamsen
1996-05-05  0:10       ` Sudish Joseph
1996-05-05  7:59         ` Per Abrahamsen
1996-05-06 14:53           ` Sudish Joseph
1996-05-06 15:18             ` Per Abrahamsen
1996-05-06 17:33               ` Sudish Joseph
1996-05-06 17:53                 ` Per Abrahamsen
1996-05-05 12:33         ` Per Abrahamsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wx2pu2tn.fsf@pfawww.pp.se \
    --to=pp@pfawww.pp.se \
    --cc=ding@ifi.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).