View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002210SOGoWeb Preferencespublic2013-01-30 15:292013-02-05 20:17
Reporterbofhus Assigned Tojraby 
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionfixed 
Product Version2.0.4 
Fixed in Version2.0.5 
Summary0002210: Comunication with sieve suspends...
Description

I'm trying to add redirect via SOGo Preferences. The script appears in IMAP serwer, but is not activated, and TCP connection between SOGo and MGM Sieve is still connected and idle: DOvecot 2.1.8, Sieve 2.0,4, Centos 6.3 x64:

Session dump:

"IMPLEMENTATION" "Dovecot Pigeonhole"
"SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave"
"NOTIFY" "mailto"
"SASL" "PLAIN LOGIN"
"STARTTLS"
"VERSION" "1.0"
OK "Dovecot ready."

AUTHENTICATE "PLAIN" {80+}
[BASE64:<login>\0<login>\0<pass>]

OK "Logged in."
NO "Error in MANAGESIEVE command [BASE64:<some trashes>]: Unknown command."

SETACTIVE ""

DELETESCRIPT "sogo"

OK "No scripts currently active."
NO (NONEXISTENT) "Script does not exist."

PUTSCRIPT "sogo" {31+}
redirect "bogdan@agh.edu.pl";

OK "PUTSCRIPT completed."

And nothing more. SOGo keeps TCP connection, but don't sending any packets more

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
child of 0002228 resolvedjraby ManageSieve connection should be closed 

Activities

bofhus

bofhus

2013-02-05 06:48

reporter   ~0005328

Please close.
ludovic

ludovic

2013-02-05 12:24

administrator   ~0005334

So there is no issue? It was a configuration issue on your end?
bofhus

bofhus

2013-02-05 16:17

reporter   ~0005336

The issue appears, if the sieve script is instaled/deleted correctly. SOGo doesn't closse managesieve connection. I reported it separately, with details, in 0002228. The log, which I included in this report, concerns situation where script instalation fails. But in this case connection is closed and error in log appears. So this report is incorrect and should be closed.

Issue History

Date Modified Username Field Change
2013-01-30 15:29 bofhus New Issue
2013-02-05 06:48 bofhus Note Added: 0005328
2013-02-05 12:24 ludovic Note Added: 0005334
2013-02-05 16:17 bofhus Note Added: 0005336
2013-02-05 20:15 jraby Relationship added child of 0002228
2013-02-05 20:17 jraby Status new => resolved
2013-02-05 20:17 jraby Fixed in Version => 2.0.5
2013-02-05 20:17 jraby Resolution open => fixed
2013-02-05 20:17 jraby Assigned To => jraby