View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0004069SOGoBackend Mailpublic2017-03-07 00:152017-03-07 16:04
Reportersteve Assigned Tofrancis  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platform[Server] LinuxOSRHEL/CentOSOS Version7
Product Version3.2.7 
Summary0004069: error saving vacation sieve script
Description

I have v3 server talking TLS sieve to Cyrus-IMAP backend which fails when trying to setup vacation message. The same config works on old v2 server (2.3.10), but fails on v3 (3.2.7) server with:

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; }

This happens regardless as to whether there is an existing sieve script for the user or not.

Steps To Reproduce

Open SOGo Web UI and go to Preferences and then Mail, and finally Vacation. Create and save vacation away message. SOGo responds affirmatively, however, the script is not saved.

Additional Information

Both v2 and v3 servers authenticate to sieve server properly, however, only v2 is able to save new or change existing script.

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2017-03-07 08:41

developer   ~0011444

This warning can be ignored.
They also happen for V2 sometimes, but the sieve scripts are stored successfully.

Your problem has another reason.
What do cyrus/sieve logs show?
steve

steve

2017-03-07 15:35

reporter   ~0011450

Ok, strange. It does seem to be working now with my account, but wouldn't work at all yesterday. Two people reported it not working either who are both using the v3 WebUI. As I can't seem to reproduce the issue any longer, please close this issue.

Issue History

Date Modified Username Field Change
2017-03-07 00:15 steve New Issue
2017-03-07 08:41 Christian Mack Note Added: 0011444
2017-03-07 15:35 steve Note Added: 0011450
2017-03-07 16:04 francis Status new => closed
2017-03-07 16:04 francis Assigned To => francis
2017-03-07 16:04 francis Resolution open => no change required