Issue 6399 in k9mail: K9 Mail What'sUp audio file Attachment Issue

[k9m...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Product-k9mail

New issue 6399 by OcispPo...@gmail.com: K9 Mail What'sUp audio file
Attachment Issue
http://code.google.com/p/k9mail/issues/detail?id=6399

Is this a bug or a support request? BUG - ISSUE

What's going wrong?

Wrong attachment if share audio file in Whatsup with K9 Mail

What steps will reproduce the problem?
1. Open whatsup
2. Open a contact and register and send an audio record (record from
whatsup)
3. Now select the audio message sended and click on the share button and
select K9 Mail as client
4. enter an email adress and send.

The file attachments are in wrong format and is not readable from PC
If you use Gmail app fore share the audio file in whatsup the problem isn't

What do you expect to have happen?

To see acc file in attachments email

What do you see instead?

A msg file in the attachments

What version of K-9 are you using?

4.804

What is your device and what version of Android are you using?

4.4.2 Android on TIM Samsung Galaxy S5

Is your email account a POP account, Exchange Account or an IMAP account?

IMAP

In order for us to have a chance at helping you with a complex issue, we're
going to need a debug log from your phone. You can dramatically increase
the chances of a quick and successful resolution to this issue by following
the directions at https://github.com/k9mail/k-9/wiki/LoggingErrors -- If
you can't give us a trace, there's a pretty good chance that we won't be
able to act on your bug report.

Note that all user-reported issues default to "Type-Defect" and are not
changeable. We can figure out if it should be something else.

What else should we know?



--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[k9m...@googlecode.com]

Comment #1 on issue 6399 by dejan.sk...@gmail.com: K9 Mail What'sUp audio
file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

I noticed the same issue with sharing an image from WhatsApp. Attached jpg
file can not be opened as picture and instead is displayed like lot of
strange charachters.

[k9m...@googlecode.com]

Comment #2 on issue 6399 by silvano....@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

I have the same issue.
I will try to activate debug. I need to install adb to get the log.
Anyway the problem is reproducible.
I created simple video file from Whatsapp and send it to a contact.
I then share the video selecting K9 email client. The receiver (in this
case myself) has got a corrupt attachment file.
The received binary file seems to have bytes of 0x80 instead of 0x00. At
least at the initial portion of the file.
When the original file has a 0x0A byte (sometimes/everytime?), the received
file has a 0x0D AND 0x0A also. So, the received file is bigger than
original.
There is more. The file uploaded to the imap "sent" folder is bigger than
the file sent to the receiver by smtp.

Samsung Galaxy S3 stock ROM, android 4.3
K9 v4.804 - IMAP

[k9m...@googlecode.com]

Comment #3 on issue 6399 by silvano....@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

I have the same issue.
I will try to activate debug. I need to install adb to get the log.
Anyway the problem is reproducible.
I created simple video file from Whatsapp and send it to a contact.
I then share the video selecting K9 email client. The receiver (in this
case myself) has got a corrupt attachment file.
The received binary file seems to have bytes of 0x80 instead of 0x00. At
least at the initial portion of the file.
When the original file has a 0x0A byte (sometimes/everytime?), the received

file has a 0x0D AND 0x0A also. So the received file is bigger than source
file.

[k9m...@googlecode.com]

Comment #4 on issue 6399 by silvano....@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

I attach the trace.

Attachments:
k9-log.7z 3.9 KB

[k9m...@googlecode.com]

Comment #5 on issue 6399 by giovanni...@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

Same problem for me: push for a long time on a WhatsApp image to select it,
choose to share with K9.
Image is unreadable for the recipient.
The problem does not appear when you single tap on a WhatsApp image to zoom
it, and then share from here.

Analyzing the received email: K9 is encoding the attachment with
Content-Transfer-Encoding: 8bit, but I think the 8bit body is not correct,
because it contains \r\n in the wrong position, not permitted by MIME RFC
2045 https://tools.ietf.org/html/rfc2045#section-2.8
I think K9 should encode attachments in the usual base64 way.

Using K9 from PlayStore, v5.006, Samsung Galaxy S5.



K9 will encode it in

[k9m...@googlecode.com]

Comment #6 on issue 6399 by giovanni...@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

Same problem for me: push for a long time on a WhatsApp image to select it,
choose to share with K9.
Image is unreadable for the recipient.
The problem does not appear when you single tap on a WhatsApp image to zoom
it, and then share from here.

Analyzing the received email: K9 is encoding the attachment with
Content-Transfer-Encoding: 8bit, but I think the 8bit body is not correct,
because it contains \r\n in the wrong position, not permitted by MIME RFC
2045 https://tools.ietf.org/html/rfc2045#section-2.8
I think K9 should encode attachments in the usual base64 way.

Using K9 from PlayStore, v5.006, Samsung Galaxy S5.

[k9m...@googlecode.com]

Comment #7 on issue 6399 by giovanni...@gmail.com: K9 Mail What'sUp audio

file Attachment Issue
https://code.google.com/p/k9mail/issues/detail?id=6399

It seems that development has moved to github. I posted the issue here:
https://github.com/k9mail/k-9/issues/744