Re: message splitting gone haywire

[Eric Abrahamsen <eric@ericabrahamsen.net>]

On Thu, Sep 29 2011, Ted Zlatanov wrote:

> On Thu, 18 Aug 2011 14:38:48 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> 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