0013610: Mail-format damaged when forwarded by Android-device via Active Sync #6731

Open
Gloirin opened this Issue Jun 9, 2018 · 3 comments

Comments

Projects
None yet
1 participant
@Gloirin

Gloirin commented Jun 9, 2018

Reported by apvit on 7 Nov 2017 12:51

Version: 2017.08.9 Community Edition

We have several Android devices connected to Tine20 via Active Sync.

When forwarding a mail using an Android-device, the format of the forwarded mail ist damaged somewhere on the way to the recepient. Format of the forwardig mail is OK.

We have testet it on several Android-smartphones of different brands. The error occors with all of them.

It seems, the error occurs since release 2017.08.9 Community Edition.

Steps to reproduce: Forward a mail from an Android device, which is connected to Tine20 via Active Sync.
Format of forwarding mail is good.
Format of forwarded mail is damaged.

@Gloirin Gloirin self-assigned this Jun 9, 2018

@Gloirin

This comment has been minimized.

Show comment
Hide comment

Gloirin commented Jun 10, 2018

Related to #6701

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by apvit on 7 Nov 2017 13:00

Not really sure, but this error could be related to 0013546.

Gloirin commented Jun 11, 2018

Comment posted by apvit on 7 Nov 2017 13:00

Not really sure, but this error could be related to 0013546.

@Gloirin

This comment has been minimized.

Show comment
Hide comment
@Gloirin

Gloirin Jun 11, 2018

Comment posted by pschuele on 7 Dec 2017 17:17

just tried that with a mantis email. the mail is added twice to the body. the second time, all linebreaks are missing. there is something wrong with forwarding via ActiveSync on Android...

Gloirin commented Jun 11, 2018

Comment posted by pschuele on 7 Dec 2017 17:17

just tried that with a mantis email. the mail is added twice to the body. the second time, all linebreaks are missing. there is something wrong with forwarding via ActiveSync on Android...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment