Hello,
I would ask another little help. When I set this sieve script:
if true
{
addflag "\\Flagged";
keep;
}
I receive mails unflagged.
Other sieve rules work as expected.
If I want a working filter I have to set:
if true
{
addflag "\\Flagged";
fileinto "INBOX";
}
Coul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Hasenack wrote:
> On Tue, Mar 21, 2006 at 11:51:04PM +1030, Daniel O'Connor wrote:
>
>>On Tuesday 21 March 2006 23:00, Lars Schimmer wrote:
>>
>>>I use exim4 4.5 and cyrus 2.1.18-1 on a debian stable system with sieve
>>>scripts.
>>>But now 1
On Tuesday 21 March 2006 23:00, Lars Schimmer wrote:
> I use exim4 4.5 and cyrus 2.1.18-1 on a debian stable system with sieve
> scripts.
> But now 1 sievescript hit an error for a mail received by exim:
> Mar 19 20:56:55 europa cyrus/lmtpd[23422]: sieve runtime error for
> UseraBC id <[EMAIL PROTE
On Tue, Mar 21, 2006 at 11:51:04PM +1030, Daniel O'Connor wrote:
> On Tuesday 21 March 2006 23:00, Lars Schimmer wrote:
> > I use exim4 4.5 and cyrus 2.1.18-1 on a debian stable system with sieve
> > scripts.
> > But now 1 sievescript hit an error for a mail received by exim:
> > Mar 19 20:56:55 eu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I use exim4 4.5 and cyrus 2.1.18-1 on a debian stable system with sieve
scripts.
But now 1 sievescript hit an error for a mail received by exim:
Mar 19 20:56:55 europa cyrus/lmtpd[23422]: sieve runtime error for
UseraBC id <[EMAIL PROTECTED]>: Fil
I solved the problem ..!!!
The problem was not on cyrus, but on postfix configuration.
I see that in the message I have two Return-Path, the first address a
cyrus@hostname and the second is the real one.
With postfix I solved the problem using lmtp insteas that cyrus transport
I use this line
TECTED]>
> Cc: Ken Murchison <[EMAIL PROTECTED]>
> Subject: Re: Sieve error: unexpected operator
>
> You're running the wrong "test" command. You're running the standard
> Unix test command instead of the (badly named) Cyrus sieve test
> command.
You're running the wrong "test" command. You're running the standard
Unix test command instead of the (badly named) Cyrus sieve test
command.
Larry
Date: Tue, 20 Nov 2001 11:49:56 -0500 (EST)
From: Arley Carter <[EMAIL PROTECTED]>
cc: Ken Murchison <[EMAIL PROTECTED]>, Lawrence Greenfi
I have come across this error whilest trying to get sieve to run properly.
This is using FreeBsd 4.4, cyrus 2.0.16 and the timseived which is built
with this. Has anybody seen this before or can diagnose the problem? This
error will also appear when a non-existent script is fed to test as I did
b
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...?
> >
>
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 f
> It appears to be a bug caused by using fnmatch(3) to perform the match.
> fnmatch(3) performs glob-style matching, which treats '?', '*' AND '['
> as special -- see glob(7). The workaround is to escape the []:
>
> header :matches "subject" "*\\[spam score 10.0/10.0 -pobox\\]*"
>
> Feel free to
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
> >
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 tha
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 reg
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.
Hi everyone,
I am trying to get Sieve to work. I can
telnet to the Sieve port without a problem but when I run installsieve I get
prompted for a password and then I get this error:
Unable to connect to server at
/usr/local/bin/installsieve line 121, line 1.
I have not had a chance to
17 matches
Mail list logo
