hello Sorry for the late response.
Am 02.12.2016 um 13:39 schrieb Patrick Ben Koetter ([email protected]): > Greetings, > > we're trying to edit and store Sieve rules using SOGo 3.2.1 on a Gentoo > server in combination with Dovecot. Editing and storing rules works as > expected if we use Roundcube. However if we use SOGo we get lines like this > one everytime we try to save them: > > Dec 02 13:11:35 sogod [24721]: <0x0x2e76ac9cc0[SOGoSieveManager]> WARNING: > Could not delete Sieve script - continuing...: {RawResponse = "{ok = 0; }"; > result = 0; } > > On the filesystem I can see that ~MAILHOME/sieve/sogo.sieve is removed > whenever > I try to save Sieve rules in SOGo. > > The Dovecot managesieve server doesn't report anything unusal: > > Dec 2 13:21:11 echo dovecot: managesieve-login: Login: user=<[email protected]>, > method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=27252, TLS, > session=<lgc7+atCE41/AAAB> > Dec 2 13:21:11 echo dovecot: managesieve-login: Login: user=<[email protected]>, > method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=27254, TLS, > session=<Utw8+atCFI1/AAAB> > Dec 2 13:21:12 echo dovecot: managesieve([email protected]): Connection closed > bytes=35/102 > Dec 2 13:21:12 echo dovecot: managesieve([email protected]): Connection closed > bytes=0/17 > > SOGo has been configured to use Sieve like this: > > SOGoSieveServer = "sieve://127.0.0.1:4190/?tls=YES"; > SOGoSieveScriptsEnabled = YES; > SOGoSieveFolderEncoding = UTF-8; > > The TLS connections doesn'T seem to be the problem. I don't use foldernames > that would require UTF-8. > > Those are normal. You get them sometimes. I see them more often for users without SIEVE rules, but also for others. The resulting files on the IMAP server are always correct. Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature
