Database Users

Solved: Pocket Outlook cannot connect to POP3 on Mac OS X server

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

Exchange ActiveSync Problem

Hi all,
I have a Hero from T-Mobile UK, and I'm not able to setup EAS. Going over the web or local network, using SSL or not, the server details verify, but when attempting a sync I all 3 data types (mail/contacts/calendar) fail with 'Sync protocol error'. I can see the hits in my web server logs, no HTTP error codes are being returned. Server is Exchange 2007.
Anybody come across this? Does anyone know if the HTC Exchange client makes any logs on the device?

I use EAS on my hero to Exchange 2010, and Exchange 2007 and I havent had any problems at all (apart from certificate signing issues).
Id say it would be a good idea to check your port settings, your outlook anywhere settings and your account permissions on your exchange server, as it seems odd for the phone to spew an error like that without something on the server playing up.

It's syncing with a Windows Mobile device without problems, and an iPhone. The Hero also sync's with a 2003 Exchange server I have access to with no issues.
I agree it could be some configuration option on the server which is tripping it up, but I've gone through everything I can think of. Having a look through adb logcat doesn't really tell me anything else, for example:
Code:
D/EAS_AppSvc( 271): 06021143 SyncThreadManager.checkQueue() Mail
W/System.err( 271): com.htc.android.mail.eassvc.core.SyncException: Protocol error
W/System.err( 271): at com.htc.android.mail.eassvc.core.SyncManager.getSyncCmdError(SyncManager.java:6225)
W/System.err( 271): at com.htc.android.mail.eassvc.core.SyncManager.syncEASEMail(SyncManager.java:3988)
W/System.err( 271): at com.htc.android.mail.eassvc.core.SyncManager.doSync(SyncManager.java:563)
W/System.err( 271): at com.htc.android.mail.eassvc.EASAppSvc$MailINCommandHandler.handleMessage(EASAppSvc.java:4850)

Hi! I have also an Exchange 2003 SP2 server and had similar issues. Be sure that you don't have "require SSL" for the /exchange folder of your IIS server activated. OMA works by simply accessing /exchange for getting access to your mailbox - but only without SSL. If you need SSL required for /exchange, you have to create a new virtual directory especially for OMA (e.g. /exchange-oma). Check out this guide by Microsoft:
http://support.microsoft.com/kb/886346
Another problem is using a primary email address which is different to the default Recipient Policy. If that's the case, EAS is not able to locate the mailbox. You have to tell EAS to use the secondary email address:
http://support.microsoft.com/kb/817379

Multiple smtp email addresses in Outlook

Hi,
I have a strange problem with the config of Outlook on my Windows Mobile 6.5 which I hope someone might be able to offer some help with. This is on a HTC HD2 with standard ROM, v 1.48.405.2 (71294) WWE.
I have configured it to connect with our work Exchange Server, and all is well, except for the "from" email address. On our exchange server I have several smtp email addresses associated with my account, for example:
[email protected] ; [email protected] ; [email protected] (a total of 5).
My main address is [email protected], but for some reason when I go to send an email from my mobile device the from address is [email protected], and I cannot find any way to change this.
I checked the device registry and found an entry:
HKEY_CURRENT_USER\Software\Microsoft\ActiveSync\Partners\{xxxx}\EmailAddresses
The contents of this entry showed all my smtp addresses, and had my main address as the final entry, and [email protected] as the first entry. So, I thought it's worth a try to swap them around - I did this, and did a soft reset, but the problem still persists.
Has anyone any suggestions ? Any help appreciated.
(Hope I explained this clearly).
Regards, Jon.

Resolved - using correct default smtp address now
Managed to resolve this, in case anyone is curious / has similar problems. I cannot be 100% sure which action resulted in it working, but I did the following:
- had our IT admin delete then re-add the smtp email addresses to my account, ensuring correct one was marked as default / primary
- deleted the Outlook account from my HD2.
- Created the Outlook account as new on my HD2 (I did this on the phone itself whereas last time I created using Windows Mobile Device Center)
It picked up the correct default email address immediately, and checking registry (location in original post), only the default email address is shown now. Previously all smtp email addresses were listed.
I am suspicious of creating the Outlook account in Windows Mobile Device Center as causing the problem in the first place - my Exchange Server account was previously working fine with a Touch Pro. But cannot be 100% sure without going back and retrying, which as I have it working, I am not going to do at the moment.
Anyway, I shall stop replying / talking to myself now.
Jon.

I have the same problem..
How is it possible to change the adress which you want to use for sending the email?
My Exchange pushes all incoming Emails I receive from different accounts, but sometimes it would be fine to answer with the right Email account.. But I found no solution yet..
Any news from your side jh9957?
Thanks and Regards,
MS

Problems with the default Exchange Mail Client

Hello,
I've just bought my Galaxy S.
I have problems with the default Exchange Email client from the phone.(is this Samsung one, or Android?).
At the begining it was working fine, without any issues.
I made a firmware update using Odin to I9000XWJG5 and it was not working anymore. When I was trying to configure it all the time I was getting "Unable to connect to open connection to server". I checked with a USB tracing tool and I saw that the email client is crashing.
Meantime I updated to the last VDF Romania verision I9000BUJF5, but the behaviour is the same.
What it is starnge is that I installed an Market Exchange Clent, Touchdown, and it is working just fine (using Active Sync connection to Exchange Server).
What do you think? Which can be the issue?
The funy thing is that with an other I9000 with the same software, is working the default Exchange Email client! So it is something with my hardware?
Thanks,
Mircea

I have same problem. Any solution? I use 3rd party like TouchDown and RoadSync are working fine. Is this ROM problem?

One more thing: the same behaviour is hapening if I try to configure yahoo mail!!! It is a problem with the embeded email client!
Sent from my GT-I9000 using XDA App

though touchdown works, but it doesn't integrate with the phone and other Widget.
Still prefer the Exchange client comes with SGS.
and looks mirceal has a more serious problem than i do, I only can't sync the calendar, unlike mirceal, can't sync anything

I have the exact same problem. Have you found a solution yet?
Thanks!

On my side I have already tested a lot of mail app and a lot of ROM ( australian JG2 I think and JFF, JM2, JM5, JG8 and JP3)
For all the 3rd party mail app ( htc work mail, k9, touch down) it basically works all the time
For the integrated mail app I had the following issues :
* Unable to connect to open connection to server for all the exchange account
* Unable to connect to open connection to server only on the subfolder ( the inbox was working)
* Unable to connect to open connection to server for the Hotmail
* Hotmail mail downloaded but not displayed ( can't even see the list of mail ... just the count on the first mail app page)
This problem occured only with some ROM and sometime with the same ROM it happened or not after a reboot
For instance on JFF, JG8 and JM5 I have never been able to see the mail coming from the subfolder of my exchange account.
I works fine with JM2 and JP3
For the calendar, I have seen only once working with JM2. With this ROM instand of having 1 exchange calendar I had several calendar coming from my exchange account ( one for every type of event like work, family, personal ....)
Now with JP3 the calendar doesnt sync so I have to use gmail to sync my exchange
So no solution to propose ...
Iwill install again tomorrow JM2 to see if the mail and calendar definitely works with this one
How did you check that the mail app was crashing through usb ?

Hello,
Good news from my side!
I found the issue I experienced.
The things are as follows: when you configure for the first time the default client, it's firstly connecting to ssl.samsungmobile.com server!!!! This I noticed only after I installed wireshark program on the mobile. My problem ead that I am using a separate APN for checking emails. This APN doesn't have access to internet. So it was impossible to reach that public server!!!! And the error was "unable to open a connection to server". It was speaking abot the samsung ssl server and not my company's Exchange Server!!!! Crazy thing.
So at the first time of email client connection setting I used the internet APN till the internal setting algorithm reaches the ssl.samsungmobile.com connection and when it tries to reach the Exchange Mail Server I switch to vpn APN. And the Exchange emails are working without any problem!
Try it!
Mircea
Sent from my GT-I9000 using XDA App

Hi,
can you please clarify what exactly have you done?
for some reason I have the same problem on WiFi as well.
(let alone that ssl.samsungmobile.com is not a valid address).

Same with Galaxy Tab - reason found
This is exactly the same problem on my tab.
literal translation: "connection with server impossible"
It seems, however, that the client is in contact with the server: when I enter a wrong username, the error throws immediatly; with the correct credentials it takes 3 times longer.
New findings:
Exchange 2010 does a good job logging EAS. Extract of the EAS dialog of my Galaxy Tab:
RequestBody :
<?xml version="1.0" encoding="utf-8" ?>
<FolderSync xmlns="FolderHierarchy:">
<SyncKey>0</SyncKey>
</FolderSync>
AccessState :
Blocked
AccessStateReason :
Policy
ResponseHeader :
HTTP/1.1 449 Retry after sending a PROVISION command
MS-Server-ActiveSync: 14.1
ResponseBody :
[No XmlResponse]
So, I can see that the mail client doesn't integrate with Exchange's security policies. Very bad job indeed, as TouchDown AND HTC (Desire:Froyo) do quite well.
Is somebody please going to request Samsung to speed up?

Exchange 2007 vs. 2010
I just discovered that on Galaxy Tab, the mail client can deal with an Exchange 2007 Server with security policies activated, but it cannot get the compliance check done with Exchange 2010.

This is a known issue with certain versions of Android OS on phones available from different manufacturers and service providers. The only verified solution that we know of at this moment has come thru this community, as 'Mitch Roberson' has written below, I have marked that as an 'Answer' as well.
Now, let me list some related details here for everyone's information.
Phones are actually running into a provisioning issue against Exchange 2010 Server. This is evident from the IIS logs pastd below by some users and the logs we have seen in Microsoft Support. For example, you will see the following in IIS Log:
2010-08-31 20:38:54 192.168.2.6 POST /Microsoft-Server-ActiveSync/default.eas Cmd=FolderSync&User=johndoe&DeviceId=validate&DeviceType=Android&
Log=V120_Ssnf:T_LdapC13_LdapL16_RpcC35_RpcL63_Ers1_Cpo19453_Fet20015_Pk0_
ErroreviceNotProvisioned_As:BlockedP_Mbx:mail.contoso.local_Dc:dc01.contoso.local_Throttle0_BudgetD)Conn%3a1%2cHangingConn%3a0%2cAD%3a%24null%2f%24null%2f1%25%2cCAS%3a%24null%2f%24null%2f1%25%2cAB%3a%24null%2f%24null%2f0%25%2cRPC%3a%24null%2f%24null%2f1%25%2cFC%3a1000%2f0%2cPolicy%3aDefaultThrottlingPolicy%5F7fd952bb-6275-4010-8c3e-bb47f4cea08f%2cNorm%5bResources%3a(Mdb)DB1(Health%3a-1%25%2cHistLoad%3a0)%2c(DC)dc01.contoso.local(Health%3a-1%25%2cHistLoad%3a0)%2c(DC)dc02.contoso.local(Health%3a-1%25%2cHistLoad%3a0)%2c%5d_ 443 contoso\johndoe 75.204.200.137 Android/0.3 449 0 64 20734
You can see that the Android mobile device is sending a 'FolderSync' EAS command to server for user JohnDoe with the DeviceID = Validate and Type = Android, and is being blocked by Exchange as it is not responding properly to the provision command from server. This is implemented thru Default Throttling Policy and the error it geenrates is error code: 449 (which essentially means device provisioning has failed). Generally this happens when client does not respond properly to provisioning commands from server where server informs mobile device that there are certain EAS policies applied by the Exchange Server Administrator and device needs to acknowledge those for implementation. This happens mostly when the device does not support all or a subset of EAS policies being implemented by the Exchange Server Administrator.
If you bring up the EMS command prompt and enter the following command, you will see the following output (similar to what we saw above in IIS Log):
Output of “Get-ActiveSyncDeviceStatistics -mailbox:johndoe”: (truncated)
RunspaceId : f0323f7c-b3a6-4102-ab5b-d1df0464e318
FirstSyncTime : 8/31/2010 8:38:34 PM
DeviceType : Android
DeviceID : validate
DeviceUserAgent : Android/0.3
DeviceModel : Android
DeviceEnableOutboundSMS : False
Identity : contoso.local/Test/John Doe/ExchangeActiveSyncDevices/Android§validate
Guid : a5750d0c-189c-4ccc-9b22-e5c87845f5c0
IsRemoteWipeSupported : False
Status : DeviceOk
DeviceAccessState : Blocked
DeviceAccessStateReason : Policy
DevicePolicyApplied : Corp
DevicePolicyApplicationStatus :NotApplied
DeviceActiveSyncVersion : 12.0
NumberOfFoldersSynced : 0
We have seen this issue mostly with devices using Android 2.1, users who have been able to update their devices with Android 2.2 somehow, stopped running into this issue, without making any changes on the server side.
I contacted HTC Support (on 9/28 via http://www.htc.com/us/support/e-mail) about this issue and they responded (like other users have reported here), please keep in mind this can change at any time in future, so please contact HTC Support directly for updates:
"At this time we do not have any Android based device that will sync with an Exchange 2010 Server. We may provide future Android devices that do offer this. However, as there is currently no release information for any upcoming devices, we encourage you to continually visit HTC’s product page at http://www.htc.com/us"
While working on this issue we also discovered that Android provided limited support for EAS policies and is working to continually improve it in their upcoming versions. For more information, please see related posts below. Again, this information is subject to change at any moment, so please refer to Android website (http://code.google.com/p/android/issues/list) for current info.
1. http://code.google.com/p/android/issues/detail?id=9426 : "we only support the basic (EAS 2.5) features in Froyo. So if your server requires, for example, password history or expiration, or complex characters, then it won't be provisionable in Froyo. Our goal is to provide more policy support in future versions, but for now we support - password (PIN/alpha), minimum characters, max. fails to wipe, inactivity timeout, and remote wipe.”
2. Exchange Device Password policy not enforced when "Allow non-provisionable devices" is selected: http://code.google.com/p/android/issues/detail?id=8601
Fix for this issue is in the Android 2.2.1 Update, released recently (for Nexus One users, may not be available thru other service providers at this time, contact your service provider for any updates that they can provide for your device), Android now implements the policies it can rather than ignoring all policies and thus it can successfully sync with the server.
Hope this helps!

Google Apps for Domains and Email client

Anyone managed to get Exchange ActiveSync working on the Tab Email client with a Google Apps for Domains account?
I know my domain is set up correctly, because I can use ActiveSync support on my Desire with these accounts, but on the Tab although everything seems to be ok I do not get any email in my Inbox and in "Accounts & Sync" settings, there is only the option for Contacts and Calendar sync.
Regards,
Dave
Sent from my GT-P1000 using Tapatalk

exchange setup could not finish: Unable to connect server
Mine doesn't connect at all. When I checked at mail.mycompany.com phone option I see it already register but couldn't complete the registration but got access denied message on access state.
Anybody have this issue and know how to fixed it?
Below is the detail info from exchange server (2010 version):
Status: OK
First sync:
11/7/2010 5:34 PM
Last successful sync: Not Available
Folders synced: 0
Device name:
Not Available
Device model: Android
Phone number: Not Available
Mobile network: Not Available
Device type: Android
Device ID: validate
Device IMEI: Not Available
Device OS:
Not Available
Device language: Not Available
User agent: Android/0.3
Access state:
Access Denied
Access set by: Security Policy Application
Policy applied:
Default - Not applied
Policy updated: Not Available
ActiveSync version: 12.0

additional info
Sorry forgot to mention, I've also set to accept all SSL certificates. Still not working..

Somehow it works, but only one time and cannot redo
Just wanna update this thread. After hard reset for the third time suddenly the active sync connection is working and show a pop up of whether I want to continue being forced to have a security policy forced to Galaxy Tab.
It loads around 2 minutes, then goes to security setting and set screen lock.
After that the account sync!
When I try adding one more exchange account it fails with the above error message again.
A bug in the android mail app for pushed security policy, perhaps?

Make sure you have "Allow non-provisionable devices" checked in exchange.