Re: [Kolab-devel] Kolab3 and Sieve
Shawn Walker <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <00482d6d37.0001cec36e.000010f96b.0000000029__42580.5181767375$1381158200$gmane$org@bynari.net> |
Anybody on the development group have any idea to why Sieve on Kolab3 isn’t working as expected when using the managesieve to manage the filters on the server? Regards, Shawn From: [email protected] [mailto:[email protected]] On Behalf Of Shawn Walker Sent: Friday, October 04, 2013 3:50 PM To: '[email protected]' Subject: [Kolab-devel] Kolab3 and Sieve Hello, Our product allow the user to set their ‘out of office’ or ‘vacation’ message via Sieve. Kolab 3 is using port 4190 for Sieve. But it doesn’t seem to be 100% supported. When doing a LISTSCRIPTS it never returns a list of scripts that I can see under /var/lib/imap/sieve/domain/b/bynari.net/a/alice.walker. Even the script that our product uploaded to the server. Doing a “GETSCRIPT oof” returns nothing, just a “OK” response. Is there something that we need to do to enable full sieve server feature? When I use the same code with a different sieve server (non-kolab) our code work quite well. Just something about kolab 3 sieve was changed and I’m not sure what is going on. Regards, Shawn _______________________________________________ devel mailing list [email protected] https://lists.kolab.org/mailman/listinfo/devel