From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80104 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: message splitting gone haywire Date: Thu, 29 Sep 2011 03:38:42 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <877h4rn3ot.fsf@lifelogs.com> References: <87ippv2phj.fsf@ericabrahamsen.net> Reply-To: ding@gnus.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1317285929 20109 80.91.229.12 (29 Sep 2011 08:45:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 29 Sep 2011 08:45:29 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28398@lists.math.uh.edu Thu Sep 29 10:45:26 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 1R9CFA-0003lM-Fm for ding-account@gmane.org; Thu, 29 Sep 2011 10:45:24 +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 1R9CF2-0005bi-PL; Thu, 29 Sep 2011 03:45:16 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1R9CF1-0005bV-JJ for ding@lists.math.uh.edu; Thu, 29 Sep 2011 03:45:15 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R9CEx-00068T-AY for ding@lists.math.uh.edu; Thu, 29 Sep 2011 03:45:15 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1R9CEv-0006qR-Ti for ding@gnus.org; Thu, 29 Sep 2011 10:45:09 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R9CEv-0003dK-Af for ding@gnus.org; Thu, 29 Sep 2011 10:45:09 +0200 Original-Received: from 38.98.147.133 ([38.98.147.133]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 10:45:09 +0200 Original-Received: from tzz by 38.98.147.133 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Sep 2011 10:45:09 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: ding@gnus.org Original-Lines: 27 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.133 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.90 (gnu/linux) Cancel-Lock: sha1:OT1OjQROA+LEagA2mOC8BE37rS4= X-Spam-Score: -4.2 (----) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80104 Archived-At: 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. Ted