Develop Bugs

Cant send Emails with Wifi

Ok when I send emails with wifi I get a message that says
From: System Administrator;
.....
.....
__________________
Your message 'RE: .............' was not send and has been moved to the Drafts folder.
The following recipients are invalid.
lookingfor [email protected] - Thats a joke.
Do you guys know why it would not work. I can only thing that the out going server address is set to my mobile provider and because I am sending it in house through a different company they are not allowing it, would this be right?
let me know, thanks

I can only thing that the out going server address is set to my mobile provider and because I am sending it in house through a different company they are not allowing it, would this be right?
Click to expand...
Click to collapse
Yes, that is the reason....
Its a pain isn't it! The only ways of getting it to work is (that I know of):
A) Use a free smtp server - most however will be classed as spam servers, so might be blacklisted
B) Use the SMTP server of the wifi network provider.

The SMTP sever will have replied 'relay access denied'. Properly configured SMTP servers dont run as open relays to stop the spamming-scum using them.
There are several methods of authentication with SMTP:
1) POP3/IMAP before smtp. The server caches your IP after a successfull IMAP/POP3 connection, and allows that IP to use its smtp server for a period of time after
2) SMTP-Auth - PPC supports this, but the server needs to also. You could try this, perhaps the host supports it - just use your pop username/password
I run my own SMTP server cause I got fed up with the sh1te offerings from ISP's. There are companies who will give you an SMTP-Auth account, but usually for a fee.
Does the likes of yahoo mail allow you to use their SMTP server - I know that they allow you to pick up yr message via POP3. I suspect they will attatch ads to the messages though!
Nigel

SMTP and change 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.

MS Push OTA Error

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!

WM6 Exchange EMail help

I am currently using WM6 and am trying to get EMail through our Exchange server setup; however, my Dash s620 will not properly save the server's address.
The address for our OWA is (ex) mail.email.com:8888/exchange
and this address works fine in Internet Explorer etc, but when I enter this into the phone it removes the /exchange and only saves up to :8888, which then gives me "Error synchronizing" when trying to connect. Our Exchange server does have Exchange ActiveSync enabled along with Direct Push enabled.
Any ideas?
Thanks in advance

I think that you have to check your ActiveSync settings on Exchange. I know that Microsoft have a lot of KB's about that.

It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?

jt76542 said:
It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?
Click to expand...
Click to collapse
Yeah I've tried every which way I could think of for the login credentials.
I'll sift through some more MS articles tomorrow afternoon, see if I can't find anything... baffled though, really.

K this is going to be a huge PITA I can tell.
I adjusted the Virtual Directory for the default web site in Exchange System manager to point directly to /exchange, eliminating the need for anything after the :8888. It works fine in IE etc, quickly brings up a login prompt. Using the phone's IE and going to the http://mail.email.com:8888 works fine, prompts a login accordingly...
I configured a coworkers Blackberry to use our OWA and it works fine, but I'm not sure if it uses Push Email (Exchange ActiveSync).
What is it about the Dash that won't mesh? The server is not using SSL so I couldn't see it being a certificate issue (maybe it still is?). Is there anyone around who manages an Exchange Server and could perhaps shed some light on common settings that need to be adjusted for Exchange ActiveSync?
Such a nuisance

ActiveSync on the phone reports "The server could not be reached. Please verify the server name." Support code: 0x80072EE7
It reports back with this no matter how I enter the address (which again, works fine in IE). Devil phone

8888 is definetly not standard for publishing ActiveSync.
the software will connect to either MailServer:80 if the SSL checkbox is cleared or MailServer:443 if the checkbox is checked.
don't think you'll get ActiveSync connect to something else.
Why don't you change your port back to 80?
you are already exposing your server to internet without any form of protection (no SSL so your password can be sniffed over the network) and having port 8888 buys you nothing in terms of security since any port scanner will report the port as opened and eventually get the HTTP banner from the IIS Server.
So, get back to a standard config and you'll love your DASH again.
UM

[Q] Android revolution hd Activesync issues

Hey all.
First off, i hope someone will see this, as i dont have enough posts yet to post in the correct forums.
I recently flashed ARHD 3.2 and its been working great. The only problem i have found is that my activesync account will no longer sync. So i tried deleting it, and recreating it. When i get to the last screen it says there was an error creating the account, and in logcat it shows error 451.
Now from what i have googled, it says 451 is:
Exchange ActiveSync returned an HTTP 451 response. (Device Misconfigured)
And something along the lines of activesync thinks there is a better server for me to connect too.
But when i was running arhd 2.x activesync was fine.
Can anyone shed some light onto this ?
Other info:
Server address: Outlook DOT com
username: mpd50 AT uclive DOT ac DOT nz
domain: uclive DOT ac DOT nz
ssl: yes
Damn, anti spam measures

is it true the server address is outlook .com ?
normally it is webmail.uclive.ac.nz something like that.
maybe you can try :
Server address:
username: mpd50
domain: uclive.ac.nz
ssl: yes
or you can set it manually (click on set manually) after you enter the username and password.

The only reason i used outlook.com was because in outlook 2010 on my laptop, the server it connects to is an outlook one.
When i try uclive dot ac dot nz as the server, i get authentication failed. But with outlook dot com, i can get right to the end, but not past finish setup.
Oh well, ill keep trying every few days... or wait for an update from mike.

Ok, I managed to setup the account on my computer fine, so I copied the server it used to my phone and that seems to have done the trick... looks like android is not selecting the correct exchange server, and you have to enter it manually yourself.