Hello,
Oh, didn't change waldinet.local to my.local
I found out why I had problems, the 2nd worked, the first not ...
in
/var/lib/imap/sieve
there I had 2 folders:
global and w/walter
and both contained a sieve script, the one under w/walter was older and
didn't handle the 2nd mail, and I guess
Is it the second email sample that does not work? If so the To: on that
one is walter@waldinet.local and I don't see any rules for
walter@waldinet.local. Also, where does the mail that doesn't work end up?
On 04/04/2017 03:00 AM, Walter H. via Info-cyrus wrote:
Hello,
I've found a Sieve Test
On Tue, April 4, 2017 08:42, ellie timoney wrote:
>> Received: from storage.mail ([unix socket])
>> by storage.mail (Cyrus v2.3.16-Fedora-RPM-2.3.16-13.el6_6) with
>> LMTPA;
>> Mon, 03 Apr 2017 21:27:35 +0200
>> X-Sieve: CMU Sieve 2.3
>
> Wild guess, is your script using sieve featur
> Received: from storage.mail ([unix socket])
> by storage.mail (Cyrus v2.3.16-Fedora-RPM-2.3.16-13.el6_6) with
> LMTPA;
> Mon, 03 Apr 2017 21:27:35 +0200
> X-Sieve: CMU Sieve 2.3
Wild guess, is your script using sieve features that are not available
in 2.3.16? 2.3.16 was released
Hello,
I've found a Sieve Tester, where everything works as I expect
https://www.fastmail.com/cgi-bin/sievetest.pl
but Cyrus Sieve doesn't
here the Sieve-Script
# Sieve filter
require ["fileinto", "relational"];
if not exists ["from"]
{
discard;
}
elsif allof (address :all :is "from
Replaced the timsieved/parser.c file in the imap 2.1.11 tarball with
the updated one from CVS and re-compiled the software, and guess what ?
the "strange sieve problem" are no longer a strange problem :-)
Thanks Chris, for your investigation
Rob Siemborski wrote:
This is fixed in CVS, so if you wait a day or so, 2.1.12 will be out and
you can use that (or you can just use CVS).
-Rob
Darn, and I just finished a patch ;-) Good to hear about 2.1.12. I'll
patch locally and then upgrade when it is out.
Thanks for the good software!
This is fixed in CVS, so if you wait a day or so, 2.1.12 will be out and
you can use that (or you can just use CVS).
-Rob
On Sun, 2 Feb 2003, Chris Scott wrote:
> Chris Scott wrote:
>
>
>
> >
> >
> > Does anyone have suggestions for what to look at next?
> >
>
> Sorry for replying to myself but
Chris Scott wrote:
Does anyone have suggestions for what to look at next?
Sorry for replying to myself but I have more info. on this. The server
I have where sieve is working is version is v1.1.0 (compiled from imap
2.1.5) and the latest where it is not working is v2.1.11. The followin
Chris Scott wrote:
Bryntez wrote:
>Hi list..
>I have trouble connecting to sieve. Everything else works fine.
>I'm using RedHat 7.3. I've tried Simons rpms also, but the same error
>occures. I'm using Cyrus Sasl 2.1.11 and Cyrus Imap 2.1.11.
>The system is a "web-cyradm" based config with My
quot;Chris Scott" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, February 01, 2003 9:53 PM
Subject: Re: Strange sieve problem
: Bryntez wrote:
:
: >Hi list..
: >I have trouble connecting to sieve. Everything else works fine.
: >I'm using RedHat 7.3.
Bryntez wrote:
>Hi list..
>I have trouble connecting to sieve. Everything else works fine.
>I'm using RedHat 7.3. I've tried Simons rpms also, but the same error
>occures. I'm using Cyrus Sasl 2.1.11 and Cyrus Imap 2.1.11.
>The system is a "web-cyradm" based config with MySQL and Postfix.
>
I'm us
Hi list..
I have trouble connecting to sieve. Everything else works fine.
I'm using RedHat 7.3. I've tried Simons rpms also, but the same error
occures. I'm using Cyrus Sasl 2.1.11 and Cyrus Imap 2.1.11.
The system is a "web-cyradm" based config with MySQL and Postfix.
saslauthd -a pam& are workin
13 matches
Mail list logo
