We here live in a heavily censored country (UAE) and have all default ports blocked.
I have set up exchange SP2 for push mail but it doesnot work. Reason - port 8- and port 443 are blocked (actually transparent proxied). In OWA - I am able to circumvent this by using non default port and typing the post addres in the address bar of IE.
How do I do that on my Jasjar? How do I chnage the default port to connect to my exchange?
hm just an idea: [Exchange-Server-Adress]:[Port]
Related
Hi all, i need some help...
my push email was working fine when i first enabled it.
now i have this problem where i was getting error codes in exchange that there was a problem with the firewall timeout settings...so i changed the registry settings according to the knowledge base article...
but i still dont get a real push experience...
all i am getting it a sync when a 'heartbeat' sent.
emails are not being sent to my device at the emial arrives at my server...
does anyone know what might be wrong.
i cant remember if i had this working with the beta rom and the new official rom or just the beta rom.
My dlink firewall does not seem to have the ability to change timeout setting for HTTPS connections.
Try to delete the Exchange Server Account in your Universal, Enable DirectPush and recreate it.
- Disconnect the universal from PC.
- Delete the Exchange Account: Activesync/Menu/Options/Delete.
I suggest you manually delete your Contacts before recreating the Exchange server setttings otherwise all your contacs will be duplicated.
After you recreate & synchronize your Exchange server Account, try to Disable and Enable DirectPush.
I also had one funny issue with my Netgear router... I had to manually open ports (443&80), because the connection was timing-out on DMZ port.
Hi ... I have a problem with the configuration of my email account.
I need to change the default SMTP port 25 with another because my ISP use another ... How can I change It?
The version of my ROM is 3.30.
THNX.
ekkelon said:
Hi ... I have a problem with the configuration of my email account.
I need to change the default SMTP port 25 with another because my ISP use another ... How can I change It?
The version of my ROM is 3.30.
THNX.
Click to expand...
Click to collapse
Apologies if I am wrong on this one but don't you just add it to the end of the mail server address in options?
ie. if mail server is : mail.server.com and you want to use port 2525, then you put in:
mail.server.com:2525
I cant get this to work - anyone know if it would be possible to create a cooked rom with a given port hardcoded into the pocket outlook app?
Dave.
port 2525 sounds like a socketmail email service
nah, 2525 is a common mail services alternate port to get around the ISP's blocking of port 25.
My mail service will also use port 587.
Anyway adding :2525 after the mail.server.com works fine here.
serverort does work
I am using servernameortnum currently in WM6 on my hermes, so it does work.
I am using port 465, the secure SMTP port. that, or 587 (the mail submission agent port) is likely unblocked by ISPs, but you would have to make sure that the server is listening there, and you will almost certainly need to authenticate to the smtp server. Many servers will only allow authentication over a secure link, so you might need SSL enabled too.
I had trouble however with SSL and SMTP AUTH in pocket outlook. If anyone else does, this might be useful: http://lists.exim.org/lurker/message/20040609.135310.ba09a6e4.html
Based on that link I ended up needing to make sure my mail server started conversations on port 465 in SSL/TLS mode (rather than waiting for a STARTTLS). For anyone using Exim, that means setting "tls_on_connect_ports = 465" in your config. For people using a commercial mail server, you might just have to try lots of ports and setting permutations.
So the short version is that serverort does work, but there are other concerns as well.
note that is "colon" "p". or a dumb looking little face.
I have been trying to get my 8525 to do OTA Push Mail from our corporate Exchange 2003 SP2 server here where I work. I am the admin so I have access to the Exchange server and all settings are correct on the server itself to deal with OMA.
I can use the web browser of my 8525 and actually browse to our server and view both OWA and OMA directly, but when I configure the server through Activesync it always comes back with error code 80072ee7 (server name not resolved) error.
I am running vp3g's official v3 AT&T rom, and radio 1.48 if that matters. But here's where I think my problem lies and maybe someone with more experience regarding this can correct me if I'm wrong. We are running our OWA site on a high port number above 50000. We also have the OWA site under a subdirectory of the server. When I configure the server in Activesync, I enter the servername, port number and path to the OWA site, but once AS fails and I look at the server setting I find that it has dumped any path information and only keeps the server name and port number info.
So am I correct in assuming that M$ direct push only works with a server where the OWA site exists off the root directory of the IIS server? Or can it support paths into the site?
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
kltye said:
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
Click to expand...
Click to collapse
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
I'm with kltye... don't think push has much (if anything) to do with OWA/OMA. It runs over port 443 (https). I believe it actually starts on port 80 (http) then switches to 443, but I'll spare you the ugly details on that one. Only need to know that for firewall config purposes.
Drop the port # and path and see how that goes.
Codevyper said:
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
Click to expand...
Click to collapse
Security through obscurity eh?
I'm with vp3g as well: doesn't the https site run over 443? If it doesn't, maybe you can create a new Website and use the same settings as the original Exchange-Activesync web app, but have it listen on 443 for https. Are you able (i.e. "have permission") to open up port 443 on your corporate firewall?
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Possibly related, but do you have a trusted SSL cert installed on the server? Without that, you might have a problem connecting.
vp3G said:
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Click to expand...
Click to collapse
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
Inline........
Codevyper said:
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
60000 is probably the killer as I noted earlier that push starts on 80 and jumps to 443.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
I think it was built around 80/443 to avoid client-side firewall issues.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
You can do a "self-signed" certificate (i.e., generated by Windows Server) at zero cost. Downside is that it must be exported, copied to the device and installed.
Click to expand...
Click to collapse
vp3G said:
Inline........
Click to expand...
Click to collapse
Thanks for the help everyone. We will be building a new Exchange server later this year and I'll push to throw the site back on 80 at that time. In the meantime, I'll try the self-signed cert and see if that gets me in. Thanks everyone for your help! This site is a great resource for WinMo newbies like myself. BTW vp3g... lovin your AT&T v3 ROM. Solid and no problems overall!
BTW, I don't think ActiveSync starts off with port 80 - I was running a personal Exchange server off my cable connection whose incoming port 80 is blocked and everything worked fine using only 443. Good luck with the setup!
I am using a mail server with non-standard port numbers. Is there a way to specify which ports it should be contacting the mail server with?
Port number
After the name of server add : and then the port number. I.e. pop.gmail.com:993
Radu
Hi guys,
Question regarding email format.
When I enter my Exchange Info, I am able to select HTML format. When I send a test email through, it indeed goes through as an HTML message.
However, after awhile (not sure if it is 5 minutes or 5 hours) - the setting changes to PLAIN TEXT and the control is disabled for me to change it. If I remove my account and re-enter it, I am again able to set it up as HTML and send HTML emails. But again, it will revert to PLAIN TEXT.
My question is - is there a way to edit the registry or something that will not allow the phone to select PLAIN TEXT ??? Or what is going on ??? I have searched and as far as I can tell it is probably because the Exchange Server is older - but like I said I AM ABLE TO SET IT UP AND SEND HTML MESSAGES !!!
Thanks,
Ryan
Based on the fact that it changes and then disables the ability to change it, it sounds like it is a policy on the Exchange server.
But isn't it possible to block the Exchange from doing this ???
Possibly by making something ReadOnly ???
No. Policies are set by the server and pushed to the device. Even if you were able to 'make something ReadOnly' it would cause an error on the server and not sync.
My company enforces PIN security on phones that sync to Exchange so i need to enter a 4 digit code to unlock my phone.
thanks for the info. this is really annoying as our company email is html so when i (or anyone else) responds with our phones it jacks the entire email to text...
Exchange Server 2003 doesn't support HTML e-mail for mobile devices...and apparently that's different than the format it supports for regular connected PCs. Exchange Server 2007 has more/better support for mobile devices.
When you first set up the account it (the TP2 client software) doesn't yet know that the remote server is running 2003, but when it communicates with the Exchange server it finds out the sad truth (version 2003) and removes the HTML option. I experienced the same thing before my e-mail host switched to Exchange 2007.
But it is amazing that you can send an HTML e-mail at all...not sure how that works..?
MCbrian said:
Exchange Server 2003 doesn't support HTML e-mail for mobile devices...and apparently that's different than the format it supports for regular connected PCs. Exchange Server 2007 has more/better support for mobile devices.
When you first set up the account it (the TP2 client software) doesn't yet know that the remote server is running 2003, but when it communicates with the Exchange server it finds out the sad truth (version 2003) and removes the HTML option. I experienced the same thing before my e-mail host switched to Exchange 2007.
But it is amazing that you can send an HTML e-mail at all...not sure how that works..?
Click to expand...
Click to collapse
Yes it is amazing - that is why I was thinking there was a ray of hope that it could be forced some way...
I guess I will find out when we are upgrading to Exchange 2007 =)