Gnus development mailing list
 help / color / mirror / Atom feed
From: Shaun Lipscombe <shaun.lipscombe@gasops.co.uk>
Subject: Re: doubling addresses when following up
Date: 24 Nov 1999 16:50:59 +0000	[thread overview]
Message-ID: <wkso1vsuj0.fsf@gasops.co.uk> (raw)
In-Reply-To: Vladimir Volovich's message of "24 Nov 1999 10:32:20 +0300"

* "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



  reply	other threads:[~1999-11-24 16:50 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 [this message]
1999-11-24 18:13 ` Toby Speight
1999-11-30 19:48 ` Justin Sheehy

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=wkso1vsuj0.fsf@gasops.co.uk \
    --to=shaun.lipscombe@gasops.co.uk \
    /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).