fancy mail splitting

fancy mail splitting

[Adam Sjøgren]

  Hi,


I usually create my fancy mail splitting rules by trial and error -
Emacs' regexps are kind of toothpicky when you are used to Perl...

Here is my problem:

I want to have emails with Subject starting with "[git/adm]" to go to
one group, but emails with the Subject starting with "Re: [git/adm]" to
another.

To match "[git/adm]" I can only get this to work:

        ("Subject" ".*\\[git/adm\\].*" "commits.adm")

If I remove either ".*", it doesn't match them.

I can't figure out how to make this _not_ match Subjects prefixed with
"Re: " (or anything else, for that matter).

I tried tacking on "nil nil" and "nil t" to the rule as well, without
hitting the jackpot. I am lost.

Any ideas?


  Thanks!

   Adam

-- 
 "How different? It seems like you are just biased in         Adam Sjøgren
  favour of your own style."                             asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: fancy mail splitting

[B.V. Raghav]

Hi,

asjo@koldfront.dk (Adam Sjøgren) writes:

>   Hi,
>
>
> I usually create my fancy mail splitting rules by trial and error -
> Emacs' regexps are kind of toothpicky when you are used to Perl...
>
> Here is my problem:
>
> I want to have emails with Subject starting with "[git/adm]" to go to
> one group, but emails with the Subject starting with "Re: [git/adm]" to
> another.
>
> To match "[git/adm]" I can only get this to work:
>
>         ("Subject" ".*\\[git/adm\\].*" "commits.adm")
          How about trying "^\\[git/adm\\].*" vs "^Re: \\[git/adm\\].*"
          I have myself not tried it. But I think the regexp should work!

>
> If I remove either ".*", it doesn't match them.
>
> I can't figure out how to make this _not_ match Subjects prefixed with
> "Re: " (or anything else, for that matter).
>
> I tried tacking on "nil nil" and "nil t" to the rule as well, without
> hitting the jackpot. I am lost.
>
> Any ideas?
>
>
>   Thanks!
>
>    Adam

-- 
(B.V. Raghav)

Re: fancy mail splitting

[Adam Sjøgren]

B.V. writes:

>           How about trying "^\\[git/adm\\].*" vs "^Re: \\[git/adm\\].*"
>           I have myself not tried it. But I think the regexp should work!

Adding the ^ doesn't work, but your suggestion gave me the idea of
having something that matches "Re: [git/adm]" first, and then the usual
rule after. That works. Although it feels a little kludgey.


   Thanks,

    Adam

-- 
 "What do you do for a living, man?"                          Adam Sjøgren
 "Oh, I confound expectations."                          asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: fancy mail splitting

[Adam Sjøgren]

Adam writes:

> Adding the ^ doesn't work, but your suggestion gave me the idea of
> having something that matches "Re: [git/adm]" first, and then the usual
> rule after. That works. Although it feels a little kludgey.

I found an entry in my fancy splitting rules that I had forgotten all
about. This works:

        ("Subject" ".*\\[git/adm\\].*" - ".*Re: .*" "commits.adm")


  Best regards,

    Adam

-- 
 "So this is what being a morning person is like, I           Adam Sjøgren
  thought. It's like being 80 years old."                asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: fancy mail splitting

[Cor]

Some entity, AKA asjo@koldfront.dk (Adam Sjøgren),
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)

> B.V. writes:
>
>>           How about trying "^\\[git/adm\\].*" vs "^Re: \\[git/adm\\].*"
>>           I have myself not tried it. But I think the regexp should work!
>
> Adding the ^ doesn't work, but your suggestion gave me the idea of
> having something that matches "Re: [git/adm]" first, and then the usual
> rule after. That works. Although it feels a little kludgey.

It the way the mail-splitting works, sequential and when it hits on the first
matchting reg-expr it drops the message in the box and then goes to the
next incoming message. 
Sometimes it really looks like doing magic to get the filtering the way
you want.

Cor

-- 
Geavanceerde politieke correctheid is niet te onderscheiden van sarcasme
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: fancy mail splitting

[Kai Großjohann]

Poster 2000 <p_oster_2000@yahoo.com.invalid> writes:

> (any "mypackage@somewhere\" - "bugs-mypackage" "mypkg.list")

The backslash looks bogus.
-- 
A preposition is not a good thing to end a sentence with.

Re: fancy mail splitting

[Kai Großjohann]

Poster 2000 <p_oster_2000@yahoo.com.invalid> writes:

>>>>>> On Thu, 27 Feb 2003 14:50:45 +0100
>>>>>> In Message <84znohltmy.fsf@lucy.is.informatik.uni-duisburg.de>
>>>>>> which is being read from gnu.emacs.gnus
>>>>>> kai.grossjohann@uni-duisburg.de (Kai Großjohann) Said 
>
>> Poster 2000 <p_oster_2000@yahoo.com.invalid> writes:
>>
>>> (any "mypackage@somewhere\" - "bugs-mypackage" "mypkg.list")
>>
>> The backslash looks bogus.
>
> Taking it as meaning an optional restrict then.

What's that?

Hm.

Oh!

You are referring to the fact that restricts are listed as "optional"
in the documentation of nnmail-split-fancy.

I thought you meant that the restrict was allowed to optionally be
not fulfilled.  That's weird :-)

I think it should be

(any "mypackage@somewhere" - "bugs-mypackage" "mypkg.list")

without that backslash.

> I've just been converting my normal split lists to fancy
> format. Since I keep getting error when running
> gnus-summary-respool-trace, I've tried creating the simplest possible
> split.
>
> Everything to a single group.
>
> (setq nnmail-split-fancy "mail.in.misc" )
> The format of split-fancy is a split and the first type of split
> mentioned is a string where this is the name of a group
>
> wrong type argument listp "mail.in.misc"

This appears to be a bug in Gnus.  The documentation of
nnmail-split-fancy clearly says that this is an allowed value.  Can
you provide a backtrace?  M-x toggle-debug-on-error RET, then repeat
the problem.  Then post that backtrace.

> so I try
> (setq nnmail-split-fancy '("mail.in.misc") )
>
> again wrong type argument listp.

Maybe this is really wrong syntax, so the error message is okay.
Let's start with the simple case first, see above.

> Likewise when I extend it to the full version for full filtering,
> which is of the form.
>
> (setq nnmail-split-fancy '
>       (| ( "Subject" "Mail Filter Log$" "mail.in.filters")
> 	 ( "X-RBL-Warning" "Blocked.*$" "mail.in.spam" )
> 	 <snipped various other splits of the same type>
>          ( "\\(To:\\|Cc:\\)" "someone@somewhere\\.com" "mail.in.someone")
> 	 "mail.in.misc")) 
>
> This as far as I can tell is of the general format described in the
> manual.

That's right.  It looks good.

> But gnus-summary-respool-trace fails as before.

I'm afraid I lost the "as before" part.  Can you show it again, in
what way does it fail?

> Have I got the format of nnmail-split-fancy wrong, or is there a
> problem in this version of oort. 
>
> (gnus-version)"Oort Gnus v0.05"

I'd always advise to upgrade -- using Oort means to live on the
bleeding edge, and living on the old bleeding edge gives you all the
disadvantages of the bleeding edge combined with the problems of old
versions ;-)

-- 
A preposition is not a good thing to end a sentence with.