Ken Murchison [EMAIL PROTECTED] writes:
I suspect you're right, William. AFAICT this goes against the RFC however,
since you should only get regex when you use the :regex comparator.
Ken--is this a bug... a feature... a misdiagnosis...?
It appears to be a bug caused by using fnmatch(3)
Simon Josefsson wrote:
Ken Murchison [EMAIL PROTECTED] writes:
I suspect you're right, William. AFAICT this goes against the RFC however,
since you should only get regex when you use the :regex comparator.
Ken--is this a bug... a feature... a misdiagnosis...?
It appears to be a
Jeremy,
You've probably noticed this yourself, but I'm suspecting cyrus is treating
the [ and ] as standard regex grouping characters, which would explain the
number rejects. I don't really know anything about the Cyrus codebase, not
being a programmer, but I do know that sieve can support
William K. Hardeman wrote:
You've probably noticed this yourself, but I'm suspecting cyrus is
treating
the [ and ] as standard regex grouping characters, which would explain the
number rejects. I don't really know anything about the Cyrus codebase, not
being a programmer, but I do know that
Jeremy Howard wrote:
William K. Hardeman wrote:
You've probably noticed this yourself, but I'm suspecting cyrus is
treating
the [ and ] as standard regex grouping characters, which would explain the
number rejects. I don't really know anything about the Cyrus codebase, not
being a
One of my users has this script:
if anyof(
header :matches subject *[spam score 10.0/10.0 -pobox]*,
header :matches subject **) {
reject Message bounced by server content filter;
stop;
}
It is rejecting a lot of messages that do not match either test. When I
