Hello,
> enterin any of the listed commands except "logout" state the mentioned error
Entering commands in sieveshell for me does work:
$ sieveshell -u aaa -a aaa localhost
connecting to localhost
Please enter your password:
> list
a.siv <- active script
On telnet the commands are different, compared to sieveshell. E.g. the
CAPABILITY command does not require authentication. You are stating that all
commands except LOGOUT fail, but you do not spell the name of the commands
which you have sent, you are not sharing the complete session, which lead to
the error message.
You are also not stating that the clients I mentioned - with source code at
https://code.guido-berhoerster.org/projects/sievemgr/ and at
https://pypi.org/project/managesieve/ - also do not work with your server, so
probably they work. If it works with these clients, then raise your questions
in the EGroupware user groups. If it does not work with these clients, then
probably your Cyrus Sieve server (timsieved) is not configured correctly.
For the sake of testing you can also install an old version of Thunderbird and
try the plugin there. Please provide a list of ManageSieve clients, stating
for each one if it works or does not work, when it connects to your ManageSieve
server.
As I mentioned the probable reason why it stopped working with 3.12 was that
the unsolicited CAPABILITES response from Cyrus IMAP was aligned to the
behaviour specified in RFC 5804 and maybe the EGroupware/Horde/ManageSieve
libraries do not reflect this change.
At your place I would read RFC 5804, add some debugging commands in EGroupware,
log what is sent to the server in the ManageSieve protocol, what is returned
from the server, and then check who is right according to RFC 58044 - the
client of the server.
You could also patch Cyrus IMAP/timsieved to log the same information, but it
would be easier to do this in Egroupware, as EGroupware is written in PHP and
does not require recompiling, installing development dependencies, linking, etc.
If it is mandatory to get EGroupware to work you might want to look for paid
support.
I personally do not use Cyrus IMAP 3.12. I use Cyrus IMAP 3.8+ and for me it
works. 3.12 might indeed have introduced some errors and these errors are not
yet narrowed down. Your current report is “something in Cyrus 3.12
ManageSieve/timsieved does not seem right”. Maybe, but this is not precise
enough, as you do not share log of the managesieve session.
Greetings // Дилян
-----Original Message-----
From: Dr. Thorsten Brandau via Info <[email protected]>
Reply-To: Info <[email protected]>
To: [email protected]
Subject: Re: Sieve/Vacation
Date: 25/08/25 09:52:34
Hello,
as mentioned in my message, sieveshell works. Managesieve also after
upgrading to 3.12 (according to the "testing sieve" procedure in cyrus
3.12 online). The problem with managesieve was a bit in the repository
of 3.10, and a subsequent problem with updating to 3.12 under manjaro
from AUR. So as mentioned, SIEVE seems to work, however enterin any of
the listed commands except "logout" state the mentioned error:
As I wrote:
>It means, that it seems as sieve itselv is somehow working.
Now, for me it is mandatory to get egroupware to work. None of the
plugins you mentioned for thunderbird (vacation etc.) work with the
current thunderbird version. A github/gitlab repository that seems to
have documentation in cyrillic only will not be installed in our IT.
The access from egroupware is done via horde. This works well with Cyrus
2.4/2.6 but stops working with 3.12. From what I understand there was no
change in specification during the time cyrus as updated from 2.6 to
3.12 so the assumption that the implementation of cyrus is done
differently is likely.
Therefore *my request was to get a better debugging to understand what
the error is and resolve the issue*.
>If the ManageSieve server is implemented in Cyrus IMAP correctly, and
you do not not describe a reproducible report demonstrating the
opposite, then switching to Dovecot will provide you just with a
different correctly running ManageSieve server. You might also want to
look for support for your system.
That is excatly the problem. Egroupware runs fine with dovecot, cyrus
2.4 and cyrus 2.6 (same as our previous groupware). However, not at all
with cyrus 3.12.
In my understanding that points straight to the sieve implementation of
cyrus 3.12.
Regards
T
Дилян Палаузов schrieb am 24.08.25 um 12:44:
> Hello,
>
> I advised you at
> https://cyrus.topicbox.com/groups/info/Ta4efc40124588ec6-M5e38763f6e2dfa21dddbf1f0/sieve-vacation
> to try a different ManageSieve client and I gave you a list of possible
> ManageSieve clients. You have not stated, that these clients do not work.
> So again, just try with several ManageSieve clients to read/writes Sieve
> scripts on the server. If it works, then the server is setup correctly.
>
> You said that you cannot get sieveshell running with Cyrus IMAP 3.10, but
> then you upgraded to Cyrus IMAP 3.12 . You are not stating, that sieveshell
> fails with Cyrus IMAP 3.12.
>
> You try to use telnet, but you are not stating that the server deviates from
> RFC 5804 (A Protocol for Remotely Managing Sieve Scripts). If you get an
> error with telnet, then maybe you do not follow the protocol?
>
> When it comes to the ManageSieve protocol, it first originated in Cyrus IMAP
> and then was standardized over IETF. This lead to a difference whether to
> send the output of unsolicited CAPABILITY command after
> authentication/security layer upgrade. Cyrus IMAP had a toggle to switch
> between its original behaviour and the RFC 5804 behaviour, which toggle was
> removed by https://github.com/cyrusimap/cyrus-imapd/pull/3346/ . This is
> mentioned also at
> https://www.cyrusimap.org/dev/imap/download/release-notes/3.12/x/3.12.0.html
> under Removed features.
>
> If the ManageSieve server is implemented in Cyrus IMAP correctly, and you do
> not not describe a reproducible report demonstrating the opposite, then
> switching to Dovecot will provide you just with a different correctly running
> ManageSieve server. You might also want to look for support for your system.
>
> Greetings // Dilyan
>
> -----Original Message-----
> From: Dr. Thorsten Brandau via Info <[email protected]>
> Reply-To: Info <[email protected]>
> To: [email protected]
> Subject: Re: Sieve/Vacation
> Date: 24/08/25 12:45:24
>
> Hi,
>
> so, I was able to upgrade to cyrus 3.12 as the 3.10 package was broken
> in the AUR.
>
> telnet sieve works well. However, anything except "logout" that is
> entered is replied with "was expecting command, got something else".
> This is unfortunately as far as the cyrus documentation under "testing
> sieve" goes.
>
> It means, that it seems as sieve itselv is somehow working.
>
> When I try to get this to work with egroupware, egroupware connects to
> sieve but issues the same "expecting command, got something else".
>
> egroupware is using horde for the connection to sieve.
>
> I am at a point that it seems that cyrus 2.6 and 3.12 use different (?)
> settings for sieve - it worked perfectly with 2.4/2.6 before. However,
> for various reasons I cannot downgrade.
>
> Is it possible to have cyrus 3.12 simulate ht 2.6 sieve behaviour?
>
> There are no plugins for any mail program as it seems anymore to manage
> vacation scripts. All groupware solutions I find (including both we
> selected for our company - group-e from endo7 to be faded out and
> egroupware as the current version) do not work with cyrus 3.12 on the
> sieve level. Egroupware at last works with subfolders on cyrus 3.12.
>
> If there is no solution we unfortunately have to move away from cyrus,
> which seems ot lack substantially in support and will have to switch to
> dovecot, which we avoided the last 20 years very successfully....
>
> Any help? Any ideas? Any possibilities to isolate the problem? Currently
> everywhere I ask I get rerouted to the other one side (cyrus -> its your
> groupware , groupware -> go check horde/cyrus, horde -> who are you? )
>
> Cheers
>
> T
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/Ta4efc40124588ec6-M31632d2aa6e5f1aaa9903d40
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
