06-14-2011 08:53 PM
06-14-2011 11:36 PM
I've used the Playbook to acces remote email accounts with the browser. Some of these services are Outlook simulated based using only the browser.
Take care that the Playbook has no email application program in it at this time. Some remote email access sites will be expecting to see Outlook in the user's computer. This is the situation where the Playbook will not work.
For emails, most of the time I use the bridge email with my Blackberry Torch.
See if you can access your email accounts using a standard remote email client service rather than the need for a resident Outlook. The public email services, and most ISP email services work in this manner.
06-15-2011 02:19 PM
I can use the PB browser to go to https://webmail.domainname.com/owa/ , then a dialog screen is displayed and I enter my username and password and the Outlook web access inbox opens. It's worked fine for me since day one.
06-15-2011 10:10 PM
Thanks for the suggestions, folks. That is exactly what i've been doing. Those same steps let me sign into my email via outlook web app on my laptop computer. Doing exactly those same steps on the playbook somehow does not work.
06-16-2011 05:37 AM
06-16-2011 10:41 AM
I am very interested in this issue with OWA use on PlayBook. When I put in our url for OWA I get a dialog box that says:
File name CookieAuth.dll
lower down it says: File exists. Rename this file or press Save to replace existing file.
My choices are Cancel and Save. When I press either one, there is still no progress to the OWA site; don't get login screen.
Anyone have any ideas on this?
06-16-2011 11:35 AM
06-16-2011 12:01 PM
Thanks for the quick and thoughtful reply. I will look at why our OWA uses this dll format.
As for having a "mail forwarding" system, this does work but that only gets the email to gmail, or yahoo. I would like to have the full functionality of OWA (calendar, contacts, and access to do contact lookup on corp address book.)