My network provider currently has a very small whitelist for which User Agents can access the Internet through the GPRS (Web only) service. Opera on my Touch HD didn't make it to the list, but I managed to modify its user agent to HTC_TyTN_II and now I'm good to go.
However, push mail doesn't work too. Is there a method to modify the User-Agent which is sent in the HTTP headers of Pocket Outlook's push mail client? It is, after all, HTTP traffic.
Any ideas?
Related
I cannnot acces to my email un gmail.
I'll really apprecaite if somebody can give me all parameters
I have 3 Gmail invites available
I was able to access my Gmail on XDA II. I now have an XDA IIs with 2003 se. I used the same parameters as on the XDA II 1.72 but I am unable to access my gmail. It seems to log on but stops in the downloading process.
Sorry, but I just realized that the problem I was having with my gmail account was not due to using 2003 se but because apparently (I don't know how) the settings on my gmail account had changed.
Here are the instructions that helped me from http://www.pocketpchow2.com/archive/2004_11_14_index.html
Update: Using Gmail from Pocket PCs
Earlier I had written here about how Google has started providing POP access for their Gmail email service. This week my account was enabled for POP access, and since then I had been trying to get it working with my Pocket PC. My efforts had been stymied by an error stating that email could not be downloaded to my mobile device. Today thanks to some assistance from Ed Hansberry got it to work. The trick is to enable POP only for new mail rather than for all mail.
If you have a Gmail account and want to access it using your Pocket PC, here is the information that you need:
Your userid and password is the same as what you use to access Gmail via a web browser
The incoming mail server name is pop.gmail.com
The outgoing mail server name is smtp.gmail.com
You need to configure the account so that the Outgoing e-mail server requires authentication
The account also requires an SSL connection
If you read Google's instructions for setting up an account you will notice that they specify port numbers for the incoming and outgoing mail servers. The numbers they provide are the standard port numbers for SSL access, so all you need to do is configure the Pocket PC account to use SSL.
You specify the authentication and SSL connection information on the 2nd account options screen. To access that screen tap Options on the fourth E-mail Setup screen and tap Next to display the Options (2/3) screen.
Since Gmail is free and provides 1 GB of online storage for email, it is a very useful email service. What makes it even better for Pocket PC users is that it requires SSL, which encrypts all your email as it travels between your Pocket PC and Gmail's servers. Keep in mind that when you use regular email servers that don't use SSL via a wireless connection, your email is floating through the airwaves in clear text. That means that anyone with the ability to capture wireless traffic can see the contents of your email. I highly recommend that since most people access email via wireless connections today, they use some form of encryption, whether that is provided by VPN or SSL.
I have done a search on this site and HOFO and cant seem to come to a solution. I'm about to go crazy.
I know my company uses Microsoft Exchange. I also have webmail access for my email as well as VPN access.
At this point, I'm unsure what to do with all of the info. I was hoping some of you could help me out. I am on yahoo messenger as curiosity7277466 or I am definitely open to calling you or talking via email. I have been really looking forward to making this work. Hopefully someone here can make my first post here a success. Thanks!
Rudy
it's pretty easy.
*IF* your company has an Outlook Web Access (OWA) Email Server setup so that you can access webmail from the net, you should be able to setup your outlook/exchange email as well.
I bought my 8125 a few nights ago - and while sitting in the store, entered my OWA info and, boom, had my contacts, email, etc. within a few minutes.
Open ActiveSync on your device and click on menu/configure server.
enter your server email address - it should be in the format of mail.doman.com. so, for example, it could look like one of the following:
mail.xda-developers.com
inetmail.yourcompany.com
The point is it will use the same web address that you use for webmail from outside the company. If you use https://mail.xda-developers.com to gain access to your OWA, you'll use mail.xda-developers.com as your server address. You'll likely need to select the SSL connection.
Hit next.
Your use name is your Active Directory user name. The password is your corporate password; and the domain is your AD domain.
You may typically know your user credentials as domain\user name, yet you do need to keep the separate on this screen. Enter user name, passowrd, and domain. Click on the save passwork box.
Hit next. Select your preferences and hit finish.
that's it. you're done.
enjoy.
The key question is which version of Exchange is being used, and what has been exposed to the Internet.
Browsing to Outlook Web Access is the usual clue. Exchange 2003 OWA looks very different from the previous versions - it is very similar to Outlook.
First thing I would try is OMA - Outlook Mobile Access. You can try it from a desktop before you start playing around with your handheld.
https://servername.domain.com/oma
You should get a prompt with username and password.
Enter your username in the format of domain\username and then your regular domain password.
You should then get a list of options in plain text. You can now read your email etc.
Move over to your handheld and enter the same URL and the same thing should happen.
If that doesn't work then you will have to speak to your Exchange administrators to see whether the options have been enabled. There are a number that aren't enabled by default which can stop OMA working.
As Exchange Active Sync works through the OMA virtual directory, if OMA doesn't work then I would be surprised is EAS works.
Exchange ActiveSync setup is as previously posted - but without support enabled on the server, it will never work.
Simon.
The best bet is for you to call your help desk. They may not know but they could probably open a ticket to the Exchage team and you will get a correct answer from them.
There are many different ways to expose the Exchange Front End server to the internet that just guessing will drive you crazy. Some companies expose the whole exchange web directories and other only expose OWA
With all the Firewall Settings Web Proxies and ISA configurations out there it will be hard to tell if you can use Active Sync.
URLs follow this method of connecting to the different IIS Web inerfaces of Exchange
mycompany.domain.com/exchange = OWA
mycompany.domain.com/OMA = WAP based OWA
mycompany.domain.com/ActiveSync = is for ActiveSync
So they have to expose ActiveSync to allow you to use it.
[/img]
I would like to kno if anyone in xda was able to address the problem with the wm5 client address on a forum i read about, i beleive i am havin the same problems
"the Pocket tv team"
we found a bug with the Windows Mobile Email client that prevents using
certain SMTP servers.
i suspect the bug is general to all Windows Mobile devices including Pocket
PCs, but we only tested it and confirmed it on the Motorola Q (a Windows
Mobile 5.0 Smartphone).
the bug prevents using some login names on SMTP servers (i.e. outgoing
email) that require a user name DIFFERENT from the POP3 ou IMAP4 server
(i.e. incoming email) and when the login name is something like
'[email protected]' i.e. when the login name contains an '@' sign.
this type of server login name is common on servers that use shared domains
on a single IP address, and this is a common case. in this case, since
there may be several users with the same name under different domains (on
the same server), the correct user is identified by using the domain name
with the '@' sign.
in fact i found that bug by trying to configure the Motorola Q to use one of
our email servers to send my email.
what happens is that the Smartphone email client removes the @ sign and
everything that follows it when loging to the SMTP server - we confirmed
that by looking in real time in the log files produced by our SMTP server.
i am not aware of any workaround.
the problem does not happen when the SMTP server uses the same login name as
the POP3 or IMAP4 server (in that case, the login name can have an "@" sign,
and it is handled correctly). the problem only happens when the SMTP server
uses a different login, and that this different login has an "@" sign.
once again, MSFT was apparently trying to be "smart" i.e. they assumed that
the @domain part in the login name of the SMPT server was entered by mistake
by the user, but being too smart is not always a good thing.
note that using fully-qualified user-name that include a mandatory @domain
part is very common and even google's gmail uses this, as you can see in the
'Account Name' section of
http://mail.google.com/support/bin/a...y?answer=13287 .
if you use gmail to both receive and send email, it will work, because the
POP3 and SMTP servers use the same login. but if you want to use gmail just
to send (i.e. SMTP), and use another server to receive (i.e. POP3 or IMAP4),
then it won't work, because of that bug.
this is a pretty serious problem.
also, the IMAP4 client configuration does not allow to specify the remote
directory (in the user's account on the IMAP4 server) where the IMAP folders
are located, which may be different from the default login directory. This
renders IMAP4 completely un-usable in some cases.
Of course those bugs are not new to Windows Mobile 5.0. It's just a shame
that MSFT never fixed them.
Click to expand...
Click to collapse
I recently got this email from att yahoo:
Dear AT&T Yahoo! Member,
We're making some security improvements to your AT&T Yahoo! service. These changes will affect members who send or receive email from a desktop or mobile client program, such as Microsoft Outlook, Microsoft Outlook Express, Eudora, Apple Mail, or Thunderbird.
To help us ensure the security of your email, you will need to change the settings on your desktop or mobile email client program.
you may take the following steps to change the settings on your desktop or mobile email client program:
Open your email client program.
Locate the email account settings for your particular client.
Change the POP server to pop.att.yahoo.com.
Change the SMTP server to smtp.att.yahoo.com.
Check the option labeled Use an encrypted connection (SSL) and change the SMTP port to 465.
Check the option labeled Use an encrypted connection (SSL) and change the POP3 port to 995.
Confirm the above settings then click OK.
I already tried my first comandment "Thou shalt not ask before search!" but alas I can't seem to find how to change ports on e-mail set up. I'm running wm6 but I don't know if wm5 had this abbilty as I didn't need it then. Any help would be great!
So, mabey I should have posted under wm6 & titled the post photon question. At the very least somebody would reply to flame me or something. lol
I had the same problem. Turned out to be the operator. They do not offer full Internet services, only WAP and unencrypted e-mail (i.e. no SSL). The problem sorted itself out after switching to another operator . . .
Add a colon then (port #, no spaces) after each in/Out server. That is how I have it set up with my 8525/ wm5
Thanks, I'll give that a shot. If not I guess I can open a hot mail account and forward email till att fixes the auto set up in August (per the "help" desk)
Push mail in Outlook Mobile sends its requests to the Exchange web server with the user agent: MSFT-PPC/5.2.1604. (Build number changes, of course).
Is there a method to modify this user agent? I can't find any registry reference to it. I need to change it because my network provider allows only certain user agents to pass through (silly security measure) and it seems like MSFT-PPC isn't on the white list.
I'm using WM 6.1 on a Touch HD.
Update: I resolved the issue with my network operator by allowing the user agent after hours of convincing. Mods, delete this topic or keep it if it could ever be useful if answered...