0004751: WRONG EPILOGUE CAN BREAK MIME FRAMEWORKS WHEN DEAL WITH MULTI-LEVEL MIME EML CONTENTS - SOGo | BTS

ID	Project	Category	View Status	Date Submitted	Last Update

0004751	SOGo	Backend Mail	public	2019-05-17 12:12	2019-05-17 12:12

Reporter	davidnucli	Assigned To
Priority	urgent	Severity	major	Reproducibility	always
Status	new	Resolution	open
Platform	ALL OSES	OS	ALL OSES	OS Version	ALL OSES
Product Version	4.0.1

Summary	0004751: WRONG EPILOGUE CAN BREAK MIME FRAMEWORKS WHEN DEAL WITH MULTI-LEVEL MIME EML CONTENTS
Description	All mails composed with SOGO has extra breaks on epilogue espaces that are non RFC compliants Major part of MIME libraries used to parse EML Mails comming from sogo mailservers will crash.
Steps To Reproduce	For example: $ pike Pike v7.8 release 866 running Hilfe v3.5 (Incremental Pike Frontend) string r=Stdio.read_bytes("sogo_format.eml"); object msg = MIME.Message(r); multipart message improperly terminated ("\n") /usr/lib/pike7.8/modules/MIME.pmod/module.pmod:1518: Message(([ ]))->create("Content-Type: multipart/mixed; boundary=\"----=_=-_OpenGroupware_org_NGMime-31711-1558092180.670334-2------\"\nFrom: \"David Estopa\" <destopa@lleida.net>\nX-Forward: 10.20.20"+[1642],UNDEFINED,UNDEFINED,UNDEFINED) /usr/lib/pike7.8/modules/MIME.pmod/module.pmod:818: MIME->Message() Files to reproduce and correct
Additional Information	* I attach two files to reprocuce and correct it: sogo_format.eml ( Generated eml file format from SOGO SAVE AS OPTION, for a simple EML (2 LEVELS) composed as multipart/mixed (multipart/alternative + another atached part) sogo_format.eml.ok** ( Same eml file, but with correct eml breaks format, without no extra breaks on all boundaries )
Tags	No tags attached.

Date Modified	Username	Field	Change
2019-05-17 12:12	davidnucli	New Issue
2019-05-17 12:12	davidnucli	File Added: files.zip