Hi,
This post might be usefull for people trying to pop mail from a Mac OS X server 10.5 (which is Cyrus POP3 v2.3.8-OS X Server 10.5).
I setup a pop3 account (over SSL but that doesn't matter) to connect to my OS X server but Pocket Outlook on a Windows Mobile 6.1 refused to download any mail, always displaying the standard error message.
I decided first to troubleshoot this by setting up a socat tunnel in order to display what was happening under the hood between my Windows Mobile device and the server.
The setup is as is:
Mobile device <-----> test server running socat <-----> Mac OS X server
The socat command used on the test server is:
socat -s -d -d -d -v TCP4-LISTEN:65432,reuseaddr,fork TCP4sxserver.com:110
On windows mobile device I then used testserver.com:65432 as pop3 server.
I logged the traffic between the device and my pop3 server and here is what I found:
Code:
+OK macosxserver.com Cyrus POP3 v2.3.8-OS X Server 10.5: 9C31 server ready <[email protected]>
CAPA <----- sent by mobile device
+OK List of capabilities follows
EXPIRE NEVER
LOGIN-DELAY 0
TOP
UIDL
PIPELINING
RESP-CODES
AUTH-RESP-CODE
USER
IMPLEMENTATION Cyrus POP3 server v2.3.8-OS X Server 10.5: 9C31
.
AUTH <----- sent by mobile device
+OK List of supported mechanisms follows
SMB-NTLMv2
SMB-NT
SMB-LAN-MANAGER
MS-CHAPv2
PPS
PLAIN
OTP
LOGIN
GSSAPI
DIGEST-MD5
CRAM-MD5
WEBDAV-DIGEST
DHX
APOP
.
Then.... quits !!!
Replaying manually this dialog I finally ended up understanding that when the Mac OS X server was replying with "GSSAPI" to the AUTH command, Pocket Outlook decided to quit without notice. (GSSAPI is Kerberos.)
Making changes to my Mac OS X server config was not an option (I could have removed GSSAPI from the sasl_mech_list in imapd.conf, but Kerberos is used for the IMAP protocol).
Microsoft and Apple are both to blame here, because the protocols listed in the AUTH command by the OS X server are bogus (they list every protocol even is they are not supported). And Pocket Outlook should not die here. Maybe there is some Kerberos support problem in WM6.1?
Anyway, as the AUTH command sent by the device is not mandatory for the POP3 protocol to work, I just decided to hack Pocket Outlook to not send this command.
After decompiling tmail.exe (pocket outlook mail program) I tracked down to the mailtrns.dll file which in charge of the POP3 / SMTP protocol.
Then all I had to do is change the AUTH command to XXXX in order to solve the problem (with and hex editor). There are several AUTH string in the file, the good one is the one just after the CAPA string.
The mailtrns.dll file is stored in ROM so I could not replace it. The solution was to edit the registry and change the following key:
HKLM\Software\Microsoft\Inbox\Svc\POP3 and change the DLL entry to "mailtrns2.dll". Then copy the patched DLL to \windows\mailtrns2.dll
Then reboot, delete mail accound and add new one (just modifyng won't work has account property is tied to older registry entries).
Hope that this will help users wanting to POP mail from a Mac OS X server!!!!
Please also find attached patched file, to save you time from dumping ROM!
Enodr.
-----
Keywords: Windows Mobile 6.1, WM6.1, POP3, SSL, Mac OS X Server 10.5, Cyrus POP3 server v2.3.8-OS X Server 10.5, Pocket Outlook, tmail.exe, mailtrns.dll, problem, cannot connect
Related
I'm trying to synchronizise with the exchange server at my work.
But for some reason it doesn't work. I've filled in everything in the right way (address, domein etc.) the fault code is 80070002.
Can somebody help me with this?
same here at home (no firewalls)
Works fine for me. Exchange server needs just some configuration.
Priit said:
Works fine for me. Exchange server needs just some configuration.
Click to expand...
Click to collapse
What kind of configuration?
First, your Outlook Web Access (yes, OWA!) can not use forms based authentication nor SSL encryption. If you don want to use these (you most probably want to use SSL) then you need to create another virtual OWA directory without SSL and force ActiveSync (and Outlook Mobile Access) to use it.
More information at
http://support.microsoft.com/default.aspx?scid=kb;en-us;817379
Check if you can access OMA (Outlook Mobile Access) using http://yourserver/oma and check also Exchange server logs.
I thought this wasn't supported on WM5 until AKU 2.0 comes out (hopefully soon)
So ur saving I have to turn Forms authentication off and ssl off on OWA for my mobile device to work ?
sounds a bit of a poor show.
I need Forms based auth ideally as it goes through firewalls where as the other type does not.
Ours works here and we use SSL.
For the server name make sure you are using the fully qualified domain name that you use from the internet. IE: mail.domain.com. You don't have to put the /exchange on the end.
username, password and domain are all the same as what you use to log in.
OH, and the certificate you use on the server should be for mail.domain.com and not servername.
Hope this helps.
@spartanrob: DirectPush needs AKU2.0. You have always had possibility to sync manually. Or if your operator provides e-mail to SMS then you have the same functionality already today.
@Karzi:
No, I'm not saying you have to turn off SSL and/or forms-based auth., but you need to create another virtual OWA directory, which does not require SSL and forms-based authentication. You can limit access to this directory to localhost only so there will be no security concerns.
@MrHappy:
Your server is probably set up in that way.
Please go read this it helped me with the same error
http://hardware.mcse.ms/archive35-2005-11-248477.html
Basicly says that you have to download the cert from https://server.domain.com/certsrv then install the certificate on your desktop and your handheld then activesync will work....
I was hesitant but it worked for me.... it changed the path in the cert from my ip to my server.domain.com
Heres a question for u: is it possible to connect to my exchange server using activesync via an RPC over HTTP connection? Currently i have to dial a VPN connection before connecting which is rather cumbersome (having to dial and it frequently drops). It is available in Outlook and is much more efficient. Cheers.
I am assuming that you are running an exchange 2K3 SP2 and Windows Server 2K3 SP1 right off the bat. If you are not this info may not apply.
When you install Exchange 2003, several virtual directories are created under the Default Web Site in Internet Information Services (IIS).
One of those is "Microsoft-Server-Active-sync" If I am not mistaken this is what your PPC uses when syncing. So you don't need to setup your PPC to use RPC over HTTP like you would outlook (with the http address, and the internal server name, and the MSSTD crap). Check to make sure your front end server (Web server) has that virtual directory in the default web site. If not, there are quite a few tutorials on Google that you can look up.
Hope that helped.
Later; Lew
http://www.google.com/search?hl=en&lr=&q="how+to"+install+"Microsoft-Server-ActiveSync"
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
When you are setting up a new server source in AS, it has some options for doing things automatically (I assume based on our email domain name). This has never worked for me (I am the sys admin for our Windows network). Do I have to be running Exch2007 to get this functionality, or is it some sort of DNS issue that is making this fail? The front-end server that we use is not mail.domain.com We use webmail.domain.com.
Any thoughts are appreciated. We are going to be allowing our users to bring their own service and devices to our cell phone mix, and I want to make connecting with WM devices as easy as possible. I'm trying to reduce the number of blackberry devices we use.
Thanks!
Brandon
Microsoft Exchange 2007 Autodiscovery
Autodiscovery allows a user to enter their email address and password into Outlook 2007 or Windows Mobile 6 Pocket Outlook to have their profile or activesync relationship automatically configured to access an Exchange 2007 server.
In short, you add a DNS record for the host "autodiscover" in the domain you want to use Autodiscovery in. If you want it to work internally just add it to your company's DNS server. If you want it to work externally you have to add it to your external DNS server.
One important note is that you must have a multi-domain SSL certificate from a known public provider. This is because you need 4-hosts on the certificate (2-domains with 2-hosts each) I purchased a multi-domain certificate from GoDaddy.com for $58 for 1-year.
Search keywords: +Exchange +2007 +Autodiscover
Hi,
I have a HTC TyTN ll and I am having problems synchronising my work email.
The server at work has exchange 2003 SP2 and Activesync. We also have both OWA and OMA and I can access these succesfully through the PDA.
The OWA/OMA both use SSL and have a instantssl certificate installed which I have downloaded and installed onto my device.
My credentials are correct, I have recreated the data source and resetted device but..
During snychronisation on the PDA I get the following error:
"ActiveSync encountered a problem on the server" Support Code: 0x85010014.
Following a google I found that this is as a result of having the SSL port 443 defined in IIS for the webmail site. Now if I remove this port I get the message "waiting for network". I have read this is temporary, but I have tried for the past few days and it still doesnt get past this stage. I am using our wireless and the GPRS as provided by orange to connect.
Also removing the port 443 has concequences on anyone else accessing the OWA as it does not work.
Do any of you guys know any ideas on how I can get the PDA to synchronise?
Will I have to first create an activesync partnership with the server?
Many Thanks in Advance
I now recieve the following error on the server:
Exchange Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=817379). For information about how to properly configure IIS to support Kerberos and NTLM authentication, see Microsoft Knowledge Base article 215383, "How To Configure IIS to Support Both Kerberos and NTLM Authentication" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=215383). This issue may occur after installing Windows SharePoint Services on a server running Exchange Server 2003. For information about how to properly configure a server to run both Windows SharePoint Services and Exchange Server 2003, see Microsoft Knowledge Base article 823265, "You receive a "Page not found" error message when you use Outlook Web Access (OWA) to browse the Exchange Server 2003 client after you install Windows SharePoint Services" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=823265).
Exchange is installed on an SBS 2003 and I dont believe the microsoft kb is useful for this. Even if it is, I can work around this by removing ssl. However at this point I dont get any errors on the server and all I get from the HTC is "waiting for network". As mentioned earliar.
Any suggestions would be highly appreciated.
Thanks