Re: Mail for Exchange (MfE). Blame me here, pls
 

Thank you.
In your experience would we expect to wait days or weeks,months for that type of update? I have no experience of this stuff and I can't have a phone that doesn't have this feature. What do you reckon? Thank you so much for your patience with me.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hey andre, you said

Probably the N900 tries to support Exchange 2007 fully, but there's something that's called a software bug... It's quite likely as I have not seen an application yet that was completely free of errors. ;-)
__________________

errr would it be too much to ask, to see your folders that include the emails???? and then the emails inside the folders...

Is it not this the reason, we use exchange?

You can call it a minor bug if you want, I take it you do not use exchange?

Re: Mail for Exchange (MfE). Blame me here, pls
 

The rumour is that there is a 1.1 release due around Christmas, who knows what goodies might be inside. May be it depends on whether you have been a good child or not over the last 12 months ;)

Re: Mail for Exchange (MfE). Blame me here, pls
 

As not being marketing guy, I am not allowed to communicate any maemo plans. Sorry.

I think the same :-) And I see the HUGE interest to sync with google in this thread and in this forum in general.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Yes. To be precise - not all the emails but the e-mails which are in sync window. Typical choice is "2 weeks" but there is an option "sync everything" as well.

Subfolders are supportedl. Of course, they shall be locate d in the server, not in your desktop computer. But I believe it is obvious for everybody here.

The same story as with the google in fact. You can be lucky but that's all. Typically you unlucky.

Wait for sw. update as I have told several times here :-) Our marketing guys will communicate more information in the right time.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Um. Which part of 'community development' doesn't make sense? How's anyone supposed to get even slightly involved if you won't even tell people what you're working on?

This is not a marketing issue.

Re: Mail for Exchange (MfE). Blame me here, pls
 

/Just a side comment. N900 MfE does not sync your IM contacts. It syncs only your "real" addressbook. And I believe this is right behavior as skype, gtalk, other IM contacts belong to the servers other than MS Exchange.

Re: Mail for Exchange (MfE). Blame me here, pls
 

I guess that the MfE part needs some work together with MS and as such doesn't fall under the "open" or "community" part. Understandable, if you want to support Exchange.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Software update is a new firmware which you can install on your device.

S60 does it in this a way: http://europe.nokia.com/get-support-...oftware-update

maemo way: http://www.maemo-guru.com/2009/11/ho...900s-firmware/

Update. The really "nice" maemo way: http://www.youtube.com/watch?v=At9tJHmgnrE

Re: Mail for Exchange (MfE). Blame me here, pls
 

The canonical source for Maemo is: http://wiki.maemo.org/Updating_the_tablet_firmware :-)

Re: Mail for Exchange (MfE). Blame me here, pls
 

i see your point but .. i dont completely agree
If i sync then for me thats a backup. Now lets assume that i somehow loose all the data on the N900 then i want to sync back and everything should be as it was.. I am merging contacts for days now over gsm/googletak/skype and msn... I really dont want to do that anymore... So it doesnt have to sync certain fields but it should know the connection...

But maybe i misunderstood and is a sync to something external not a backup..

Re: Mail for Exchange (MfE). Blame me here, pls
 

http://www.sherweb.com/hosted-exchan...-2007-features ?

Than this is a bug in our stuff. I would be more than happy if the guy can send me the logs of the connection. The best way to do it is to use maemo bugzilla: https://bugs.maemo.org/ I will be happy to have a bug there, track it and fix it.

Simpler. Most probably, N900 MfE has a bug. Most realistic case. Yes, Don Knuth is not a member of our team and (more important) we didn't have the same time to develop MfE as he had to develop TeX and MetaPost. And we have to communicate with the server which is not under our control, by the way.

Pls, file a bug in bugzilla, put me in cc or inform me about the bug id in any other way (including private message). We will investigate the issue and fix it in one way or the other.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Stop attacking developers and understand that you should complain to managers. Things are more complicated when it comes to cooperates.
If I was a Nokia developer, attacking Nokia developers is exactly the behaviour that would make me stop spending time to talk to the maemo.org community here.

Re: Mail for Exchange (MfE). Blame me here, pls
 

It's not a rumour. See http://talk.maemo.org/showthread.php?p=390705

Re: Mail for Exchange (MfE). Blame me here, pls
 

Maemo way is to wait that Application Manager tells that there is update available, you click install and that's it.

Flashing tools and NSU are just alternative and much harder way to do update firmware.

Re: Mail for Exchange (MfE). Blame me here, pls
 

When was the event in that photo?

If it was a long time ago, who knows if it's still valid. It could be pushed back.






Video:

http://www.youtube.com/watch?v=At9tJHmgnrE

Why do the NSU update vitaly? Isn't this way better?

Re: Mail for Exchange (MfE). Blame me here, pls
 

But there is one project which is very close to this target:

http://en.wikipedia.org/wiki/TeX


The number of digits after the dot sign in its version number is equal to the number of bugs found during its lifetime.

So, the fun starts:

$ tex --version
TeX 3.1415926

Count it yourself :-)

Unfortunately, it is near to impossible to reach this target in the modern industrial software engineering. But all the sw. engineers shall not forget about this real example :-)

Re: Mail for Exchange (MfE). Blame me here, pls
 

Yes. And the link I have posted tells about SSU as well.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hint: I directly wrote the event name in the line above that photo. ;-)
(October 2009.)

Re: Mail for Exchange (MfE). Blame me here, pls
 

No. I have posted a link which describes all the alternatives.
SSU is how the typical Maemo user does it.

Re: Mail for Exchange (MfE). Blame me here, pls
 

There was too much for average user to read

Re: Mail for Exchange (MfE). Blame me here, pls
 

There are a number of people posting to and reading these boards with better access to Nokia managers than I have, not least, the developers. It seems simplest, most honest, and common practice in an open community, to speak in public.

If you or any of the other Nokia staff would like to draw your managers' attention to the negative results of their policies, you can point them at this thread and many others.

I can't.

Edit: I'd also take issue with the idea that Plenty of developers from Intel, Novell, Redhat, IBM etc. seem to manage to work in public on open mailing lists etc. Nokia's hardly unique as a company working with free software.

Re: Mail for Exchange (MfE). Blame me here, pls
 

I think the point is that the IM contacts are already stored on the IM servers, and that is the best place for them to live.

I understand what you mean about merging them, though, as I can imagine it being annoying to have to redo that if you had a disaster. I guess the problem is that the merging is a concept only understood by the N900 itself. (Of course, there will be ways of backing up everything on the N900, including the contact merge info, but that wouldn't be synced up to the IM provided or Exchange server, that's all.)

Re: Mail for Exchange (MfE). Blame me here, pls
 

Perhaps, but you have roamed now from specific MfE issues to generic whining. If you don't like how community is handled go another thread, and let people who want to make MfE better keep this thread as direct communication channel to MfE devs?

IMHO The lack of active moderation here makes make talk almost useless. If some moderator wakes up and decides to clean this thread, feel to remove my post as well.

Re: Mail for Exchange (MfE). Blame me here, pls
 

do you know what you're talking about here?

exchange is a microsoft product, and microsoft is not exactly known for their good relations to open source devs.
there is no community implementation of activesync (at least none that i'm aware of), nokia has to pay hard money to license the protocol needed to sync with exchange.

if you want to reverse engineer the interface, be my guest. but don't expect nokia to support you in this semi-legal undertaking.

Re: Mail for Exchange (MfE). Blame me here, pls
 

And you really think that will change something to the positive?

Most of these companies have a long tradition of opensource or bought in companies (and their cooperate culture) that always have been opensource (in case of Novell: Ximian and Suse).
In Nokia, many managers and developers come from Symbian, for example the S60 series. Not all of them are used to interacting and talking directly to a community, and it takes a while to convince everybody that there's **advantages**.
This transition to an open culture does not become easier when developers get immediately attacked on the first day they join the community for stuff that is SIMPLY NOT THEIR FAULT.

I hope it's a bit easier now to understand the situation with Nokia and that the comparison to the other big companies you listed is not that similar as it initially looked like.

Re: Mail for Exchange (MfE). Blame me here, pls
 

M4E is built into the e-mail client, just the setup is not. In fact that's part of the problem. The standard e-mail does not offer search or copy and paste. Since Exchange synced messages display in that e-mail client it is a problem. So the fix will involve the e-mail client team to fix the client itself and the MFE team to implement more reasonable sync periods (2 months, 3 month and 6 months) and also implement server search. Also they could work together to build the M4E setup into the mail application.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Somewhat off-topic, but is there a video posted anywhere of the Summit's speech? (The speech that contained the photo you posted)

I found this:
Maemo Summit 2009 Opening
http://www.youtube.com/watch?v=dqsMAkKrXJ8

But it ends RIGHT when the person starts speaking :mad:

Re: Mail for Exchange (MfE). Blame me here, pls
 

And in the case of Nokia, Trolltech.

Did they miss the bit where you were given most of your latest OS by other people for free?

I'm not sure what would encourage Nokia to open up any more than pointing out the problems in not doing so, but I'm completely open to suggestions.

It looks pretty similar to me. Nokia appears to be planning a migration away from Symbian to a Maemo, they've bought Trolltech, and (more or less) opened the Symbian code for good measure. You're a free software company now, and it is to everyone's advantage if you can try to act more like one. I really do want Maemo to be a roaring success for Nokia, but it's frustrating when the community is locked out of the bug tracking system, when test builds aren't released externally etc.

We've had reports of various firmware bugs, this one included, that have only come to light once the devices were out the door on the mass market. If there'd been more of an effort to engage the community in testing that simply wouldn't have happened. That's the advantage, and it's Nokia's for the taking, if they want it.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hi Vitaly_repin ,

thanks for your candid posting on the status with Mfe , I also have this issue, using certificates and exxchange 2003, would an additional syslog trace help yourselves in this matter ? I'm more than happy to generate one if it would be valuble (really would like to see this working)
Rgds Steve

Re: Mail for Exchange (MfE). Blame me here, pls
 

Many, many bugs were filed by early users and the 'Summit 300' well before sales start, so I really do not think you know what you are talking about here. These bugs included the ones regarding MfE.

Vitaly, I apologize for this off-topic post in your well-meaning thread.

Re: Mail for Exchange (MfE). Blame me here, pls
 

What would be on topic in this thread exactly? Discussions of the development of the Exchange sync feature? It's not the off-topic posts that are blocking that.

FWIW I'm sorry if Vitaly is feeling got at; he's clearly trying to do entirely the right thing, I just wish he was wasn't being stopped from doing it by his management.

Re: Mail for Exchange (MfE). Blame me here, pls
 

? But it IS! You can launch mfe setup wizard from 2 places - control panel and mail client. In the later case you just select "New account" and select "mail for exchange" as account type. What's wrong with this? Is it not obvious for end-user?

But remember - only 1 account of type mfe can be configufred in the system. If you have one account configured already, mfe will not be listed in the list of account types.

It also means support from serrver side. I need to check the specs before answering is it (more reasonable sync periods, as the situation with search is clear) feasible or not.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Maybe you should check more carefully. M4E is not a selectable account type.


If Roadsync can do it on S60 and Android, and Apple can do it on iPhone I don't see any reason why you cannot. Even 1 month with server search is fine. If you don't know that the competition has server search then it would behoove you to try some other devices to get some perspective on what you are competing with.

Re: Mail for Exchange (MfE). Blame me here, pls
 

I have opened a new bug.
https://bugs.maemo.org/show_bug.cgi?id=6349

My problem is that whne you tap on a new email notification, the email doesn't open up, but it opens a blank email

If you experience this bug, please vote

Re: Mail for Exchange (MfE). Blame me here, pls
 

Yes sometimes it happens.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Lucky you! It happens always to me!

Re: Mail for Exchange (MfE). Blame me here, pls
 

I don't have my device yet, but Vitaly said after setting up an account, it won't allow you to do another. Could it be you don't see the other setup option because you've already set yours up?

I'm curious on this one, myself. Is SR overlooking something, or is Vitaly mistaken in the Mfe setup implementation? No one's perfect. But what are we talking about here, user error/overlooking or Maemo/Mfe setup features missing that they believe or expect to be there?

No need to bring up competition. I don't think Maemo is about winning a race. They want to serve the users. Try to focus on showing how useful the features are to YOU and others, not Apple and other "competitors".

Apple has a great fart simulator as well, which means nothing to Maemo if users don't find it useful. But if someone needs a fart simulator for a mission critical task, it makes more sense. So explaining use cases where it is needed is far more helpful.

I'm SO glad you're here, btw, SR. You're giving some good input different from what others are saying.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Vitaly, thank you for introducing the topic and for making your interest known.

Does "mfe and related components" include imap-idle? I've already voted for #3888 and added myself to the cc: list, but it would be well appreciated if you happen to know the proper person to nudge to make this happen.

Re: Mail for Exchange (MfE). Blame me here, pls
 

http://www.flickr.com/photos/vitalyr...57255431/show/

Are you sure you don't have any MfE account configured already?

Server search - there is no question about feasibility. I mean, it is feasible.

Currently supported sync windows: 1day, 3 days, 1 week, 2 weeks, 1 month (!), All messages.

And as far as I remember this list is done in this a way not (only) because of User Interface designers but also because this is the list supported by Exchange. 90 days was requested and I am unsure this is supported by Exchange.

I know, trust me. I have tried all the available competing solutions on the market. This is part of my job.