Hello all,
I installed [ROM] NexusHD2-JellyBean-4.1.2-CM10 V1.2 from tytung.
It is fine. I find it great.
But I have an issue to configure with my corporate exchange account.
My error log emaillog.txt is as following:
[11:17:53] AbstractSyncService| Testing EAS: my.server.adress, my_domain\my_user, ssl = 1
[11:17:53] ExchangeService| !!! EAS ExchangeService, onStartCommand, startingUp = false, running = false
[11:17:53] ExchangeService| Reconciling accounts...
[11:17:53] ExchangeService| !!! EAS ExchangeService, stopping self
[11:17:53] AbstractSyncService| Validation (OPTIONS) response: 500
[11:17:53] AbstractSyncService| Internal server error
[11:17:53] ExchangeService| !!! EAS ExchangeService, onDestroy
Click to expand...
Click to collapse
I can't get rid of the error:
[11:17:53] AbstractSyncService| Validation (OPTIONS) response: 500
[11:17:53] AbstractSyncService| Internal server error
Does someone know how to solve it? What is it meaning?
I searched hours on the xda forums and found lots of posts with issues concerning Email.apk and Exchange Server.
I tried different proposed solutions, but they didn't solved my case.
Here what I tried:
- Delete all accounts (even the google account), recreate the exchange account 1st ...
- Check my permissions in Active directory (The famous checkbox inherit permissions), which are correct.
- Reinstalled the rom.
- I tried to replace my apk with various Email.apk and Exchange2.apk without exchange security, it never worked.
- I tried with a pin lock screen, a password lockscreen or a pattern lock screen
- I found post speaking about issues concerning the exchange server SSL Certificate.
I tried the workaround with WIFI connection and shut down the connection, to finish the account configuration, but it didn't worked.
Instead of skipping the SSL certificate check and completing the account configuration, it cancelled/interrupted the account configuration.
- I tried to add the SSL certificate in the trusted certificates
- With my Email.apk V4.1 and Exchange2.apk v5.0 I never got the message to add the email application to the device administrator...
- I checked my settings with Moxier trial and Touchdown trial, and it worked. So my settings (account, domain, server) are correct. The only problem is the Email.apk on JB 4.1.2 !!!
I noticed that if i install a previous version of Email.apk (v2.3), I can configure my exchange account and sync mails, but the application is not stable on JB 4.1.2 and constantly crashes.
What could I do to solve that issue?
Do someone have a tip or hint?
Thanks in advance
Regards
A. Meladius
Related
Hello
I installed 4.1.1 on a MB525 (Defy) according to the honorable post in <http://forum.xda-developers.com/showthread.php?t=1768702> and it works like a charm!
One thing I am missing is: Configuration options for the IMAP account are not as fine granular as in the stock Motorola. Especially I can't configure to an IMAP server supporting the following:
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready.
Means: IMAP with STARTTLS and encrypted (MD5) password
What is supported by the 4.1.1: None, SSL/TLS, SSL/TLS (all certs accepted), STARTTLS, STARTTLS (all certs accepted).
What I would need is STARTTLS with password encryption md5 (automatically detected or fixed configurable).
How could I solve this issue?
Regards
TinL
Q does not seem to be Question
Hello
it does not seem to be an issue for Android 4.1 in general.
Regards
TinL
Hi, I recently purchased the ZTE Open C and want to synchronize its calendar with my own Caldav server.
Firefox rejects the connection tough, because the server has an invalid (self signed) certificate.
So i tried adding my certificate to firefox.
I found this guide:
http : // wiki . mozfr . org / Adding_CA_to_FirefoxOS
(Sorry for inserted spaces, won't let me post a link in first post.)
However I fail in the very first steps.
Code:
adb shell ls /data/b2g/mozilla/
Returns: /data/b2g/mozilla/: Permission denied
This means I dont have reading rights in this directory.
How do I get those rights, or alternativeley is there a better way to achieve my Caldav-Server goal?
Mathews123 said:
Hi, I recently purchased the ZTE Open C and want to synchronize its calendar with my own Caldav server.
Firefox rejects the connection tough, because the server has an invalid (self signed) certificate.
So i tried adding my certificate to firefox.
I found this guide:
http : // wiki . mozfr . org / Adding_CA_to_FirefoxOS
(Sorry for inserted spaces, won't let me post a link in first post.)
However I fail in the very first steps.
Code:
adb shell ls /data/b2g/mozilla/
Returns: /data/b2g/mozilla/: Permission denied
This means I dont have reading rights in this directory.
How do I get those rights, or alternativeley is there a better way to achieve my Caldav-Server goal?
Click to expand...
Click to collapse
You cannot use that method unless your phone is rooted, BUT...
I had the same problem and solved it a lot easier. Just launch the browser and input your server's URL. Then you will be warned about the not valid cert, add a permanent exception and that's all, now calendars should sync over HTTPS.
BTW this worked for me until FFOS v1.4. Today I updated to FFOS 2.1 and this trick stopped working, so you have been warned.
Thank you for the suggestion.
I am not running v2.0, so I tried it.
I could add the certificate.
However, when trying to connect, I get:
"Unknown Error. Please try again later."
Any way to figure out what's wrong now?
Seems to be a problem with the server I used. (Baikal)
Using a different one (Owncloud - sadly quite a lot bigger), it works with your tip.
So thanks for the help.
to ged rid of the "unknown error" in Caldav (etc.?)
doragasu said:
I had the same problem and solved it a lot easier. Just launch the browser and input your server's URL. Then you will be warned about the not valid cert, add a permanent exception and that's all, now calendars should sync over HTTPS.
Click to expand...
Click to collapse
thank you so much :victory:
Hi,
I am having trouble getting exchange accounts to work in Gmail in Android 5.0.1
Pre-lollipop update we were using the onboard android mail client with no worries, keen for the gmail integration we upgraded to gmail where we discovered we cannot download or send attachments greater than 5mb when using an exchange account in gmail.
When downloading an attachment I get the following error "Couldn't download. Touch to retry."
When attaching a 5mb file I get "Can't attach file over 5mb."
The debugging I have done:
Files over 5mb can be downloaded/sent over wifi
All settings related to limits have been disabled
I have checked the exchange 2007 settings and there is a limit of 15mb set
Removing this limit did not help
Tested downloading an attachment using a gmail account, this was successful
Rolled back to lollipop with no updates: no success
Ensured all apps are OS is up to date
3rd party apps such as 'outlook' have no issue
I am able to download attachments greater than 5mb using OWA
I have tried multiple file types including PDF, ZIP and JPEG
Confirmed accounts are still working on email clients pre-gmail integration
Not getting anywhere from this I rooted a test phone and got the following information from logcat when attempting to download an attachment:
Code:
W/AttachmentService( 2363): Attachment #346 is not eligible for download
W/AttachmentService( 2363): Attachment #346 cannot be downloaded ever
I/ConvLayout( 2363): IN setHeight=386px of overlay item: [email protected]
W/AttachmentService( 2363): Attachment #346 is not eligible for download
W/AttachmentService( 2363): Attachment #346 cannot be downloaded ever
I/ConvLayout( 2363): IN setHeight=386px of overlay item: [email protected]
D/audio_hw_primary( 184): disable_audio_route: reset and update mixer path: low-latency-playback
D/audio_hw_primary( 184): disable_snd_device: snd_device(2: speaker)
I/wpa_supplicant( 884): wlan0: CTRL-EVENT-SCAN-STARTED
Vague results here didn't help me that much, is anyone here able to help with this issue I am having?
Unfortunately using a 3rd party mail application isn't a solution I can use for this.
Is this a known bug for the system?
Any help or advice for places to look is greatly appreciated, I have run out of ideas for trying to find what this issue is.
Thankyou
I am trying to connect an email app (AquaMail) on my phone (Sprint Samsung Note 4, stock rooted, Android OS 5.0.1) to my email server (IMAP) using SSL. When I try this, I get the following error message:
Incoming mail server (IMAP): Invalid security (SSL) certificate. java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.
The server to which I am trying to connect is my own VPS. I do have a wild card certificate installed on the site and I believe it is installed properly. I say this because of the report I generated on www.ssllabs.com/ssltest:
Certificate: 100%
Protocol Support: 95%
Key Exchange: 90%
Cipher Strength: 90%
Two certification paths are shown: mail.mydomain.com -> StartCom Class 2 Primary Intermediate Server CA -> StartCom Certification Authority (one path shows this with SHA1withRSA and the other shows SHA256withRSA).
Looking at the Handshake Simulation section, it clearly shows that Android 5.0.0 functions properly, but is also shows that Java 7u25 has a 'protocol or cipher suite mismatch'. This same warning shows up for other, deprecated systems and is probably due to my having turned off older, insecure access protocols.
Can anyone suggest how to get this working properly? Yes, I could work around this by a) allowing all certificate or b) not using secure protocols; but neither of these are solutions.
Thank you for your help!
I am trying to understand how the android password authenticator works in some specific app.
There is this line of code in the app:
PasswordAuthentication auth = java.net.Authenticator.requestPasswordAuthentication(url.host(), getConnectToInetAddress(proxy, url), url.port(), url.scheme(), challenge.getRealm(), challenge.getScheme(), url.url(), RequestorType.SERVER);
I know that the requestPasswordAuthentication function Ask the authenticator that has been registered with the system for a password. It then returns the username and password and store them in "auth".
My questions are:
what is the authenticator that has been registered with the system? where is this password stored? Where does it get the password from?