View Issue Details

IDProjectCategoryView StatusLast Update
0005969SOGoGUIpublic2024-05-16 09:24
ReporterArtim Assigned To 
PrioritynormalSeveritytweakReproducibilityhave not tried
Status newResolutionopen 
Product Version5.8.0 
Summary0005969: Better line breaking of base64 encoded mails
Description

For some reason, some mail clients (including Thunderbird) encode mails as base64 when it's not needed (normal text, not any attachments or special characters beyond UTF8) and use that as only encoding message. If such a mail is being opened in SOGo, it's shown with very strange line breaking. If that mail also contains that text e.g. as HTML, the issue doesn't show. Also, this displaying error doesn't show in other clients, including Thunderbird. An improved handling of this case would be greatly appreciated.

Tagsbase64

Activities

sebastien

sebastien

2024-05-15 19:32

administrator   ~0017732

Hello, can you provide an eml ?

Artim

Artim

2024-05-16 09:24

reporter   ~0017733

Not at the moment, but I think that may not be necessary. I've found a way by accident to show what's being ignored by Thunderbird and other mail clients, but not by SOGo: I've taken the base64 encoded body, ran it through base64 -d and looked at the result through emacs. I've previously had base64 put the output to stdout which doesn't show these extra symbols. At the line breaking point where SOGo breaks the line, emacs shows the character combination "^M" which probably is some kind of new line character. SOGo puts a line break everywhere this character appears, while Thunderbird ignores it. Now I'm not sure about the specifics - or even why Thunderbird but them there in the first place - but for viewing the content, at least Thunderbird and K9 mail only insert an empty line when there's only the "^M" in a line.

Issue History

Date Modified Username Field Change
2024-05-14 17:12 Artim New Issue
2024-05-14 17:12 Artim Tag Attached: base64
2024-05-15 19:32 sebastien Note Added: 0017732
2024-05-16 09:24 Artim Note Added: 0017733