From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Calling mrep with -from results in multiple from headers
Date: Sat, 23 May 2020 15:42:16 +0200 [thread overview]
Message-ID: <20200523134216.j0XG_2XD4esQC5ts1awRMcbshzQOQ6VfvR9mI_dFvsw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-176@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Closed issue by xelxebar on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/176
Description:
Admittedly, this is a strange thing to do, but as a workaround for while #173 is in the works, I have been calling mrep like this:
$ mrep -from "$(maddr -h from .)"
Which ends up creating two `From` headers, one with the value from the command above and another with the `local-mailbox` address. A few times I've slipped up and forgotten to delete the spurious `From` header, which usually ends up causing bounces.
Anyway, is this something worth fixing?
prev parent reply other threads:[~2020-05-23 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 1:53 [ISSUE] " xelxebar
2020-05-23 13:42 ` leahneukirchen [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=20200523134216.j0XG_2XD4esQC5ts1awRMcbshzQOQ6VfvR9mI_dFvsw@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).