* doubling addresses when following up @ 1999-11-24 7:32 Vladimir Volovich 1999-11-24 16:50 ` Shaun Lipscombe ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: Vladimir Volovich @ 1999-11-24 7:32 UTC (permalink / raw) Hi, suppose that some message has headers To: someone@domain.com Reply-To: SomeOne@domain.com 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. Best regards, -- Vladimir. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: doubling addresses when following up 1999-11-24 7:32 doubling addresses when following up Vladimir Volovich @ 1999-11-24 16:50 ` Shaun Lipscombe 1999-11-24 18:13 ` Toby Speight 1999-11-30 19:48 ` Justin Sheehy 2 siblings, 0 replies; 4+ messages in thread From: Shaun Lipscombe @ 1999-11-24 16:50 UTC (permalink / raw) * "Vladimir" == Vladimir Volovich <vvv@vvv.vsu.ru> writes: Vladimir> Hi, suppose that some message has headers To: Vladimir> someone@domain.com Reply-To: SomeOne@domain.com Vladimir> When i followup to this message, gnus puts both addresses Vladimir> (one to To:, and one to Cc:). But these addresses differ Vladimir> only by case. Do RFCs say that email addresses are Vladimir> case-insensitive? If so, then gnus should ignore duplicated Vladimir> emails which differ only by case. This is what a wide reply `S f' or just `f' does. ------------- C-h d gnus-summary-wide-reply RET gnus-summary-wide-reply is an interactive compiled Lisp function in `gnus-msg'. (gnus-summary-wide-reply &optional YANK) Start composing a wide reply mail to the current message. If prefix argument YANK is non-nil, the original article is yanked automatically. ------------- A wide reply will include all email addresses that where in the email you are replying to. If there is a reply-to, then this is included in the Cc: list even if its identical. It shouldn't be identical as it then serves no purpose, and that person will receive an extra copy because of this. HTH, Shaun -- (o_ (o_ (o_ //\ (/)_ (/)_ V_/_ shaun.lipscombe@gasops.co.uk ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: doubling addresses when following up 1999-11-24 7:32 doubling addresses when following up Vladimir Volovich 1999-11-24 16:50 ` Shaun Lipscombe @ 1999-11-24 18:13 ` Toby Speight 1999-11-30 19:48 ` Justin Sheehy 2 siblings, 0 replies; 4+ messages in thread From: Toby Speight @ 1999-11-24 18:13 UTC (permalink / raw) Vladimir> Vladimir V. Volovich <URL:mailto:vvv@vvv.vsu.ru> 0> In article <m34sece457.fsf@vvv.vsu.ru>, Vladimir wrote: Vladimir> suppose that some message has headers Vladimir> To: someone@domain.com Vladimir> Reply-To: SomeOne@domain.com Vladimir> Vladimir> When i followup to this message, gnus puts both addresses (one Vladimir> to To:, and one to Cc:). But these addresses differ only by Vladimir> case. Do RFCs say that email addresses are case-insensitive? The local-part of an address is case-sensitive as far as transmission is concerned (though the two addresses may be delivered to the same mailbox, a mail agent must assume they are as different as <some-one@example.com> and <some.one@example.com>). In a past life, I once used this for filtering mail based on which case variant it was addressed to (with case-insensitive delivery, and no "plussing" facility). The domain-name, though, is case-insensitive, so <some-one@example.com> and <some-one@Example.COM> refer to the same mailbox. The relevant RFC is RFC 822 <URL:http://www.ietf.org/rfc/rfc0822.txt>, which says: #> 3.4.7. CASE INDEPENDENCE #> #> Except as noted, alphabetic strings may be represented in any #> combination of upper and lower case. The only syntactic units #> which requires preservation of case information are: #> #> - text #> - qtext #> - dtext #> - ctext #> - quoted-pair #> - local-part, except "Postmaster" #> #> When matching any other syntactic unit, case is to be ignored. #> For example, the field-names "From", "FROM", "from", and even #> "FroM" are semantically equal and should all be treated ident- #> ically. #> #> When generating these units, any mix of upper and lower case #> alphabetic characters may be used. The case shown in this #> specification is suggested for message-creating processes. #> #> Note: The reserved local-part address unit, "Postmaster", is #> an exception. When the value "Postmaster" is being #> interpreted, it must be accepted in any mixture of #> case, including "POSTMASTER", and "postmaster". ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: doubling addresses when following up 1999-11-24 7:32 doubling addresses when following up Vladimir Volovich 1999-11-24 16:50 ` Shaun Lipscombe 1999-11-24 18:13 ` Toby Speight @ 1999-11-30 19:48 ` Justin Sheehy 2 siblings, 0 replies; 4+ messages in thread From: Justin Sheehy @ 1999-11-30 19:48 UTC (permalink / raw) 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1999-11-30 19:48 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 1999-11-24 7:32 doubling addresses when following up Vladimir Volovich 1999-11-24 16:50 ` Shaun Lipscombe 1999-11-24 18:13 ` Toby Speight 1999-11-30 19:48 ` Justin Sheehy
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).