unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <4uce.02.r.steib@gmx.net>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: bad rfc2047 encoding
Date: Wed, 21 Aug 2002 19:40:00 +0200	[thread overview]
Message-ID: <v965y4dsb3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <ilu7kiknntm.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 21 Aug 2002 19:06:45 +0200")

On Wed, Aug 21 2002, Simon Josefsson wrote:

> Dave Love <d.love@dl.ac.uk> writes:
[...]
>>> (I'm reading the gnus bugs list from quimby.gnus.org, which
>>> removes To/Cc so when I reply it only goes to the author and
>>> bugs@gnus.org.)
>>
>> That seems unfortunate.  People reporting bugs will potentially miss
>> discussion.
>
> It appears I was wrong, quimby.gnus.org does not alter headers, at
> least the last few messages CC bug-gnu-emacs properly, but the
> original submission did not.

Dave's first message had bug-gnu-emacs@gnu.org in the To-Header, not
in the Cc as the next ones. The posting script on quimby changes the
"To:" to "Original-To:":

| From: Dave Love <d.love@dl.ac.uk>
| Newsgroups: gnus.gnus-bug
| Cc: bugs@gnus.org
| Original-To: bug-gnu-emacs@gnu.org

The reason for this was ...

,----
| From: Lars Magne Ingebrigtsen <larsi@gnus.org>
| Subject: Re: gnus-summary-edit-article and wrapped From-line
| Newsgroups: gnus.ding
| Date: Sun, 30 Dec 2001 22:37:09 +0100
| Message-ID: <m3bsggjsoq.fsf@quimbies.gnus.org>
| Original-To: ding@gnus.org
| 
| Reiner Steib <reiner.steib@gmx.de> writes:
| 
| > BTW, the parent article <m37kr5ci6y.fsf@quimbies.gnus.org> is not
| > available on news.gnus.org:
| 
| Looking at the logs, it was rejected because I inserted a To header,
| leading to the article getting two To headers.  Would it be more
| reasonable if `C-c C-t' inserted a Cc header instead?
| 
| Anyway, I've now had the posting script rename To to Original-To.
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

  reply	other threads:[~2002-08-21 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 22:00 bad rfc2047 encoding Dave Love
     [not found] ` <ilu8z36li3m.fsf@latte.josefsson.org>
2002-08-20 17:02   ` Dave Love
2002-08-20 17:22     ` Simon Josefsson
2002-08-21 16:54       ` Dave Love
2002-08-21 17:06         ` Simon Josefsson
2002-08-21 17:40           ` Reiner Steib [this message]
2002-08-22 11:47           ` Dave Love
2002-08-22 17:48             ` Simon Josefsson
2002-08-30 18:08               ` Dave Love
     [not found]       ` <hvofbxtmpd.fsf@rasputin.ws.nextra.no>
2002-08-21 17:14         ` Simon Josefsson
2002-08-22 12:20           ` Dave Love
     [not found]           ` <rzq4rdncdta.fsf@albion.dl.ac.uk>
2002-08-22 13:50             ` Bjørn Mork
2002-08-30 17:59               ` Dave Love
2002-08-22 17:55             ` Simon Josefsson

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v965y4dsb3.fsf@marauder.physik.uni-ulm.de \
    --to=4uce.02.r.steib@gmx.net \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=reiner.steib@gmx.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).