Hello,
The SOGo RHEL 9 nightly build dated 20260811 which I installed today appears to 
contain a regression that prevents users from composing, saving drafts, or 
sending mail through the web interface.
sogo-5.12.9.20260811-1.el9.x86_64
sogo-activesync-5.12.9.20260811-1.el9.x86_64
with the corresponding 20260811 SOPE packages.
Symptoms:
 * Selecting Compose produces an empty window with a persistent spinner * 
Saving or sending a draft fails * Compose, save and send requests return HTTP 
501 * Login, mailbox listing and message reading continue to work * Restarting 
sogod does not resolve the problem
The SOGo log records:
NSInvalidArgumentException -[GSCInlineString stringWithoutHTMLInjection:]: 
unrecognized selector
For example:
POST /SOGo/so/<user>/Mail/0/folderDrafts/<draft>/send HTTP/1.1 501
The installed build calls the obsolete one-argument stringWithoutHTMLInjection: 
selector from SOGoDraftObject.m, while the runtime provides the newer 
two-argument selector.
This appears to have been corrected upstream by commit 
1caa25711f5891135c7ebca63f33b8758c00c8e8, “fix(bug): incorrect method called”:
https://github.com/Alinto/sogo/commit/1caa25711f5891135c7ebca63f33b8758c00c8e8
That commit changes:
[newText stringWithoutHTMLInjection: NO]
to:
[newText stringWithoutHTMLInjection: NO stripAngular: NO]
However, the correction was committed after the 20260811 nightly package was 
built, and a corrected RHEL 9 nightly was not yet available when I checked.
I could not find an entry for this problem at bugs.sogo.nu, and there have been 
no comments on this mailing list warning users that this nightly breaks core 
webmail functionality.
Could the SOGo team please:
1. Confirm which nightly platforms and builds are affected.
2. Publish a corrected nightly as soon as possible.
3. Advise nightly users of the regression and its impact.
Please Also Consider retaining at least one previous nightly build so 
administrators can perform a targeted rollback when a nightly is defective.
We have temporarily mitigated the issue locally by providing a compatibility 
method that forwards the obsolete selector to the corrected two-argument 
sanitizer (thank you Codex). That is only an interim measure until a corrected 
package is available.
Regards,
Simon

-- 
 Simon Wilson
M: 0400 121 116

Reply via email to