View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002314SOGosogo-toolpublic2013-05-11 23:132013-05-13 15:30
Reporterichdasich Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2.0.5 
Summary0002314: tls=YES argument for sieve not parsed correctly in sogo conf
Description

Using SOGoSieveServer = sieve://mail.example.com:2000/?tls=YES; in /etc/sogo/sogo.conf leads to:

mail.eberlin.de /var/lib/sogo # /etc/init.d/sogod restart
Restarting SOGo:
2013-05-12 01:10:51.689 sogod[5805] File NSDictionary.m: 626. In -[NSDictionary initWithContentsOfFile:] Contents of file '/etc/sogo/sogo.conf' does not contain a dictionary
<0x0x7f05142a5528[SOGoStartupLogger]> Cannot read configuration from '/etc/sogo/sogo.conf'. Aborting
sogo [FAILED]

Using SOGoSieveServer = sieve://mail.example.com:2000/; provides the correct results.

If ~/GNUstep/Default/.GNUstepDefaults is used instead of /etc/sogo/sogo.conf
<key>SOGoSieveServer</key>
<string>sieve://mail.example.com/?tls=YES</string>
works correctly.

Additional Information

Package Version: 2.0.5a-1.centos6
System: Scientific Linux 6.4

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2013-05-13 14:45

developer   ~0005581

Did you create your sogo.conf with sogo-tool?
ichdasich

ichdasich

2013-05-13 14:48

reporter   ~0005582

Nope, was hand written.
Christian Mack

Christian Mack

2013-05-13 15:01

developer   ~0005583

Could you generate it with sogo-tool from the working GNUStep configuration and check the diff?

I suspect you missed some curly braces in sogo.conf.
ichdasich

ichdasich

2013-05-13 15:13

reporter   ~0005586

Issue could be identified. Although sogo.conf usually accepts entries without explicit string notation (no "" around it), it is required if the string contains a question mark.

A configuration file generated by sogo-tool contains the correct formating. If " are applied around the entry, the problem does disappear. It can be reintroduced by removing the notation.

Bug can be either closed as fixed from my side.

Issue History

Date Modified Username Field Change
2013-05-11 23:13 ichdasich New Issue
2013-05-13 14:45 Christian Mack Note Added: 0005581
2013-05-13 14:48 ichdasich Note Added: 0005582
2013-05-13 15:01 Christian Mack Note Added: 0005583
2013-05-13 15:13 ichdasich Note Added: 0005586
2013-05-13 15:30 jraby Status new => closed
2013-05-13 15:30 jraby Resolution open => no change required