From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Reply calculation
Date: Sat, 25 Jul 2009 14:10:54 -0400 [thread overview]
Message-ID: <1248545266-sup-6886@javelin> (raw)
I think sup's "To" address calculation algorithm is wrong, and
messes up in some important edge-cases. The two edge
cases I have in mind are:
* When a mailing list sends an unsubscribe/subscribe notification
* When someone posts to a mailing list with an explicit Reply-to
header.
In both of these cases, the mail will commonly have an explicit
Reply-to header. However, Sup will by default disregard this
header in favor for List-id, which is *wrong*.
You can guess, this has bitten me several times.
I think the correct behavior is to only use List-id when Reply-to
is not explicitly set, since List-id is "magical" whereas Reply-to
is commonly explicit.
Cheers,
Edward
next reply other threads:[~2009-07-25 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 18:10 Edward Z. Yang [this message]
2009-07-25 18:24 ` Edward Z. Yang
2009-07-25 19:03 ` Edward Z. Yang
2009-07-25 19:15 ` Edward Z. Yang
2009-07-27 16:49 ` William Morgan
2009-07-27 17:09 ` Edward Z. Yang
2009-07-28 15:48 ` William Morgan
2009-07-28 18:34 ` Edward Z. Yang
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=1248545266-sup-6886@javelin \
--to=ezyang@mit.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