Hello Am 06.03.2017 um 20:13 schrieb Stephen Ingram ([email protected]): > I see previous reference from some time ago to where setting vacation auto > response (via sieve) would not work for a TLS connection. My old v2 server > works just fine, however, when I try from latest version 3 server to > Cyrus-IMAP TLS sieve connection I see: > > Mar 06 10:56:18 sogod [2503]: |SOGo| set clientObject: > <0x0x7fc1ab24bc40[SoPageInvocation]: class=UIxPreferences > product=<0x0x7fc1ab243f80[SoProduct]: loaded code-loaded > bundle=/usr/lib64/GNUstep/SOGo/PreferencesUI.SOGo #categories=1 > rm=0x0x7fc1ab245400>> > Mar 06 10:56:18 sogod [2503]: <0x0x7fc1accc0ce0[NGSieveClient]> TLS started > successfully. > Mar 06 10:56:19 sogod [2503]: <0x0x7fc1accce190[NGSieveClient]> TLS started > successfully. > Mar 06 10:56:19 sogod [2503]: <0x0x7fc1accccb10[SOGoSieveManager]> WARNING: > Could not delete Sieve script - continuing...: {RawResponse = "{ok = 0; > reason = \"Error deleting script\"; }"; result = 0; } > > Looking at the sieve server, the connection appears to work, however, as > from above SOGo logs, the script change does not. This happens regardless > as to whether there is an existing script or not. >
You can ignore those warning messages. They happen sometimes, but the sieve scripts are stored successfully anyway. BTW: What do you think "TLS started successfully." means ;-) 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
