Hello Am 20.10.2015 um 14:31 schrieb FoxNET Support: > >> Le 20 oct. 2015 à 13:31, Christian Mack <[email protected]> a >> écrit : >> >> Am 18.10.2015 um 12:22 schrieb FoxNET Support: >>> >>> I will not put oil on the fire, but I still have this error on version 2.3.2 >>> >>> What is this error, or it happens is what, because I can not find and I can >>> not understand ... >>> >>> Oct 18 12:13:06 sogod [30984]: <0x0x7f4112991268[NGImap4Client]> Note: no >>> key found for sorting, using 'DATE': (null) >>> Oct 18 12:13:07 sogod [30984]: <0x0x7f4112991268[NGImap4Client]> Note: no >>> key found for sorting, using 'DATE': (null) >> < cut > >> >> This is no error, it is a note/hint/info. >> It occurs, because the user didn't choose for which column his email >> list shall be sorted. >> SOGo then falls back to sorting after 'DATE'. >> >> So no harm at all. >> > Ok, question, how to adjust, it is the configuration used ... > What do I have to perform >
It is a user setting. The user has to click on the column header he/she wants to sort for. This will be stored by SOGo. You can see this in the sogo-tool backup of a user (Preferences -> mail -> SortingState), but I do not know if you can set this for a user. You could add it to the users backup and restore his/her preferences with "sogo-tool restore -p". 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
