My company has just moved me from Lotus Notes to OWA (Office Outlook Web Access).

Since I am a CLP (Certified Lotus Professional) I am a bit biased but trying to keep an open mind.

One thing our company did was drastically reduce the number of days an email can stay in your mailbox.

Is there a way I can archive off my mail to my local hard drive (please be aware OWA is setup by our company for web access only and I am just a user)?

I am new to OWA but maybe a desktop client of some sort could be installed or maybe there is some other way to transfer these emails locally

Thanks

Evolution can talk to OWA (in fact until recently it couldn't talk to Exchange any other way), and also supports local mail folders.

Peter

I've had luck with fetchExc. Basically works similar to fetchmail to download mail off an Exchange server via OWA.

I can't understand a company that moves from Notes to Exchange.

The only way I can see it working is if they only ever used Notes for Email/Calendar. In that case, I could see a migration working.

But when I used Notes, we did so much more than Email. I co-wrote an entire version control system in Notes. Put that in your Outlook and smoke it, Microsoft.

Frying pan/fire. Rock/hard place.

I'm sorry that you had to deal with Notes and I'm sorry that you are going to have to deal with Exchange.


I'm not sure if I'm unaware of a switch that can turn off RPC/HTTP in OWA or if you've just been told that that's all they're giving you.

Do you have a copy of Outlook? You should be able to set up Outlook to access Exchange via RPC/HTTP — that is, via the OWA web site — and use it just as if it was making a direct connection to the Exchange server. I can't really test it right now because Outlook only allows you to configure one Exchange account (Why? Because it's a piece of crap.) but you should be able to find instructions online.

Last I checked, that was only working for the 2003(?) version of Exchange, not the newer version that companies now seem to be upgrading/installing.

Ah, OK. It was some time ago that I last had to do this -- eventually I talked the mail admins into turning on proper IMAP+SSL.

Peter

Migrating mail systems is a nightmare, we're about to migrate from Scalix v10 to whatever the latest version of Exchange is. We've tried 2 tools sold for the job, neither worked for us. Looks like we'll be exporting PSTs and re-importing them, although Scalix doesn't export the message header info correctly, so more faffing...

Would have stayed with Scalix if we could find a decent support org, and the licensing costs weren't almost the same as MS now.

No help to you though.

So this time round you've made sure to choose a mail system where all the data and metadata can be exported in standardised formats?

(Actually Exchange is OK at that these days with the mail itself. But I don't know whether you can get at the calendaring and stuff with non-MS tools yet?)

Peter

Our company (over 70k employees now) has been using Lotus Notes since version 1.0. Over 20 years now. We are supposedly moving to Exchange for cost cutting reasons. But the truth is our new head of IT just hates Lotus Notes and this is the third company he has worked for and done this to. I guess the other two companies kicked him out after he made the switch.

We have thousands of apps. developed in Lotus Notes/Domino and many are having to be rewritten (Tuition Reimbursements, Time off, and our entire company Portal) and the rest are just thrown out. I sure don’t know how this is saving money.

The one application I like to brag on is my Benefits Open Enrollment app. (although that was over ten years ago). In those days all companies still used paper to enroll and it was a pain. I also created a Confidential Employee Data application that retrieved all the data our HR system and placed it in Notes. Many application in Notes where then built off this app. Employees still use it on a daily basis to check their HR data.

The archive issue and the fact that OWA doesn’t even have a user dictionary is just icing on our shit-cake.

Well I have Outlook Express. I guess that is the same as Outlook (like I said this is all new to me).

On the E-mal Server Names setup page I have it set to....


My incoming mail server is a "HTTP" server

My HTTP mail service provide is "Other"

Incoming mail (POP3,IMAP, or HTTP) server: "https://mail.MYCOMPANYNAME.com/owa


I then get the error message - "Please enter a valid HTTP server"

I thought I was. I tried removing the https and the /owa. Nothing seems to work.

No, Outlook Express is nothing like Outlook, at all.

If you are using an Exchange server you really need to be using Outlook rather than Outlook Express.

There has always been a COM interface that you could create/edit/delete mail/calendar/task/etc entries with. It hasn't always worked well and it doesn't typically give you complete access to all the fields in Exchange records, but it has always been there for third party developers to target.

No, I've made sure that we're moving to a platform which lots of different orgs can support. We're not a big firm; 25 users, expanding quickly but I can't see us having much more than 50 mail users in 5 years time. I guess we'll probably upgrade to the latest version of Exchange when the time comes. We only moved from Exchange 5.5 because we needed to upgrade and Scalix was a LOT cheaper than Exchange at the time.

Not that it helps anyone in your position, but this is why it's such a good idea to ask at job interviews what mail system a company uses, and what source-control system they use -- not necessarily because any of them are unusable (though some are), but because it's a simple way of finding out whether the IT department is operated for its users' benefit or wholly for its own benefit (or the benefit of the IT director's golf buddies). Exchange+Outlook+IMAP is a reasonable thing to hear as an answer; Exchange+OWA and no IMAP would be a big red flag.

Peter

The company I work for has been going down hill for the last five years. It was a company of high achievers and the company valued their employees. Since our direction changed to provide customer care outsourcing we are just “cheeks in seats” that are a cost to be cut.

And you are still there because?

Good $ and work from home. My department is full of good people and my manager is great. The company as a hole is not so hot.

I tried to get this to work on a Win 2000 machine. I got a ton of Classloader errors (Unknown Source). I have Java 6 so I would think I would be up to date. Maybe I need an older version or something.

Also if I get this to work, and update a local mail file, what should I view the mail file with?

Looks like Office costs and I know my company won't pay.

Looks like it might be possible.....

http://onemansjourneyintolinux.blogspot.com/2007/05/connecting-to-exchange.html

Interesting sequence of words.
MMmm.. might come in useful someday.

-ml

That's probably why MS released a totally new Exchange 2007 server, with new protocol and all.. to shut that solution out again, for a while.

-ml

At times I feel I'm in a hand basket heading down the hole

I last used it on a Mac with Java 5, Java 6 should work just fine in theory. Make sure you have the other .jar files (commons-httpclient-3.0.1.jar and others) linked off that page in the same place as the FetchExc.jar file.

It can either save to a local mbox file, or forward the mail on to an SMTP server (like GMail). I believe Thunderbird would work to read a local mbox file, though I don't know if it will constantly update, or require an import process to be run.

Rolling out Exchange without Outlook just seems like a bad idea, but then again it sounds like the whole project is a collection of bad ideas. If I was migrating away from Notes, I'd be looking at web app solutions to replace the custom Notes apps, and move the mail/calendaring/directory stuff over to standards like IMAP, CalDAV and LDAP to just let people use what they want.

Woo Hoo I'm getting closer. It seems to be connecting but then I get this....

INFO: ntlm authentication scheme selected
[Fatal Error] :1:1: Premature end of file.
IOException in fetchAll()):Premature end of file.

I've created a local mail file but I think its talking about the a file on the server, maybe.

As previously stated, it is not. I would suggest getting your hands on an "evaluation" copy of Outlook and seeing if it works and you like the way it works. If so, you can, uh, upgrade your evaluation copy.

MS should really have redone their Outlook Express and called it Entourage, because it really (really) has nothing to do with the Outlook that ships with Office. I suppose they both have "crap" in common though.

I disagree. Here's why:

Exchange means they're using the Exchange calendar, for which the only clients are Outlook, Entourage, and OWA (which is bad at the best of times, but which is awful if you're not using IE; for example, without IE, there's no email search feature).

Exchange automatically converts every text/plain email into HTML to present to IMAP users. This might be okay if it would bother to use a monospaced font.

Exchange munges RFC(2)822 emails by separating incoming mail headers from the body and reconstructing the RFC(2)822 email when needed, for example, for IMAP clients. The resultant email will look sort of like the original, but will be different. In a particularly egregious flaw, it throws away all "Resent-" headers except Resent-Mailer.

Exchange means most everyone is using Outlook. Outlook has any number of bugs, like splitting a long URL at 72 (or some other arbitrary number of) columns, without using quoted-printable's line continuation feature, despite setting Content-Transfer-Encoding to quoted-printable. In order to resolve this, Outlook would have to take the extreme tactic of adding a "=" to the broken ends. (Outlook, of course, knows about this Outlook bug and works around it, which can break correctly formatted messages with long URLs by combining them with the next line.) Amazingly, it seems no one has written a Thunderbird extension to emulate Outlook's workaround. It could work even better by only applying it to messages that have the header "User-Agent: .*Outlook". Oh, except Outlook doesn't bother to send a User-Agent header.

Oh, and Outlook automatically expands email groups into a list of everyone in the group, so there's no way to have your mail client tell you if a message from Outlook was sent directly to you or to a group you happen to be in. And I always feel like a prick doing a reply-all to a list of fifty people instead of just a reply-to-group.

Outlook also automatically converts emoticons to webdings. Of course, a smiley-face in webdings is encoded as "J", so it sends a "J", but it encodes it as us-ascii, which means that any correct email client will just display a "J".

Outlook means that if someone sends you an email that contains nothing but ":)", you will receive a 2300-character HTML blob (I counted. Okay, wc counted.) that tells you "J".

Outlook also means that everyone will be top-posting.

Outlook means forwarded messages will be in that horrible Outlook forwarding format where it's inlined without any quoting indicators, and the few headers that are included have actual email addresses stripped from them. And there's not any way to turn on any other method of forwarding. Not that the Frankenmail that Exchange generated is going to help you out anyway.

And if your IT department rolled the critical failure of Exchange plus Blackberry Enterprise Server, have fun watching every email sent to you get delivered, deleted, delivered, deleted, delivered, deleted, and delivered again, all within a few seconds. I'm pretty sure each of these has a different IMAP UID. Sometimes it'll do it again a few minutes later, leaving behind such unimportant flags as "read" and "responded" while in limbo. And if it decides to delete it while you're looking at it in Thunderbird, all sorts of fun things can happen until you reselect the new version, like it can't find the attachments, or if you forward it, it's empty. (Is this a Thunderbird bug? Yeah, maybe, but it's still egregious on Exchange's or BES's part.)

Also, IT departments are loath to support multiple clients (with reason). So when you encounter an IMAP-related problem, they're most likely going to tell you "too bad; use Outlook". This is fun when the Exchange server is rebooted and decides that it didn't need to start the IMAP server this time.

Other than that last one (and then only because I am the IT department), this is all common, recent personal experience. And I'm pretty sure there are more that aren't popping to mind. There are other serious complaints and whines.

Entourage is marginally better than Outlook. It's generally less broken, and generally has a better UI, but try to, for example, send an HTML link. Hah! Can't do it, can you? It's not as if it doesn't send HTML mail, though. You still get that bloat (though, IIRC, it's reasonably easy to turn off) but not such advanced HTML features as "a href" links.