Re: What Headers Are Checked With split-fancy 'any'

[Reiner Steib <4.uce.03.r.s@nurfuerspam.de>]

On Wed, Oct 29 2003, Jake Colman wrote:

> This will match spamassassin-talk and spamassassin-announce whether it is
> followed by lists.sourceforge.net or sourceforge.net.  The construct
> "\\(lists\\.\\)?" says zero or more "lists." preceded by "@" and followed by
> the rest of it.

Yup.

> Does the match always start with the first character 

No.

> or do I have to use "^" if I am concerned about something preceding
> it?

It depends.  If the address is written as
| To: Spamassassin Talk <spamassassin-talk@sourceforge.net>
or
| To: <spamassassin-talk@sourceforge.net>
it will not match.

Also note ...

,----[ (info "(gnus)Fancy Mail Splitting") ]
|    In these splits, FIELD must match a complete field name.  VALUE must
| match a complete word according to the fundamental mode syntax table.
| You can use `.*' in the regexps to match partial field names or words.
| In other words, all VALUE's are wrapped in `\<' and `\>' pairs.
`----

... and the variable `nnmail-split-fancy-match-partial-words':

,----[ C-h v nnmail-split-fancy-match-partial-words RET ]
| nnmail-split-fancy-match-partial-words's value is nil
| 
| Documentation:
| Whether to match partial words when fancy splitting.
| Normally, regexes given in `nnmail-split-fancy' are implicitly surrounded
| by "\<...\>".  If this variable is true, they are not implicitly surrounded
| by anything.
| 
| You can customize this variable.
| 
| Defined in `nnmail'.
`----

You can check your split rules by doing `B q', `B t' and `B r', see
(info "(gnus)Mail Group Commands") for more explanations.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/