View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005330 | SOGo | ActiveSync | public | 2021-05-27 14:39 | 2022-11-22 11:20 |
Reporter | rbicelli | Assigned To | sebastien | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | [Client] Google | OS | Android | OS Version | Jelly Bean |
Product Version | 5.0.1 | ||||
Fixed in Version | 5.8.0 | ||||
Summary | 0005330: Replying from gmail app sometimes result in message being truncated | ||||
Description | Sometimes replying from gmail app result in message being truncated. The relevant part of attached payload is: Between "Ignora la m" and "CIAO" should be present another part of message. | ||||
Tags | active sync, android | ||||
sogo-aes-debug.txt (4,792 bytes)
<!DOCTYPE ActiveSync PUBLIC "-//MICROSOFT//DTD ActiveSync//EN" "http://www.microsoft.com/"> <Sync xmlns="AirSync:"> <Collections> <Collection> <Class>Email</Class> <SyncKey>4120-20704</SyncKey> <CollectionId>mail%2F81a33f177a9bf859bb6300004ca6fcd2</CollectionId> <Status>1</Status> <Commands> <SoftDelete> <ServerId>3966</ServerId> </SoftDelete> <Add> <ServerId>4120</ServerId> <ApplicationData> <To xmlns="Email:">"REDACTED.1@example.com" <REDACTED.1@example.com></To> <DisplayTo xmlns="Email:">REDACTED.1@example.com</DisplayTo> <From xmlns="Email:">"REDACTED.2" <REDACTED.2@example.com></From> <Subject xmlns="Email:">Fwd: offerta x fustini</Subject> <ThreadTopic xmlns="Email:">offerta x fustini</ThreadTopic> <DateReceived xmlns="Email:">2021-05-27T10:44:20.000Z</DateReceived> <Importance xmlns="Email:">1</Importance> <Read xmlns="Email:">1</Read> <MessageClass xmlns="Email:">IPM.Note</MessageClass> <ContentClass xmlns="Email:">urn:content-classes:message</ContentClass> <InternetCPID xmlns="Email:">65001</InternetCPID> <Body xmlns="AirSyncBase:"> <Type>2</Type> <Truncated>0</Truncated> <Preview/> <Data><div dir='auto'><div>Ciao Mauro .</div><div dir="auto">Ecco l offerta aggiornata.&nbsp;</div><div dir="auto"><br><div class="gmail_quote" dir="auto">---------- Messaggio inoltrato ----------<br>Da: "REDACTED" &lt;REDACTED.4@example.com&gt;<br>Data: 27 Mag 2021 11:46<br>Oggetto: offerta x Caffaro<br>A: REDACTED.3@example.com<br>Cc: <br><br type="attribution"><blockquote class="quote" style="$ <br> <br> in allegato offerta da inviare al cliente attenzione nuova quotazione <br> <br> Consegna meta' Giugno. <br> <br> Grazie <br> <br> <br> <br> <br> <br> </p> </blockquote></div><br></div></div></Data> <EstimatedDataSize>1168</EstimatedDataSize> </Body> <Attachments xmlns="AirSyncBase:"> <Attachment> <DisplayName>15736_OFF_CLI_2021-OFCBX-0006221.pdf</DisplayName> <FileReference>mail/Sent/4120/2</FileReference> <Method>1</Method> <EstimatedDataSize>357764</EstimatedDataSize> </Attachment> </Attachments> <Flag xmlns="Email:"> <FlagStatus>0</FlagStatus> </Flag> <Categories xmlns="Email:"/> <ConversationId xmlns="Email2:">PDk3N2E3MzFmLWI3ODQtNGQwMi05ZjNhLTllZWJjMGJjMjE4ZUBlbWFpbC5hbmRyb2lkLmNvbT4=</ConversationId> <LastVerbExecuted xmlns="Email2:">0</LastVerbExecuted> <NativeBodyType xmlns="AirSyncBase:">2</NativeBodyType> </ApplicationData> </Add> <Add> <ServerId>4121</ServerId> <ApplicationData> <To xmlns="Email:">"REDACTED" <REDACTED.3@example.com></To> <DisplayTo xmlns="Email:">REDACTED</DisplayTo> <From xmlns="Email:">"REDACTED.2" <REDACTED.2@example.com></From> <Subject xmlns="Email:">Re: REDACTED SUBJECT</Subject> <ThreadTopic xmlns="Email:">REDACTED SUBJECT</ThreadTopic> <DateReceived xmlns="Email:">2021-05-27T12:59:35.000Z</DateReceived> <Importance xmlns="Email:">1</Importance> <Read xmlns="Email:">1</Read> <MessageClass xmlns="Email:">IPM.Note</MessageClass> <ContentClass xmlns="Email:">urn:content-classes:message</ContentClass> <InternetCPID xmlns="Email:">65001</InternetCPID> <Body xmlns="AirSyncBase:"> <Type>2</Type> <Truncated>0</Truncated> <Preview/> <Data><div dir='auto'>Ciao Max .<div dir="auto">Ignora la mCIAO RICKY, MI HA CHIAMATO REDACTED PER SAPERE SE CI SONO SCONTI...<br /><br />NELLO STORICO CDU NON NE VEDO...<br /><br />DAMMI TUE INDICAZIONI, OPPURE CONTATTALO DIRETTAMENTE.<br /><br />MASSI<br /><br /><br /><br /><br /><br /><br /><br /></Data> <EstimatedDataSize>406</EstimatedDataSize> </Body> <Flag xmlns="Email:"> <FlagStatus>0</FlagStatus> </Flag> <Categories xmlns="Email:"/> <ConversationId xmlns="Email2:">PDIxMDUxMzEwMTkxMDAwMDcxNzU2OThAWERTMDMuc2Vydml6aTAxLmFkZHM+</ConversationId> <LastVerbExecuted xmlns="Email2:">0</LastVerbExecuted> <NativeBodyType xmlns="AirSyncBase:">2</NativeBodyType> </ApplicationData> </Add> </Commands> </Collection> </Collections> </Sync> |
|
Attached the Smartreply log, looks like the reply text is base64 encoded in base64 encoded body. smartreply-eas-log.txt (1,135 bytes)
<!DOCTYPE ActiveSync PUBLIC "-//MICROSOFT//DTD ActiveSync//EN" "http://www.microsoft.com/"> <SmartReply xmlns="ComposeMail:"> <ClientId>SendMail-105848786755999</ClientId> <SaveInSentItems/> <Source> <ItemId>15051</ItemId> <FolderId>mail%2F41c96c0cd6446f60c85f0000c343691f</FolderId> </Source> <MIME>RGF0ZTogVGh1LCAyNyBNYXkgMjAyMSAxNDo1OTozNSArMDIwMA0KU3ViamVjdDogUmU6IEludmlvIHByZXZlbnRpdm8gbnIuIDIwMjEtT0ZDQlgtMDAwNTQ2OQ0KTWVzc2FnZS1JRDogPDk1N2FiYTc5LTE1MjMtNGJlNi1hZGYyLWFiZDNhZjlmMmEyZkBlbWFpbC5hbmRyb2lkLmNvbT4NClgtQW5kcm9pZC1NZXNzYWdlLUlEOiA8OTU3YWJhNzktMTUyMy00YmU2LWFkZjItYWJkM2FmOWYyYTJmQGVtYWlsLmFuZHJvaWQuY29tPg0KRnJvbTogci5jb2xsaXZhQGRlZ2FlZ3JhemlvbGkuaXQNClRvOiAiTWFzc2ltaWxpYW5vIEN1Z2xpYW5kb2xvIC0gREVHQSBlIEdSQVpJT0xJIFMuci5sLiINCiA8bS5jdWdsaWFuZG9sb0BkZWdhZWdyYXppb2xpLml0Pg0KSW1wb3J0YW5jZTogTm9ybWFsDQpYLVByaW9yaXR5OiAzDQpYLU1TTWFpbC1Qcmlvcml0eTogTm9ybWFsDQpNSU1FLVZlcnNpb246IDEuMA0KQ29udGVudC1UeXBlOiB0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgNCkNvbnRlbnQtVHJhbnNmZXItRW5jb2Rpbmc6IGJhc2U2NA0KDQpQR1JwZGlCa2FYSTlKMkYxZEc4blBrTnBZVzhnVFdGNElDNDhaR2wySUdScGNqMGlZWFYwYnlJK1NXZHViM0poSUd4aElHMD0NCg==</MIME> </SmartReply> |
|
I cannot reproduce the problem with the lastest version of the gmail app. |
|
I am having a similar problem where Gmail app on Android breaks an attachment. When I send an e-mail with an attachment (a jpeg picture) it sends it just fine. However when I reply with this same attachment to another e-mail, it will do something to the attachment that makes it unreadable and the reported size in sogo webui goes from 4.5 MiB (working) down to 3.3 MiB (broken) - after download this size is 3398 KB for the broken picture and 3397 KB for the working one (yes the bigger/smaller is flipped compared to webui) I could provide the jpeg picture for testing - it's in the attachment (Woz.jpg and the broken version Woz - broken.jpg) SOGO version: 5.7.1 |
|
I have info to add, by analyzing attachments in the reply, I found that the broken one is missing CRLF across the whole file (only has LF). Apparently during some processing Sogo does this which renders binary file formats unreadable (pdf, jpeg tested). |
|
Can you please set SOGoEASDebugEnabled = YES and check sogo.log for <SmartReply ...> and <SendMail ...> requests? |
|
Sending mail with the attachment: <SendMail xmlns="ComposeMail:"> Replying to any mail with the same attachment: <SmartReply xmlns="ComposeMail:"> In Sent mails the attachment will be unreadable. The MIME parts compared here (was too big to upload here): |
|
This is a side effect of bug : fix(mime): encode text parts individually - Fixes 0005376 - https://github.com/inverse-inc/sope/commit/0eb64db6e1e3ba8fc5e03831ac31873f88a75859. |
|
Any way I can help further? Samsung Mail on Android has the same bug. This is universally reproducible on Android it seems. I don't know of any other good EAS apps and Gmail app by itself must be very popular. Why this is a serious problem imo: Right now, Sogo EAS always breaks attached files to replies from Android - meaning I have to write a new mail or use a webUI or use SMTP, which is not always possible on some "corporate" wifi networks (don't ask me why somebody blocked sending through 465 and 587, but EAS being entirely https is a huge advantage in this case and blocking 465 and 587 seems to be a common malpractice). I wouldn't even know about this if the recipient didn't tell me, which is the saddest part. Most people use Gmail or Outlook and their mail sending runs over https, so again, they won't hit this problem. But even people with their company IMAP setups run into this and it's a big reason to use EAS to avoid such bs. Btw, don't get me wrong, I appreciate this great software, but how did nobody run into this yet or do people even know it happens? Without the recipient notifying me, I wouldn't have known to this day. |
|
Merged : https://github.com/Alinto/sogo/pull/334/commits/dff907a158f9b8d7d2ca69e2ad33c7a4dd562abf Thanks @tfu |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2021-05-27 14:39 | rbicelli | New Issue | |
2021-05-27 14:39 | rbicelli | Tag Attached: active sync | |
2021-05-27 14:39 | rbicelli | Tag Attached: android | |
2021-05-27 14:39 | rbicelli | File Added: sogo-aes-debug.txt | |
2021-05-27 15:47 | rbicelli | Note Added: 0015287 | |
2021-05-27 15:47 | rbicelli | File Added: smartreply-eas-log.txt | |
2021-10-03 11:37 | tfu | Note Added: 0015507 | |
2022-10-29 16:07 | plantroon | Note Added: 0016322 | |
2022-10-29 16:07 | plantroon | File Added: Woz.jpg | |
2022-10-29 16:07 | plantroon | File Added: Woz - broken.jpg | |
2022-10-29 16:07 | plantroon | File Added: Empty essage sent from Gmail.eml | |
2022-10-29 16:07 | plantroon | File Added: Message with attachment.eml | |
2022-10-29 16:07 | plantroon | File Added: Reply with attachment to_ Empty essage sent from Gmail.eml | |
2022-11-18 16:48 | plantroon | Note Added: 0016399 | |
2022-11-18 18:37 | tfu | Note Added: 0016401 | |
2022-11-19 19:12 | plantroon | Note Added: 0016403 | |
2022-11-20 20:01 | tfu | Note Added: 0016406 | |
2022-11-20 20:36 | plantroon | Note Added: 0016408 | |
2022-11-21 10:17 | tfu | Note Added: 0016409 | |
2022-11-22 11:20 | sebastien | Note Added: 0016412 | |
2022-11-22 11:20 | sebastien | Assigned To | => sebastien |
2022-11-22 11:20 | sebastien | Status | new => resolved |
2022-11-22 11:20 | sebastien | Resolution | open => fixed |
2022-11-22 11:20 | sebastien | Fixed in Version | => 5.8.0 |