Mail for Exchange (MfE). Blame me here, pls - Page 113 - maemo.org

Active Topics

The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 6 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 18 hrs ago
more...

Page 113 of 158

113

Thread Tools

	vitaly_repin	2010-02-08 , 13:40
	Posts: 320 \| Thanked: 763 times \| Joined on Oct 2009 @ Espoo, FInland	#1121

Originally Posted by nightfire

Hey everyone,

This is what I got from the log:

Jan 23 14:25:10 glamb-n900 activesync[1804]: MS-ASProtocolVersion: 2.5

2.5 means Exchange 2003, basically.

Jan 23 14:25:10 glamb-n900 activesync[1804]: AS-LIB: FolderSync response received (403)

Yep. Looks like infamous provisioning problem: http://wiki.maemo.org/Mail_For_Excha...Q#Provisioning

Quote & Reply |

The Following User Says Thank You to vitaly_repin For This Useful Post:
Texrat

	vitaly_repin	2010-02-08 , 13:47
	Posts: 320 \| Thanked: 763 times \| Joined on Oct 2009 @ Espoo, FInland	#1122

Originally Posted by DrubytCIO

More info... If I look at the details I do see that 244 items have been added to the calendar, however the status continues to say synchronizing and never stops. If I stop the process the changes are lost and the items never get to the calendar. I am not sure what is hanging up the process.

https://bugs.maemo.org/show_bug.cgi?id=7971 ?

Quote & Reply |

The Following User Says Thank You to vitaly_repin For This Useful Post:
Texrat

	vitaly_repin	2010-02-08 , 13:50
	Posts: 320 \| Thanked: 763 times \| Joined on Oct 2009 @ Espoo, FInland	#1123

Originally Posted by nightfire

If any of the Nokia guys are still monitoring this thread, can anyone tell me if there's still work being done to address 2003 connectivity issues?

Exchange 2003 support is introduced in PR1.1 upgrade. Yes, ongoing bug-fixing activity is happening all the time. Regarding to all the supported servers (MS Exchange 2003 and MS Exchange 2007).

If so, is there any way I can help?

As usually, via bug filing or e-mail client fixing (which is open-sourced).

Also, is the source available for the exchange / activesync stuff, or is it proprietary? I could probably fix it.

MfE is proprietary. Modest (e-mail client) is open-sourced. So, if the bugs or wrong/stupid behavior is caused not by MfE but by modest, you could help by fixing it :-)

Originally Posted by qhorse

I tells me that the Host Address is invalid on the exchange server (translation from french);

Hmm. If it tells you this, it means that it can not resolve the host address which you enter in the server name field. Try it with the browser.

Does it contain only server name or the path as well?

E.g.:

server. com - only server name
server.com/path - server name + path.

Originally Posted by nathanielsametz

Ugh, so. 102 pages of thread and we don't have a work-around for the google incompatibilities? bummer.

I can only repeat that the N900 MfE was not designed to be compatible with google. As well as google EAS implementation was not (most probably) designed to be compatible with N900. And I don't have any fact in my pocket which give me a hope that google wants to bring this compatibility on board. At least, I have never been contacted by any google server guy. So, what do you expect from Nokia engineers? To try to catch the black cat in the black room?

If server does not want to be compatible with the client, what client could do?

Originally Posted by IlkkaP

If Apple iPhone can support provisioning, I don't see a reason why N900 could not offer it.

Me too. What I wanted to say is that MfE team is not the team which shall be blamed for absence of provisioning support. Just to be clear - this is not MfE issue. This is device-wide issue.

Last edited by CrashandDie; 2010-02-09 at 12:30. Reason: multipost

Quote & Reply |

The Following User Says Thank You to vitaly_repin For This Useful Post:
Texrat

Guber99	2010-02-08 , 14:17
Banned \| Posts: 291 \| Thanked: 60 times \| Joined on Dec 2009	#1124

Originally Posted by vitaly_repin

I can only repeat that the N900 MfE was not designed to be compatible with google. As well as google EAS implementation was not (most probably) designed to be compatible with N900. And I don't have any fact in my pocket which give me a hope that google wants to bring this compatibility on board. At least, I have never been contacted by any google server guy. So, what do you expect from Nokia engineers? To try to catch the black cat in the black room?

If server does not want to be compatible with the client, what client could do?

Nokia N900: A $600 paper weight

Quote & Reply |

	vitaly_repin	2010-02-08 , 14:21
	Posts: 320 \| Thanked: 763 times \| Joined on Oct 2009 @ Espoo, FInland	#1125

Originally Posted by hypoxic

vitaly_repin, can you please clarify the following line

it is hardly advised to update to PR1.1.

Does this mean it is recommended, or is not recommended, to upgrade to PR1.1?

hardly advised === recommended. At least to my limited knowledge of the english language

Anything wrong with this?

Quote & Reply |

Freemantle	2010-02-08 , 14:21
Posts: 94 \| Thanked: 44 times \| Joined on Feb 2010	#1126

......or a small $600 digital photo frame.

Quote & Reply |

Rob1n	2010-02-08 , 14:22
Posts: 3,617 \| Thanked: 2,412 times \| Joined on Nov 2009 @ Cambridge, UK	#1127

Originally Posted by vitaly_repin

hardly advised === recommended. At least to my limited knowledge of the english language

Anything wrong with this?

It's not normal usage, no - "strongly advised" would be better (hardly is more often used in this sense to mean "not really").

Quote & Reply |

The Following 2 Users Say Thank You to Rob1n For This Useful Post:
qole, vitaly_repin

Freemantle	2010-02-08 , 14:22
Posts: 94 \| Thanked: 44 times \| Joined on Feb 2010	#1128

hardly advised, probably means it's not advised. Otherwise it would be strongly or heavily advised.

Quote & Reply |

The Following 2 Users Say Thank You to Freemantle For This Useful Post:
Texrat, vitaly_repin

	vitaly_repin	2010-02-08 , 14:26
	Posts: 320 \| Thanked: 763 times \| Joined on Oct 2009 @ Espoo, FInland	#1129

Originally Posted by 0xDEADBEEF

Vitaly, (or anyone) could you please tell us if MfE supports authentication with client certificate?

It is really hard to hide anything from the community here

Sad news first: Current MfE available for the public does not work with client certificates. At all.

Better news: we are working on this right now. This is important bug to fix as this is 100% legal use case.

Originally Posted by Freemantle

hardly advised, probably means it's not advised. Otherwise it would be strongly or heavily advised.

OK. Thanks for the clarification. Wanted to tell "strongly recommended" and told "not recommended". Funny.

Originally Posted by planetf1

Is there a way to specify the servlet URL in mfe

* I can't see any reference in GUI
* I tried adding URL after server name, don't think that's working

So is there a text file or similar created by MFE that can be manually edited?

Not as of now, sorry.

Last edited by CrashandDie; 2010-02-09 at 12:31. Reason: multipost

Quote & Reply |

The Following 5 Users Say Thank You to vitaly_repin For This Useful Post:
hstende, netmask, Rob1n, Texrat, twaelti

sjgadsby	2010-02-08 , 14:50
Posts: 5,335 \| Thanked: 8,187 times \| Joined on Mar 2007 @ Pennsylvania, USA	#1130

Originally Posted by vitaly_repin

hardly advised === recommended. At least to my limited knowledge of the english language

I think you might have confused "hardly advised" with "heartily advised". They're effectively opposites, but they sound almost the same, so it's an easy mistake to make. Your English is excellent.

__________________
maemo.org profile