From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: minor patch against message.el
Date: Tue, 12 Mar 2002 16:40:12 -0500 [thread overview]
Message-ID: <m3bsdtqxbh.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <ilulmcxwk1m.fsf@extundo.com> (Simon Josefsson's message of "Tue, 12 Mar 2002 22:30:45 +0100")
Simon Josefsson <jas@extundo.com> wrote:
> fn@hungry.org (Faried Nawaz) writes:
>> I'd like to set my sender header to whatever my from header is.
>> I use qmail, so I needed this patch (against Oort 0.04):
>
> Committed, thanks.
I guess my response to Faried accidentally went off-list. This patch
is actually not necessary for the desired functionality. (If there is
a Return-Path field, qmail-inject will set the envelope sender
according to it and delete it. Return-Path can be set via posting
styles, etc.) Maybe this patch is useful for somebody else anyway,
though.
paul
next prev parent reply other threads:[~2002-03-12 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 19:59 Faried Nawaz
2002-03-12 21:30 ` Simon Josefsson
2002-03-12 21:40 ` Paul Jarc [this message]
2002-03-14 0:21 ` Chris Green
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=m3bsdtqxbh.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).