maemo.org - Talk - Trying to overcome some MFE limitations

maemo.org - Talk (https://talk.maemo.org/index.php)

- Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)

- - Trying to overcome some MFE limitations (https://talk.maemo.org/showthread.php?t=55867)

Trying to overcome some MFE limitations

Hi,

I am working in a corporate that allow employees to access thier work mails from outside the organisation through OWA 2007.
The problem is that provisioning is required so mfe will not do and the webmail site is too small for handling.

The following method did not work for me but might work for some one else:
1) Install IcedTea from the extars-testing and rootsh if it is not installed
2) Download davmail binaries and extract it (for BSD and other linux types not the debian one). Davmail serve as a proxy mail server so we actually set the Nokia mail client to use POP or IMAP to connect to davmail while the davmail is the one that connects to the OWA.
3) IceTea is not enough... Need to generate an SSL certificate...

Code:

keytool -genkey -alias tomcat -keyalg RSA

sudo gainroot

cp /home/user/.keystore /opt/icedtea6/jre/lib/security/cacerts

exit

4) in the terminal cd to the extarcted davmail and edit davmail.sh by replacing 'java' with '/opt/icedtea6/jre/bin/java'
5) run 'sh davmail.sh'. it will take a moment to start
6) create new mail account in Nokia Mail client and configure it to the ports specified in the davmail. click send and recieve.

In my case it got a login time out that was caused by an DOCTYPE ioexception (becuase of "). I recommend to delete the mail account definition if not in use or it will consume your phone resources with retries.

I've tried several other mail proxies written in perl and python, but this one seems to get me as far as I can go for now.

Good luck!

Re: Trying to overcome some MFE limitations

2nd attempt different method: EMOZE

i used emoze on my previous 5800 to sync with the corporate owa both my mails and my calendar.
There is a java version of emoze which is suited for old phones so i tried it with microemu.
Sadly I got a missing class exception (javax/wireless/messaging/MessageConnection).

After fixing it by running it through command line ( java -cp ../microemulator.jar:cldcapi10.jar:cldcapi11.jar:micr oemu-javase-applet.jar:microemu-jsr-120.jar:microemu-jsr-135.jar:microemu-jsr-75.jar:microemu-jsr-82.jar:microemu-nokiaui.jar:midpapi20.jar org.microemu.app.Headless /home/user/MyDocs/.documents/emoze.jar) it still did not work... I am not sure why:

Quote:

headless arguments [[/home/user/MyDocs/.documents/emoze.jar]]
org.microemu.app.Headless.main(Headless.java:112)
openJar [file:///home/user/MyDocs/.documents/emoze.jar]
org.microemu.app.Common.loadJar(Common.java:554)
Resource not found [com/openbit/midp/licensemanager/messages_en.properties]
org.microemu.app.util.MIDletResourceLoader.getReso urceAsStream(MIDletResourceLoader.java:77)
Resource not found [com/openbit/midp/licensemanager/messages_en.properties]
org.microemu.app.util.MIDletResourceLoader.getReso urceAsStream(MIDletResourceLoader.java:77)
MicroEmulator-2.0
fw.<init>(null:-1)
10:56:50,981 LicenseManagerProto.checkLicense: Applicaion mode = Free main
fw.a(null:-1)
10:56:51,220 Exception -> javax.microedition.rms.InvalidRecordIDException main
fw.a(null:-1)
10:56:51,371 m_Engine.Init(m_PM, this, ) main
fw.a(null:-1)
10:56:52,131 Exception -> bu main
fw.a(null:-1)
10:56:52,134 Exception -> java.lang.NullPointerException: main
fw.a(null:-1)
10:56:52,137 Exception -> bu main
fw.a(null:-1)
10:56:52,139 FirstLaunch :true main
fw.a(null:-1)
10:56:52,750 Exception -> bu main
fw.a(null:-1)
10:56:52,753 Exception -> java.lang.NullPointerException: main
fw.a(null:-1)
10:56:52,755 Exception -> bu main
fw.a(null:-1)
10:56:52,756 FirstLaunch :true main
fw.a(null:-1)
10:56:52,758 Exception -> bu main
fw.a(null:-1)
10:56:52,919 Exception -> bu main
fw.a(null:-1)
10:56:52,922 Exception -> java.lang.NullPointerException: main
fw.a(null:-1)
10:56:52,928 Exception -> bu main
fw.a(null:-1)
10:56:52,977 FirstLaunch :true main
fw.a(null:-1)
10:56:53,85 Exception -> bu main
fw.a(null:-1)
Init time: 49
ax.a(null:-1)

Bummer,,,

Re: Trying to overcome some MFE limitations

Does your MIDlet works fine when you run it with MicroEmulator but on the PC?

Re: Trying to overcome some MFE limitations

That was a good idea...

I tried the same method on my laptop, and it did not work as well.

But, when I tried it with version 3 instead with 2.0.4 it worked and emoze started. Did the same thing on the n900 and indeed it worked.

Code:

java -cp microemu-jsr-120.jar:microemu-jsr-135.jar:microemu-jsr-75.jar:microemu-jsr-82.jar:microemu-nokiaui.jar:../microemulator.jar org.microemu.app.Main emoze.jar

There is no calendar sync feature in the emoze version I'm using, no folders support and it has awful UI experience which does not fully cope with either the touch screen or the HW keyboard - I mean when I wanted to type a capital letter or a number I had to switch to capital mode or number mode and this makes the HW keyboard usable (atleast copy-paste worked OK).

I guess I'll be back to the drawing board for more ideas on how to access my corporate mail and sync my calendar...

EDIT:
BTW, whoever is still interested in this. it is much easier to run the midlet on the PC, configure it there and then copy all of the files from ~/.microemulator/suite-Emoze to the equivalent on the n900. The when you'll start it on the n900 it will already have your account definitions

Re: Trying to overcome some MFE limitations

i hope you crack it......its a major reason i would not rank n900 higher.......my corporate email is on another phone

Re: Trying to overcome some MFE limitations

1st method (Davmail) works well but has some flaws:

- First sync was very long (TIP: use wifi for first sync)
- Sometimes for unknown reason the JVM crash
- Needs manual run: it will be nice to have davmail starting at the boot with a init.d script

Re: Trying to overcome some MFE limitations

I finally had some time off from work so made another attempt with davmail 3.8.7.
This time I "installed" davmail to opt, set it to run in server mode (nogui) and modified the davmail script to set java.io.tmpdir to /home/user/tmp as its larger than /tmp.
The results are mixed, the memory usage of davmail is at 7-9% while the cpu is at 0% (idle) and upto 35% under a lot of requests. This is mostly good and I can leave with that.

The problem is that there are no touch friendly application that integrate to the sevices provided by davmail.
GPE-calendar says its synced with the davmail caledar I configured but doed not show any of my outlook meetings.
The builtin mail application shows the mail directories (but does not show thier content), and the inbox does refresh but only shows mails that are older than the last month (not the new ones, well only after half a day of syncs).
laws mail is not finger friendly and show some layout issues, Trojita mail fails on certificate and QTmail is not finger friendly.
Additionally, I was not able to find an application that has contact integration.
The mobile KDE PIM is not ready yet and looks like a hope in the distant future.

Any ideas?

Re: Trying to overcome some MFE limitations

Quote:

Originally Posted by damagedspline (Post 914991)

Trojita mail fails on certificate

Hi, I'd be glad if you could elaborate on this -- what problem are you having with certificates?

Re: Trying to overcome some MFE limitations

Quote:

Originally Posted by jkt (Post 915200)

Hi, I'd be glad if you could elaborate on this -- what problem are you having with certificates?

sure, the message is:

Quote:

The underlying socket is having troubles: Error
during SSL handshake error: 140770FC:SSL
routines:SSL23_GET_SERVER_HELLO:unknown protocol

Clicking Done will simply show the same message again and again and will need to be killed from the terminal...

Re: Trying to overcome some MFE limitations

Quote:

Originally Posted by damagedspline (Post 915225)

SSL23_GET_SERVER_HELLO:unknown protocol

Make sure you've selected correct port numbers and protocol in the IMAP page of the settigns dialog. Here are your options:

- If you want to use the STARTTLS feature, use "TCP" as the "Method" and check the "STARTTLS" checkbox. In this case, the communication starts in plaintext (hence you should use standard port for plain IMAP, that is, 143) and uses the STARTTLS command to transparently encrypt almost right after start.

- If you want to use SSL (and not the STARTTLS method, as described above, which is actually "the way to go"), select "SSL" as the "Method. In this case, SSL is active from very beginning, and hence you should choose a corresponding port. A default value is 993.

- Finally, an insecure method of connecting is having the "TCP" option set, but the "STARTTLS" not checked. Chances are that the server disallows login over this method, and when Trojita detects that, it transparently sets up a STARTTLS-protected channel for you.

So, in short, please make sure that the hostname, method and port number are correct. If you don't mind sharing them here, please post them so that others can try.