Jez, it looks like your phone is sending the message “quoted printable” transfer encoding. And something along the way is causing it to not decode properly. Try sending an email from your phone to a regular email address where you can access the raw text of the message, and see what it looks like.
If your phone has any options to control the encoding of the emails it sends, try fiddling with those.
Thread Starter
Jez
(@jez)
Hi, I’m pretty sure that I’m unable to control the encoding that the emails are sent in, unfortunately. When I view emails that I send from my phone to my usual email address, they show up fine. Using Horde, I was able to view the message source, and got the following:
Return-path: <phone@nocturnalpulse.com>
Envelope-to: jez@nocturnalpulse.com
Delivery-date: Wed, 28 Apr 2004 14:34:05 -0400
Received: from [212.183.131.162] (helo=[10.16.3.177])
by onyx.ataraxy.net with smtp (Exim 4.24)
id 1BItsh-0005AH-SQ
for jez@nocturnalpulse.com; Wed, 28 Apr 2004 14:34:05 -0400
From: “=?ISO-8859-1?Q?Jez?=” <phone@nocturnalpulse.com>
To: jez@nocturnalpulse.com
Subject: =?ISO-8859-1?Q?Test?=
Date: 28 Apr 2004 19:34:05 +0100
Mime-Version: 1.0
Content-Type: TEXT/PLAIN;
charset=”ISO-8859-1″
Content-Transfer-Encoding: QUOTED-PRINTABLE
Message-Id: <E1BItsh-0005AH-SQ@onyx.ataraxy.net>
Blah Blah Blah Blah Blah this is a test this is a nice test Blah Blah.
Most of that makes sense to me, but I don’t know how to use it to solve this issue… Any ideas? Thanks 🙂
Thread Starter
Jez
(@jez)
Oh, and just to make it clear, the line “Blah Blah Blah Blah Blah this is a test this is a nice test Blah Blah.” is exactly as I typed it on my phone.
Think that somebody is going to have to add some sort of MIME decoding into the moblog hack to fix this. There seems to be aPEAR module that can handle the quoted-printable MIME stuff. Maybe the moblog hack author could adapt something like that into his code?
Thread Starter
Jez
(@jez)
That would be extremely helpful to me… Probably won’t happen too soon though I imagine. Oh well, looks like I might just have to sit tight for the moment.
Thread Starter
Jez
(@jez)
Hope nobody minds me resurrecting this thread, but after months I’ve still not found out how to deal with the problem. Just in case anybody around here knows the answer now?
I am in the same boat as you Jez. I have a T616 which is identical to the T610 and am having problems sending email from my phone to wp. Mine just doesn’t pick up at all. I’ll be sure to let you know if I do come across something that works though.
Thread Starter
Jez
(@jez)
Hello. Resurrecting this very old thread again, due to what I read in the 1.2.2 release post. One of the listed fixes is “email encoding issues”. Does anybody know if this includes the issue I’ve been experiencing here? I gave up with this in the end, but if it’s now fixed then that would be pretty cool.
Anonymous
In the same boat even with T630. I dont know what to do!!!
🙁
Guys, I got my moblog working 100% with my Orange SPV C500. Check out http://www.0gravity.co.uk/wordpress/index.php?cat=3 for some posts.
I used WP keitai mail @ http://unknowngenius.com/blog/archives/2004/08/23/wp-keitai-mail-plugin-v-10/
Let me know if anyone needs help …
I can’t use keitai mail.
So what’s the trick to get rof of int. chars in the subject line when using the original wp-mail.php from v1.2.2?
I’ve got keitaimail up and running on 1.5, but when I send email from my SE s710 phone, all it pulls is the subject. Works fine when I send from my computer email as plain text, but if I send from the computer as HTML, it decodes it right, but then also shows the text with the html code.
I really wanna get this up and running from my SonyEricsson phone, but am having no luck.
I guess that I am dragging this thread up again, but I am experiencing the same problem with my T610.
I was very excited about the possibility of “mobile blogging”, but it looks like I’m stuck for now.
Has anyone had any luck getting it working?
I had it working with my s710a using some modifications of some existing scripts, see here for details.
Just thought that I would let you know that I got it working using the Postie plugin which can handle HTML and the ISO 8859-1 text.
