From: "Matt Armstrong" <matt+dated+1007493714.64bd31@lickey.com>
Subject: Re: [PATCH] Bug fix for mail-followup-to
Date: Sun, 04 Nov 2001 12:21:52 -0700 [thread overview]
Message-ID: <871yjeibov.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <2nady2wqqb.fsf@zsh.cs.rochester.edu> (ShengHuo ZHU's message of "Sun, 04 Nov 2001 09:33:16 -0500")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> "Matt Armstrong" <matt+dated+1007413744.f977c8@lickey.com> writes:
>
>> If you trace through message-send-mail, you'll see that the second
>> call to message-generate-headers -- the one that adds the
>> Mail-Followup-To: header -- erases the previously generated Date:,
>> Message-Id: and Lines: headers. This is bad because only the Lines:
>> header gets subsequently generated, so the Message-Id: and Date:
>> headers must be inserted by the MTA (sendmail, etc.).
>
> Thanks. I fix it in another way, calling message-generate-headers
> once.
A better fix, and it works too! ;-)
--
matt
prev parent reply other threads:[~2001-11-04 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-03 21:09 Matt Armstrong
2001-11-04 14:33 ` ShengHuo ZHU
2001-11-04 19:21 ` Matt Armstrong [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=871yjeibov.fsf@squeaker.lickey.com \
--to=matt+dated+1007493714.64bd31@lickey.com \
/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).