View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005716||SOGo||Web Mail||public||2023-03-24 08:10||2023-03-27 08:49|
|Priority||normal||Severity||crash||Reproducibility||have not tried|
|Summary||0005716: New Identity generates faulty JSON|
I'm using SoGo 5.8.0 as part of Mailcow. (related issue: https://github.com/mailcow/mailcow-dockerized/issues/5146)
I've added a new Identity for my account via SoGo Webclient to send mails with a different sender address. This worked fine for the first 4 different identities.
It seems, that the generated json (stored in sogo_user_profile) is corrupt. After "SoGoMailIdentities" there is some weird pipe but I'm not sure if this is by purpose or the source of the error. (I added some snippets to the Github Issue)
I am not entirely sure if it's safe to touch the database entry or just drop it entirely. What would be the best way to at least reset the identities without breaking everything?
|Tags||identity, web, webmail|
Hi, I did not reproduced this issue ont my dev env. Could you please provide :
I posted a snippet of the generated json on GitHub. Is this sufficient?
Where to get the errors from the JS console?
But I guess, I already found the issue here. Some chrome plugin injected something in the signature field. This might have broken it:
Uncaught SyntaxError: Invalid or unexpected token (at view:48:400)
So it looks like this wasn't properly escaped? (It shouldn't be there at all in the first place, I will contact the creator of that extension too)
|2023-03-24 08:10||skankhunt42||New Issue|
|2023-03-24 08:10||skankhunt42||Tag Attached: identity|
|2023-03-24 08:10||skankhunt42||Tag Attached: web|
|2023-03-24 08:10||skankhunt42||Tag Attached: webmail|
|2023-03-27 07:44||sebastien||Note Added: 0016761|
|2023-03-27 08:49||skankhunt42||Note Added: 0016762|