I think this bug is in the neighborhood of 0004287.
Thanks for report, I'm feeling less alone.

Hello Cedric,

I saw your bug, but I was not sure was the same issue, so I opened a new one.

To make sure is the same bug, we could try to have the same debug options and try the same steps to reproduce (I am on centos 7 with the nightly rpms).

I have in my /etc/sogo/sogo.conf the following debug enabled:

SOGoDebugRequests = YES;
SoDebugBaseURL = YES;
LDAPDebugEnabled = YES;
PGDebugEnabled = YES;
MySQL4DebugEnabled = YES;
WODontZipResponse = YES;

I open a terminal and I do a tail -f /var/log/sogo/sogo.log

On the web gui I create a new folder (i.e. test2017) and on the log I see a successful folder creation:

Sep 18 15:04:55 sogod [4874]: |SOGo| request took 0.765789 seconds to execute
Sep 18 15:04:55 sogod [4874]: 10.1.2.70 "POST /SOGo/so/USER/Mail/0/createFolder HTTP/1.1" 204 0/19 0.770 - - 0
Sep 18 15:04:55 sogod [4874]: |SOGo| starting method 'GET' on uri '/SOGo/so/USER/Mail/0/view'
Sep 18 15:04:55 sogod [4874]: |SOGo| request took 0.366927 seconds to execute
Sep 18 15:04:55 sogod [4874]: 10.1.2.70 "GET /SOGo/so/USER/Mail/0/view HTTP/1.1" 200 3249/0 0.368 - - 0

then when I try to get into the very same folder I just created, I get the error message "An error occurred.." on the web client and on the log I get

Sep 18 15:06:42 sogod [4874]: [ERROR] <0x0x7f069aacab80[NGImap4Connection]> could not select URL: imap://USER@localhost/test/: {RawResponse = "{ResponseResult = {description = \"Mailbox doesn't exist: test\"; result = no; tagId = 6; }; }"; reason = "Mailbox doesn't exist: test"; result = 0; }

If you rename to test2017test from thunderbird, the error message on the log becomes:
Sep 18 15:08:50 sogod [4874]: |SOGo| starting method 'POST' on uri '/SOGo/so/USER/Mail/0/foldertesttest/view'
Sep 18 15:08:50 sogod [4874]: [ERROR] <0x0x7f069ab4f730[NGImap4Connection]> could not select URL: imap://USER@localhost/testtest/: {RawResponse = "{ResponseResult = {description = \"Mailbox doesn't exist: testtest\"; result = no; tagId = 6; }; }"; reason = "Mailbox doesn't exist: testtest"; result = 0; }
Sep 18 15:08:50 sogod [4874]: 10.1.2.70 "POST /SOGo/so/USER/Mail/0/foldertesttest/view HTTP/1.1" 500 72/45 0.374 - - 0

The numbers are strangely removed from the folder name.

Scratch that, this is exactly 0004287, very little doubt about it.

Fixed.

See https://github.com/inverse-inc/sogo/commit/d02f0db0b48f0631ecbaaa6d5f015e5407b035a9

Hello,

I have installed sogo-3.2.10.20170919-1.el7.centos.x86_64 that as far as I understand contains the commit proposed by Francis.

However the issue is still there.

Using the developer tools of chrome I see something very strange in the String.prototype.asCSSIdentifier.

I see that when I do an hard refresh and sogo rebuilds the folder list (I think), when it arrives to "test1" it does something very strange:

It does the loop at line 147, it does not find any special character to change (i.e. _ to U), and when it arrives at line 152, the newString value is updated to "test" from test1.

If I remove lines 152 and 154-156, when it arrives to the return statement, the newString value changes alone to "test".

It is very strange, I empty the cache each time (developer mode + "Empty Cache and Hard Reload") and I tried many times and still the digits are removed from the newString variable.

If I remove the handling of exceptions an the function becomes only
String.prototype.asCSSIdentifier = function() {
var characters = [ '_' , '\.', '#' , '@' , '\*', ':' , ',' , ' ', "'", '&', '\+' ];
var escapeds = [ 'U', 'D', 'H', 'A', 'S', 'C', 'CO', 'SP', 'SQ', 'AM', 'P' ];

var newString = this;

return newString;
};

I still have the error with the imap request for folder test instead of test1.

I am not really into javascript debugging, I do not know how to look further...

Am I doing something wrong?

Looks like our bot failed to generated the static JavaScript files last night, so you're still running the broken version.

Ah, ok. This is over my head, sorry.

Is there a way for me to compile these files myself or it is better to wait for next nightly?

Wait for the next build.

3.2.10.20170920-1 : first tests OK for me.

Thanks Francis

Same here!