From: Svend Tollak Munkejord <stm@bacchus.pvv.org>
Subject: Re: Why asterisks in nnmail-split-fancy rule?
Date: Fri, 30 May 2003 17:57:52 +0200 [thread overview]
Message-ID: <hdd8ysov33z.fsf@bacchus.pvv.ntnu.no> (raw)
In-Reply-To: <hddhe7cv3bq.fsf@bacchus.pvv.ntnu.no>
I wrote:
> Today, Kai Großjohann <kai.grossjohann@gmx.net> wrote:
>
>> Svend Tollak Munkejord <stm@bacchus.pvv.org> writes:
>>
>>> What is the difference, in nnmail-split-fancy, between
>>>
>>> (from "foo" "mail.foo")
>>>
>>> and
>>>
>>> (from ".*foo.*" "mail.foo") ?
>>
>> Fancy splitting implicitly adds \\<...\\> around the value. This
>> means that you can't use "xy@" as the value: because "@" is not a
>> word constituent, a word can never end there, so "xy@\\>" will never
>> match. That's why you have to use "xy@.*".
>
> OK, but I did not use any "@", only a surname string. I am puzzled,
> because the first rule (without .*) worked on a message from "Peter Foo",
> but not on a message from "Mike Foo", and by staring at the headers of
> those messages, I cannot figure out where this effect comes from.
And I forgot to say that the strange message also really needed the first
".*" in ".*foo.*".
--
Svend Tollak Munkejord
next prev parent reply other threads:[~2003-05-30 15:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hddk7c8vpwa.fsf@bacchus.pvv.ntnu.no>
[not found] ` <84znl46967.fsf@lucy.is.informatik.uni-duisburg.de>
2003-05-30 15:53 ` Svend Tollak Munkejord
2003-05-30 15:57 ` Svend Tollak Munkejord [this message]
[not found] ` <hddn0h4tni8.fsf@bacchus.pvv.ntnu.no>
2003-05-30 19:38 ` Kai Großjohann
2003-05-31 12:46 ` Svend Tollak Munkejord
[not found] ` <87ptm0edoa.fsf@mail.paradoxical.net>
2003-05-30 16:44 ` Kai Großjohann
[not found] ` <4nbrxk858v.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <84he7b2yk9.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <4nsmqv5nv8.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <84d6hzdw4u.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <4nof1i6duy.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <848yslraqf.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <u4r39li99.fsf@att.net>
[not found] ` <84he783oju.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <uadd0a6wx.fsf@att.net>
[not found] ` <84n0gzzo9b.fsf@lucy.is.informatik.uni-duisburg.de>
2003-06-04 0:07 ` Michael R. Wolf
[not found] ` <wc3vfvn9cr1.fsf@gamma.cis.ohio-state.edu>
2003-06-06 21:09 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=hdd8ysov33z.fsf@bacchus.pvv.ntnu.no \
--to=stm@bacchus.pvv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).