View Issue Details

IDProjectCategoryView StatusLast Update
0001097SOGoBackend Mailpublic2011-03-02 13:23
Reportercorradofiore Assigned Toludovic  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionno change required 
Product Version1.3.4 
Target Version1.3.6 
Summary0001097: Cannot define per-domain imap hosts
Description

In GNUstep defaults, the SOGoIMAPServer declaration, i.e.

    <key>SOGoIMAPServer</key>
    <string>imap://imap.mydomain.com:143</string>

won't be parsed when put into a domain block. For example:

<key>domains</key>
<dict>
<key>mydomain.com</key>
<dict>
<key>SOGoMailDomain</key>
<string>mydomain.com</string>
<key>SOGoIMAPServer</key>
<string>imap://imap.mydomain.com:143</string>
</dict>
</dict>

will be ignored and SOGoIMAPServer value will default to localhost.

The above could be a problem in a large deployment where multiple IMAP backends (possibly one per domain) are used.

Additional Information

See also http://www.mail-archive.com/users@sogo.nu/msg02609.html

TagsNo tags attached.

Activities

ludovic

ludovic

2011-02-17 20:00

administrator   ~0002124

I've just tried and I can't reproduce the bug. It works perfectly.

Please paste your FULL .GNUstepDefaults.

ludovic

ludovic

2011-02-17 20:01

administrator   ~0002125

Also make sure that your <domains> declaration is a leaf of <key>sogod</key> ...

ludovic

ludovic

2011-02-23 17:20

administrator   ~0002156

Please give feedback otherwise this issue will be closed.

corradofiore

corradofiore

2011-03-02 10:07

reporter   ~0002179

Sorry for the delay. After some more days of testing I was able to trace the origin of the problem.

1) The declaration inside the <domains> node actually works, but...
2) It won't be called because there is no clear way to associate a SOGo domain with a certain host, like e.g. in Roundcube.

At first, I thought that under a MySQL backend the domain or the SOGoMailDomain value would have been matched against the http host, or the @domain.tld part of the email, or the http server name. Since none of them worked, I thought there was a bug in preference parsing. I later realized that the SOGo domain gets selected by looking at which UserSource the user belongs to.

So, to recap:
-- there are no bugs in preferences parsing
-- the SOGo way to decide which domain shall be used could be made more straightforward (but that's a different problem).

Feel free to close this bug report.

Issue History

Date Modified Username Field Change
2011-01-26 13:42 corradofiore New Issue
2011-02-01 21:22 ludovic Target Version => 1.3.6
2011-02-17 20:00 ludovic Note Added: 0002124
2011-02-17 20:01 ludovic Note Added: 0002125
2011-02-23 17:20 ludovic Note Added: 0002156
2011-02-23 17:20 ludovic Assigned To => ludovic
2011-02-23 17:20 ludovic Status new => feedback
2011-03-02 10:07 corradofiore Note Added: 0002179
2011-03-02 13:23 ludovic Status feedback => resolved
2011-03-02 13:23 ludovic Resolution open => no change required