split rule debugging

split rule debugging

[Norbert Koch]

Hi!

I use fancy mail splitting, and I've got an error in my split rules.
Thus, too many messages are placed into the bogus group.

Is there a way to debug the split rules?  Some output of the various
splits or something?

Thanks,
norbert.

Re: split rule debugging

[Steve Youngs]

[-- Attachment #1: Type: text/plain, Size: 981 bytes --]

* Norbert Koch <viteno@xemacs.org> writes:

  > Hi!
  > I use fancy mail splitting, and I've got an error in my split rules.
  > Thus, too many messages are placed into the bogus group.

  > Is there a way to debug the split rules?  Some output of the various
  > splits or something?

This probably isn't all that elegant, but I do it like so...

Go into that bogus group and do `B t' on a message that should have
gone somewhere else.

At this stage it'll say "bogus".  Just leave the message there.  Now
alter your split rule, re-eval it, come back to the summary buffer and
do `B t' again.

Repeat until you get it right.

Once all is right with your splits, mark all the messages in bogus
that shouldn't be there and do `B r'.

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|                   Te audire no possum.                   |
|             Musa sapientum fixa est in aure.             |
|----------------------------------<steve@youngs.au.com>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

Re: split rule debugging

[Norbert Koch]

Steve Youngs <steve@youngs.au.com> writes:

> This probably isn't all that elegant, but I do it like so...
> 
> Go into that bogus group and do `B t' on a message that should have
> gone somewhere else.

That's been good enough, it showed me the culprit right away.

Thanks,
norbert.