My install lists the image as ghcr.io/mailcow/sogo:5.12.9-1, which was published two months ago. That should contain the fixes, I believe. Perhaps the OP just needs to update the containers?
On Thu, Aug 13, 2026 at 3:10 PM dev <[email protected]> wrote: > Hello, > > What is the SOGo version contained in the Mailcow image ? Is it 5.12.9 ? > On the SOGo release page <https://github.com/Alinto/sogo/releases> there > aren't any new other version than 5.12.9 dating of late may. > > The empty content forward bug was referenced as 0006209: HTML ckeditor > content truncated on forward if header reference - SOGo | BTS > <https://bugs.sogo.nu/view.php?id=6209>, is it the same behavior you are > experiencing ? If so the commit fixing it is f11f34c > <https://github.com/Alinto/sogo/commit/f11f34cdefdd4175ae6c8b0814c2ccaecfd7c373>. > It was done after the 5.12.9 release. > > Some of our clients are confronted to it and we are looking forward for a > new SOGo release O:) > Le 12/08/2026 à 16:53, Dimos Vamvourellis YAW ([email protected]) > a écrit : > > Hello, > > I'm following up on my report from July 20 regarding SOGo 5.12.9-1 on > mailcow. > > Unfortunately, the previously suggested workaround of saving the > reply/forward as a draft and reopening it does *not* solve the issue for > us. > > The two main problems are still consistently reproducible: > > 1. > > *Reply / Reply All:* the original message is not quoted. Instead, SOGo > inserts: > > (null) > 2. > > *Forward:* the original message body is completely missing from the > composer. Attachments are forwarded correctly, but the actual email content > is not included. > > We are running: > > - > > mailcow Mooly 2026 Revision A > - > > SOGo 5.12.9-1 (ghcr.io/mailcow/sogo:5.12.9-1) > > I would also be happy to open proper bug reports for these issues, but my > account on bugs.sogo.nu currently appears to have read-only access and > does not allow me to create an issue. > > Could someone from the SOGo team please advise: > > 1. > > Are the Reply/Reply All (null) and missing Forward body known issues? > 2. > > Are they already tracked in the bug tracker because from my research i > couldn't find them? > > These issues currently make Reply/Reply All and Forward unreliable for our > users, so I would be happy to provide any logs, browser console output, > network requests, or test messages needed to reproduce them. > > Thank you, > Dimos > > > > On 7/9/2026 3:40 PM, Dimos Vamvourellis YAW wrote: > > Hello, we are using sogo-mailcow (ghcr.io/mailcow/sogo:5.12.9-1). > > We are facing three different issues, but because i only have view access > in the bug forum i cannot post them. > > 1. I found the same issue reported on another email (msg34617), but the > solution doesn't work for us. > > Whenever we try to forward, the whole email content is missing. > > 2. Whenever we try to reply/reply all, in the content we only see (null) > Im attaching a .eml example. > > 3. On some emails from specific users, the viewer doesnt show the content > correctly > "KáëçóðÝñá óáò, Åõ÷áñéóôïýìå ðïëý ãéá ôçí áðïäï÷Þ óáò" > Please let me know how i can privately share a .eml example. > A temporary solution is to select "convert to event" and in the new popup > you can read the text correctly. > > Please let me know if you need more details. > Best, Dimos > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
