Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-pretest-bug@gnu.org, Ding List <ding@gnus.org>
Subject: Re: Gnus mangles one of my group names
Date: Tue, 12 Oct 2004 16:43:17 +0200	[thread overview]
Message-ID: <v9r7o4ro8q.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <q5gis9gyrpp.fsf@lucent.com> (Klaus Zeitler's message of "Tue, 12 Oct 2004 15:46:26 +0200")

[ I'll CC the Gnus list.  Please keep the CC intact when replying.
  (Maybe we can even drop emacs-pretest-bug?) ]

On Tue, Oct 12 2004, Klaus Zeitler wrote:

> All of a sudden (since about 2 weeks) one of my nnml groups (called bridge)
> gets mangled every time a new mail arrives.
>
> When I receive a mail, that Gnus is supposed to distribute to this group,
> Gnus instead creates a new group with the odd name "bridge?bridge".
> I think there's some ascii character, maybe C-j, between the duplicated group
> names.
> The active file then additionally contains a new entry:
> --- snip ---
> bridge\
> bridge 1 1 y
> --- snip ---
>
> an ls in ~/Mail shows something similar as new group name:
> bridge?bridge

What is the output of "ls -b"?

> The old group remains unaffected. Everything's still there and the entry in
> active file is also ok.
>
> I noticed this the first time right after Gnus in CVS emacs got updated. I
> haven't changed anything in my gnus configuration for months.
>
> Does anybody have an idea?

Could you show us your mail splitting setup (or the relevant parts of
it)?

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

       reply	other threads:[~2004-10-12 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <q5gis9gyrpp.fsf@lucent.com>
2004-10-12 14:43 ` Reiner Steib [this message]
2004-10-13  6:48   ` Klaus Zeitler

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=v9r7o4ro8q.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-pretest-bug@gnu.org \
    /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).