Hi,
It happens only for relpies but seems to be linked to formatting. 
If I close the reply draft and open it it the draft folder everything is fine. 
So my workarround is  * reply and save as draft. * open draft and edit.
Best regards
Jürgen


Am Dienstag, Juli 07, 2026 17:04 CEST, schrieb "dev" ([email protected]) 
<[email protected]>:

 
Hello, 
Thanks Jurgen ! Is the behavior you're seeing is like the bug linked by Cédric 
(https://bugs.sogo.nu/view.php?id=6209) ? For us it completely seems like the 
same issue.Le 07/07/2026 à 15:42, "Juergen Breitlow" ([email protected]) a 
écrit :
 
Hi everybody,
I can see the empty forward problem as well. Running Mailcow/Sogo with 5.12.5.
Best regards
Jürgen

Am Montag, Juli 06, 2026 13:52 CEST, schrieb "Christian Mack" 
([email protected]) <[email protected]>:

 
Hello

Please open a bug report at
https://sogo.nu/bugs

As development of SOGo 6 is currently prioritised, there will probably 
no fix in the near future.
With a bug report, this will not get lost.


Kind regards,
Christian Mack

Am 29.06.26 um 11:06 schrieb dev ([email protected]):
> Hello,
> 
> We are using SOGo 5.12 on a custom MailCow instance. For some emails, we 
> are having troubles when forwarding them from the inbox or draft 
> folders : after clicking on the forward button, when the modal opens up, 
> we only see original message header but no content. When opening source 
> we can see the original message is there actually...
> 
> Here is a screenshot :
> 
> Image
> 
> 
> If sending the message as is, the message can be seen with no issue 
> (original message header + original message content) by the recipient 
> even in the same SOGo instance.
> 
> The problem never appears when forwarding from the sent folder.
> 
> 
> We first created an issue on MailCow's GitHub repository : https:// 
> github.com/mailcow/mailcow-dockerized/issues/7279
> We also searched in this mailing list archive but couldn't find a 
> similar problem.
> 
> We also tested up to SOGo 5.12.8 and problem is still here.
> 
> 
> There is surely something triggering the behavior in the email affected 
> but we couldn't find what...
> 
> 
> Does someone saw something similar ? Has anyone would have idea on what 
> to look ?
> 
> Thanks
> 

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung IT-Dienste Forschung, Lehre, Infrastruktur
78457 Konstanz
+49 7531 88-4416

 



  



 

Reply via email to