From: Justin Sheehy <dworkin@ccs.neu.edu>
Subject: Re: doubling addresses when following up
Date: 30 Nov 1999 14:48:24 -0500 [thread overview]
Message-ID: <vndn1rvzrp3.fsf@betelgeuse.ccs.neu.edu> (raw)
In-Reply-To: Vladimir Volovich's message of "24 Nov 1999 10:32:20 +0300"
Vladimir Volovich <vvv@vvv.vsu.ru> writes:
> To: someone@domain.com
> Reply-To: SomeOne@domain.com
Those are probably the same in reality, but could legally be different
addresses.
> When i followup to this message, gnus puts both addresses (one to To:,
> and one to Cc:). But these addresses differ only by case. Do RFCs say
> that email addresses are case-insensitive? If so, then gnus should
> ignore duplicated emails which differ only by case.
Gnus is acting correctly, as it cannot know that those are
equivalent. If they are equivalent, then the originator of the
message should not have put that Reply-To header in.
-Justin
prev parent reply other threads:[~1999-11-30 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 7:32 Vladimir Volovich
1999-11-24 16:50 ` Shaun Lipscombe
1999-11-24 18:13 ` Toby Speight
1999-11-30 19:48 ` Justin Sheehy [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=vndn1rvzrp3.fsf@betelgeuse.ccs.neu.edu \
--to=dworkin@ccs.neu.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).