From: Joseph Barillari <jbarilla@princeton.edu>
Subject: Re: Diagnosis of a nnmail-split-methods problem
Date: Sun, 24 Aug 2003 00:42:24 -0400 [thread overview]
Message-ID: <87d6ev64zz.fsf@bigbox.barillari.org> (raw)
In-Reply-To: <84r83c8mal.fsf@slowfox.is.informatik.uni-duisburg.de>
>>>>> "KG" == Kai Großjohann <kai.grossjohann@gmx.net> writes:
KG> One difference between the virus rule and the other rules is
KG> that the virus rule does NOT have a space (or tab?) after the
KG> colon.
KG> I would be surprised, but you never know...
I can insert a space and see what happens. The flood of viruses has
subsided, so I may not have much testing material. But the odd thing
about the problem was its intermittentcy. Sometimes it would split the
messages properly; other times, on messages with an identical
virus-flag header, it would dump them in the regular mail folder.
KG> Btw, I think the ".*" at the end are not needed. (".*" at the
KG> end might be useful for fancy splitting.) The string "xyzzy"
KG> matches the regexp "x" just like it matches the regexp "x.*".
Gotcha.
Thanks,
--Joe
--
Joseph Barillari -- http://barillari.org
prev parent reply other threads:[~2003-08-24 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 21:19 Joseph Barillari
2003-08-23 14:45 ` Kai Großjohann
2003-08-24 4:42 ` Joseph Barillari [this message]
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=87d6ev64zz.fsf@bigbox.barillari.org \
--to=jbarilla@princeton.edu \
/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).