From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: checking several headers when splitting mail
Date: Tue, 28 Jun 2011 21:16:08 +0200 [thread overview]
Message-ID: <8739it4vif.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <m2hb79q1dp.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> lee <lee@yun.yagibdah.de> writes:
>
>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>
>>> lee <lee@yun.yagibdah.de> writes:
>>>
>>>> Andreas Schwab <schwab@linux-m68k.org> writes:
>>>>
>>>>> (from "root@yun\\.yagibdah\\.de"
>>>>> ("Subject" "/var/log/.*"
>>>>> "mail.sys.yun"))
>>>>
>>>> This doesn't work.
>>>
>>> In which way does it not work?
>>
>> It doesn't seem to have any effects. I expected it to yield an error
>> message, and to my surprise it didn't. When I press B q on a message
>> that supposedly would match, like
>>
>> ,----
>> | From: root <root@yun.yagibdah.de>
>> | Subject: /var/log/exim4/rejectlog
>> `----
>>
>> ... gnus says it'll go to mail.0-incoming.
>
> That's because "\\</var/log/.*" doesn't match "/var/log/exim4/rejectlog".
Huh?
(from "root@yun\\.yagibdah\\.de" ("Subject" "var/log/.*" "mail.sys.yun"))
... seems to work, thanks :)
Why does "var/log/.*" match "/var/log/exim4/rejectlog" and "/var/log/.*"
does not? How is one supposed to figure out what matches what when this
is so weird?
>> A group name like "mail.sys.yun" is not a structure, so that cannot be
>> a SPLIT.
>
> The format of this variable is SPLIT, where SPLIT can be one of
> the following:
>
> GROUP: Mail will be stored in GROUP (a string).
Hm. Even if the documentation would just say so, it's still hard to
understand. Perhaps I can make a suggestion about how to improve it
once I understand it better.
next prev parent reply other threads:[~2011-06-28 19:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 19:46 lee
2011-06-15 19:53 ` Tassilo Horn
2011-06-15 20:42 ` Andreas Schwab
2011-06-28 16:04 ` Ted Zlatanov
2011-06-28 18:04 ` Andreas Schwab
2011-06-28 19:01 ` Ted Zlatanov
2011-06-28 21:21 ` lee
2011-06-28 23:22 ` lee
2011-06-15 21:16 ` lee
2011-06-26 9:31 ` Lars Magne Ingebrigtsen
2011-06-26 19:00 ` lee
2011-06-26 19:26 ` Andreas Schwab
2011-06-27 0:53 ` lee
2011-06-27 22:40 ` Andreas Schwab
2011-06-28 1:00 ` lee
2011-06-28 18:03 ` Andreas Schwab
2011-06-28 19:16 ` lee [this message]
2011-06-26 19:37 ` Lars Magne Ingebrigtsen
2011-06-27 1:49 ` lee
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=8739it4vif.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--cc=ding@gnus.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).