Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: more test on the From: header
Date: 28 Mar 1999 17:26:41 +0200	[thread overview]
Message-ID: <m3n20xski6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Didier Verna's message of "19 Mar 1999 11:20:31 +0100"

Didier Verna <verna@inf.enst.fr> writes:

> 1/ From is in message-required-news-header.
>    When editing the message, I see a line with "Sender: verna@metheny.enst.fr"

Do you generate the headers before sending?

>         a/ the message is send as-is.
>            There, I get the expected From header.
> 
>         b/ I explicitely insert a From header.
>            There, the message can't be sent. I get an error of type "Duplicate 
>            From: header".

Well, if you only insert a From header, and there's already a From
header in the buffer, then you, er, have two from headers.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1999-03-28 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-19 10:20 Didier Verna
1999-03-28 15:26 ` Lars Magne Ingebrigtsen [this message]

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=m3n20xski6.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    /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).