(Archived) Emailed image from Samsung G600 not working

[Verminity 0]

Hi,

I'm trying to get the "email image from camera phone" scenario working with my Samsung G600 phone. Emails that only contain text work correctly, but if I try to attach an image Evernote tells me

"Evernote was unable to submit your note for the following reason:

Emailed note was received, but an internal error occured while processing it. This may be because the note/email is broken, or due to some other factor. Please try sending the note again later."

I can see the email and the image from the phone fine in Thunderbird.

The source of the email looks like this:

Return-Path: ...

Received: from 10.57.57.171 ([212.183.134.131])

by mx.google.com with ESMTPS id 10sm54636eyd.0.2009.09.02.07.34.56

(version=SSLv3 cipher=RC4-MD5);

Wed, 02 Sep 2009 07:35:16 -0700 (PDT)

Message-ID: <4a9e82a4.0a04d00a.7145.0a7d@mx.google.com>

From: ...

To: ...

Subject: Test

Date: Tue, 02 Sep 2009 15:34:00 +0000

Reply-to: ...

MIME-Version: 1.0

Content-Type: multipart/mixed;

boundary="----=_NextPart_KO_X1098V29876N91O412QM815"

This is a multi-part message in MIME format.

------=_NextPart_KO_X1098V29876N91O412QM815

Content-Type: text/plain; charset=UTF-8

Content-Disposition: inline

Content-Transfer-Encoding: base64

VGVzdA==

------=_NextPart_KO_X1098V29876N91O412QM815

Content-Type: image/jpg

Content-Disposition: attachment;

filename="Photo-0003.jpg"

Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHhof

Hx0aHRwhJS8oISMsIxwdKTgpLDAyNTU1ICc6PjkzPS80NTL/2wBDAQkJCQwLDBgNDRgyIh0i

...

...

zzTKWgYuaSmk1GXoGS7sUwvUdFAB1paXpzSgDvQAm2nYzT6UC

gBgWpCuOlO2YpGwBxQIZjFMLDFTRW8ty21B+tab6THDbjf8A6ylzDMD55OgqWO0/vVo+Wq5q

En5uKBCpbhalPTFMV6k/hoEMbrTKXNJTQwpKd2pQOaAG07bUgFKBmgQwLT8UuKl2UgIwmaeq

1IFqVY6YESrUyxVYSGrtvZmVtooA/9k=

------=_NextPart_KO_X1098V29876N91O412QM815--

(Email addresses and majority of image data removed)

If this a supported format? There doesn't seem to be any options on the phone to change the way the email is created, so I guess I'm out of luck if not...

Thanks for your time.

[engberg 89]

I checked on the service, and it appears that there was another layer of MIME nesting in the actual email we received. You sent us that email, but in the form of an attachment on an empty email:

...
Subject: [Fwd]
Content-Type: multipart/mixed;
 boundary="------------050605060705040508050502"

This is a multi-part message in MIME format.
--------------050605060705040508050502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



--------------050605060705040508050502
Content-Type: message/rfc822;
 name="Test.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Test.eml"
...

From the perspective of our mail server, this looks like an email with no contents and an attached file named "Test.eml". If you had a Premium account, we would have created a note with this attached file, but this is not one of the supported Free file types, so the message was rejected since it didn't contain any relevant Free parts.

[Verminity 0]

Thanks for looking into this.

That specific email was an attempt to forward the phones email from Thunderbird (note the FW: in the subject) not the email that the phone sent directly. If you can look back further than one email into my account you should find the original sent from the phone shortly before that one. If not let me know and I can send it directly from the phone again.

Thanks again for the incredibly fast response.

[engberg 89]

I checked the first message of the three failures, and it appears that it was rejected because its text part contains content that is encoded in "base64" format, but in a way that is rejected by Sun's mail processing Java libraries:

...
------=_NextPart_KO_X1098V29876N91O412QM815
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: base64

====

------=_NextPart_KO_X1098V29876N91O412QM815
Content-Type: image/jpg
...

When the Java mail libraries try to parse this base64 text part, they treat that "====" content as an error:

Caused by: java.io.IOException: Error in encoded stream: needed at least 2 valid base64 characters, but only got 0 before padding character (=), the 1 most recent characters were: "="
	at com.sun.mail.util.BASE64DecoderStream.decode(BASE64DecoderStream.java:246)
	at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:135)

The content in the mail is definitely a bit strange, but I don't know offhand whether this constitutes a minor bug in your email program or in Sun's mail parsing libraries. I haven't seen this error before, so I'm guessing it's a somewhat unique behavior by your mailer.

You could try mailing a picture again, but type a word or two into the email first ... see whether that works.

Thanks

[Verminity 0]

Okay, I just tried a message with some text in it, and it worked flawlessly!

Thanks again for the excellent support.