From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80106 Path: news.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: message splitting gone haywire Date: Thu, 29 Sep 2011 17:00:16 +0800 Message-ID: <871uuziuzj.fsf@ericabrahamsen.net> References: <87ippv2phj.fsf@ericabrahamsen.net> <877h4rn3ot.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317286846 26362 80.91.229.12 (29 Sep 2011 09:00:46 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 09:00:46 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28400@lists.math.uh.edu Thu Sep 29 11:00:42 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R9CTx-0002eA-Nh for ding-account@gmane.org; Thu, 29 Sep 2011 11:00:42 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1R9CTs-0005jg-Ii; Thu, 29 Sep 2011 04:00:36 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1R9CTr-0005jS-6U for ding@lists.math.uh.edu; Thu, 29 Sep 2011 04:00:35 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R9CTn-00088j-1X for ding@lists.math.uh.edu; Thu, 29 Sep 2011 04:00:35 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R9CTl-0007C0-MC for ding@gnus.org; Thu, 29 Sep 2011 11:00:29 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9CTl-0002bS-Ar for ding@gnus.org; Thu, 29 Sep 2011 11:00:29 +0200 Original-Received: from 123.115.182.192 ([123.115.182.192]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 11:00:29 +0200 Original-Received: from eric by 123.115.182.192 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 11:00:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 51 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 123.115.182.192 User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/23.2 (gnu/linux) Cancel-Lock: sha1:k8uAaNvN4J5O9K996gzq3sIeudo= X-Spam-Score: -4.2 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80106 Archived-At: On Thu, Sep 29 2011, Ted Zlatanov wrote: > On Thu, 18 Aug 2011 14:38:48 +0800 Eric Abrahamsen wrote: > > EA> I've been keeping up to date with git gnus (I'm on Ubuntu's 23.2 emacs), > EA> and a week or so ago, message splitting started going haywire. There's > EA> not much of a discernible pattern: messages are just going in the wrong > EA> groups. > > EA> I'm using the registry, with gnus-registry-split-fancy-with-parent. Also > EA> BBDB 3.0, with bbdb/gnus-split method. Then some plain old > EA> nnmail-split-fancy regexps. None of these seems obviously the culprit. > EA> Some messages that should be split into their own groups by > EA> nnmail-split-fancy go into those groups half the time, into mail.misc > EA> the other half (they used to all go into the proper group, they're > EA> automated messages and neither the message nor the regexp has changed). > EA> A message I just sent from one of my email addresses to another of my > EA> email addresses went into a group that's only referenced by a > EA> gnus.private line in a BBDB record (not my own record, needless to say). > > EA> Like I said, no one thing seems to be the clear source of the problem. > EA> Has anyone else seen anything like this over the past few weeks? I can > EA> paste the relevant part of my config, if necessary. > > I didn't touch the registry around the time you mention. But I would > simply bisect the issue by limiting splitting to one method at a time > and see if it causes the aberrant behavior. Eventually I figured out what was happening -- in the case of a few regular email threads (newsletters in particular), one earlier issue had gone into the wrong group, and all subsequent issues went into the same group. Standard registry behavior, but I had physically moved later issues into the proper group, and new issues were still getting split into the wrong group. Eventually I realized that the originally offending message was still buried back in the wrong group, and once I rooted out all of them, things went back to normal. This happened with two or three separate threads (not sure how), creating the impression that all hell had broken loose with splitting. I'm not sure what proper behavior should be, but I did expect that split-with-parent would send new messages to the location of the newest/nearest parent, and not to where some distant ancestor had once gone. Thanks! Eric -- GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on rothera, modified by DebiannNo Gnus v0.18