maemo.org - Talk
Page 39 of 40 « First 293738 39 40
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Maemo 5 / Fremantle (https://talk.maemo.org/forumdisplay.php?f=40)
-   -   Mail for Exchange (MfE). Blame me here, pls (https://talk.maemo.org/showthread.php?t=35136)

rmoravcik 2011-06-08 10:00
Re: Mail for Exchange (MfE). Blame me here, pls
 
I have the same problem. Synchronization with google calendar stopped working for me too today.

rmoravcik 2011-06-08 10:08
Re: Mail for Exchange (MfE). Blame me here, pls
 
Synchronization problems should be really related to IPv6: Bug 9943 - (int-164687) MfE Wizard fails if exchange server hostname has IPv4 and IPv6 addresses

petur 2011-06-08 11:36
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by rmoravcik (Post 1024895)
Did google enable ipv6 then?

Also, I did find this: http://www.google.com/support/forum/...c763bd42&hl=en but disabling contacts sync doesn't fix it

petur 2011-06-08 11:44
Re: Mail for Exchange (MfE). Blame me here, pls
 
OH DAMN

according to http://ipv6-test.com/validate.php they did indeed enable ipv6 for m.google.com

Rob1n 2011-06-08 11:50
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by petur (Post 1024962)
OH DAMN

according to http://ipv6-test.com/validate.php they did indeed enable ipv6 for m.google.com
That will probably change shortly - today is world IPv6 day, which is intended to help find these sort of issues. They'll be reverting to IPv4 only again tomorrow (or whenever they get round to making the DNS changes and getting them propagated).

AndyNokia232 2011-06-08 21:27
Re: Mail for Exchange (MfE). Blame me here, pls
 
@Rob1n: I hope so. I was doing my usual 'Delete MfE calendar and then reinstall MfE calendar' routine in order to update it, but it kept saying "Error connecting to server" type message.

I'll try again tomorrow or Friday.

petur 2011-06-12 11:47
Re: Mail for Exchange (MfE). Blame me here, pls
 
After a reboot, things are working again - I assume Google changed something back (there is a related thread in their groups to complain, maybe they picked it up)

seronline 2011-06-15 13:36
Re: Mail for Exchange (MfE). Blame me here, pls
 
Hi lads,

I'm getting quite annoyed on my N900. For me synchronising the Gmail contacts doesn't work anymore. Neither with Exchange nor SynchEvolution. Tried rebooting the phone multiple times (including flushing the entire contact list).
When using Mail for Exchange I'm getting "Invalid user name, password or domain for Exchange account". With synchevolution Error 401 (authentication failed) is returned.

Edit: Erminig for gmail calendar is working fine :-/

Any suggestions? Thx in advance for any hints.

S

toxaris 2011-10-12 06:21
Re: Mail for Exchange (MfE). Blame me here, pls
 
Today MfE totaly ****ed all my contacts, I got everyone in dublicate.
First MfE downloads a dublicate from Hotmail, then MfE uploads everyone again to hotmail.
So now I got dublicate of every contact in both the phone and on hotmail.

This is crazy. Crappy MfE!

toxaris 2011-10-14 16:57
Re: Mail for Exchange (MfE). Blame me here, pls
 
Hello.

Seams my MfE is broken.
Is there a way to cleanup/reset/reinstall MfE?

thx.

SpRoOoOo 2011-12-06 18:14
Re: Mail for Exchange (MfE). Blame me here, pls
 
1 Attachment(s)
Hello Everyone,
I really need someone's help regarding my MFE. The problem started after upgrading to version 21.2011.38-1. After the upgrade completed the first thing I did is setup my Gmail as IMAP and tried to set up my Email with MFE to connect to exchange server 2007. I am the administrator and I haven't changed anything prior the update. I installed power-kernel for overclock and ip6 and community OS for a fix if it was there, I tried importing the cert. for my server "Which didn't have to do before" with the same error . I have the syslog for active-sync attached .
If someone has an idea on how to fix this please let me know . Thank you all

Saturn 2011-12-06 18:56
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by SpRoOoOo (Post 1134121)
Hello Everyone,
I really need someone's help regarding my MFE. The problem started after upgrading to version 21.2011.38-1. After the upgrade completed the first thing I did is setup my Gmail as IMAP and tried to set up my Email with MFE to connect to exchange server 2007. I am the administrator and I haven't changed anything prior the update. I installed power-kernel for overclock and ip6 and community OS for a fix if it was there, I tried importing the cert. for my server "Which didn't have to do before" with the same error . I have the syslog for active-sync attached .
If someone has an idea on how to fix this please let me know . Thank you all
Don't know if it is really related to your problem, but some time ago it was the ip6 test day and people had all kinds of errors and were not able to read their mails.

It worth checking if fixing it to ip4 solves your problems. There were instructions here, maybe search could help you read more on the issue.

HIH

SpRoOoOo 2011-12-07 05:13
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by Saturn (Post 1134139)
Don't know if it is really related to your problem, but some time ago it was the ip6 test day and people had all kinds of errors and were not able to read their mails.

It worth checking if fixing it to ip4 solves your problems. There were instructions here, maybe search could help you read more on the issue.

HIH
Thx for the reply man. I am going to restore connectivity back to IPv4. but wouldn't upgrading the phone restores the system files back to normal?? since I tried to configuring the MFE directly after the upgrade ! am going to try your idea first though . I will post back.

SpRoOoOo 2011-12-07 05:46
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by Saturn (Post 1134139)
Don't know if it is really related to your problem, but some time ago it was the ip6 test day and people had all kinds of errors and were not able to read their mails.

It worth checking if fixing it to ip4 solves your problems. There were instructions here, maybe search could help you read more on the issue.

HIH
same error "Error in communication with Exchange server" . So IPv6 is not the reason ! I think I could flash back to the older version but am not going to consider this option yet .. anyother suggestions will be appreciated ??

Rob1n 2011-12-07 09:57
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by SpRoOoOo (Post 1134121)
Hello Everyone,
I really need someone's help regarding my MFE. The problem started after upgrading to version 21.2011.38-1. After the upgrade completed the first thing I did is setup my Gmail as IMAP and tried to set up my Email with MFE to connect to exchange server 2007. I am the administrator and I haven't changed anything prior the update. I installed power-kernel for overclock and ip6 and community OS for a fix if it was there, I tried importing the cert. for my server "Which didn't have to do before" with the same error . I have the syslog for active-sync attached .
If someone has an idea on how to fix this please let me know . Thank you all
The log would suggest that either the Exchange details you entered were incorrect, or there were some network issues. Lines 424-440 show it attempting to connect to driskillconsulting.com but failing to resolve the address. After that it seems to be trying to use server.com instead (unless you've done some substitutions on the log?) for some reason.

SpRoOoOo 2011-12-07 15:38
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by Rob1n (Post 1134368)
The log would suggest that either the Exchange details you entered were incorrect, or there were some network issues. Lines 424-440 show it attempting to connect to driskillconsulting.com but failing to resolve the address. After that it seems to be trying to use server.com instead (unless you've done some substitutions on the log?) for some reason.
Thx For the reply and confirming my initial troubleshooting . Yes I did some changes in the log file since not everyone is trust worthy like you guys. The information is correct a 100% email, password, username, domain and server address. It's kinda of weird why the client can't resolve the server name after resolving all other information. Do you think its related to the certificate??

n900-dk 2011-12-07 16:26
Re: Mail for Exchange (MfE). Blame me here, pls
 
Can you resolve the servername in a terminal by nslookup?
If not, what happens if you add servername and IP address to /etc/hosts and try to sync again?

SpRoOoOo 2011-12-07 17:33
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by n900-dk (Post 1134571)
Can you resolve the servername in a terminal by nslookup?
If not, what happens if you add servername and IP address to /etc/hosts and try to sync again?
I was able to resolve it and adjusted host file . still the same.

SpRoOoOo 2011-12-07 18:19
Re: Mail for Exchange (MfE). Blame me here, pls
 
1 Attachment(s)
Quote:
Originally Posted by n900-dk (Post 1134571)
Can you resolve the servername in a terminal by nslookup?
If not, what happens if you add servername and IP address to /etc/hosts and try to sync again?


And I did check cert. and shows it's fine . Should I just flash back to the version before the update ??

kawabill 2011-12-08 06:46
Re: Mail for Exchange (MfE). Blame me here, pls
 
I have identical problems syncing at work with MfE to Outlook, even when trying to sync the device to m.google.com I get this communication error. My own and my girlfriends phone show the same problem.

Software version says;21.2011.38-1

@SpRoOoOo
I hope I'm not stealing your story here, so please let me know if there's no relation. It would help me if you checked syncing to gmail works for your device.

Thanks,
Bill

SpRoOoOo 2011-12-08 14:28
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by kawabill (Post 1134863)
I have identical problems syncing at work with MfE to Outlook, even when trying to sync the device to m.google.com I get this communication error. My own and my girlfriends phone show the same problem.

Software version says;21.2011.38-1

@SpRoOoOo
I hope I'm not stealing your story here, so please let me know if there's no relation. It would help me if you checked syncing to gmail works for your device.

Thanks,
Bill
That is O.K. man. Well from what I read in the articles about Gmail Sync, Email push is not supported . So, to work around my problem I configured Exchange account as imap , Gmail as Imap and mfe with Gmail to sync Calender and Contacts. Though, after the initial sync , I noticed that the calender in sync but no contacts. So, here is what I did to further try to keep everything in sync , I installed Goolgle calender sync with outlook and and Go Contacts Sync software on my computer . After, that I was able to get me calender and contacts into Gmail . Though, I couldn't get gmail to sync back with the phone just the calender . So, I gave up and synced my contacts using PC suite and left calender sync with gmail using mfe .

So to sum up. Added contacts to outlook will replicate to gmail using Go Contact Sync Mod but can't sync back to N900 only with PC suite , installed Google calender sync on my computer (2 ways ) to replicate exchange calender to Gmail and N900 using mfe .

I am not ready to get rid of this phone yet , I am so attached to it that's why am jumping through hoops. Maybe this won't help you much but regarding Exchange Error with m.google.com try unchecking the email and leave just calender and contacts.

shoonmcgregor 2011-12-08 14:50
Re: Mail for Exchange (MfE). Blame me here, pls
 
I'm seeing the same thing with m.google.com

Code:
# cmcli -T common=ca -v m.google.com:443
f5......4a
  Verification failed: unable to get local issuer certificate
google cal/contact sync has always been sporatic for me but even more so with the recent cssu update.


Quote:
Originally Posted by kawabill (Post 1134863)
I have identical problems syncing at work with MfE to Outlook, even when trying to sync the device to m.google.com I get this communication error. My own and my girlfriends phone show the same problem.

Software version says;21.2011.38-1

@SpRoOoOo
I hope I'm not stealing your story here, so please let me know if there's no relation. It would help me if you checked syncing to gmail works for your device.

Thanks,
Bill

SpRoOoOo 2011-12-08 14:54
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by shoonmcgregor (Post 1135029)
I'm seeing the same thing with m.google.com

Code:
# cmcli -T common=ca -v m.google.com:443
f5......4a
  Verification failed: unable to get local issuer certificate
google cal/contact sync has always been sporatic for me but even more so with the recent cssu update.
I can confirm the cert. failure on my phone .

kawabill 2011-12-09 06:32
Re: Mail for Exchange (MfE). Blame me here, pls
 
Thanks SpRoOoOo, the reason for me checking gmail sync was identical to yours.

We had corporate change to another exchange server, before it worked without problems. I agree it must be something in the phone that needs updating. Will check this weekend and see whether I can get Meego installed an see whether I can get that to work properly.

For today's standads the N900 is big and heavy, but I love the phone as it is possible to do almost everything.... Except sync Outlook through MfE these days.

Will keep following this thread.

shoonmcgregor 2011-12-12 15:02
Re: Mail for Exchange (MfE). Blame me here, pls
 
I think the cert issue is a red herring.

I was able to capture a syslog that contains a successful MfE session, a failed MfE session, all subsequent MfE session failures, and then resolve without a reboot/full resync/etc:

The successful MfE case was on fresh reboot, wifi ap, external power. It looks like the ASDaemon-conn process kicks off a curl call back that returns http 200 (and I would guess the data from the post.)

Code:
HTTP REQUEST:  POST https://m.google.com/Microsoft-Server-ActiveSync?Cmd=Sync&DeviceId=XXXXXXXXXX&DeviceType=SmartPhone
ASDAEMON-CONN: startSession start, aWait=30 seconds
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=2                                                                       
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=1                           
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=4                                     
ASDAEMON-CONN: startSession end, ret=0         
AS-PERF: Transfered 1804 bytes in 0 seconds. Transfer rate is 0 Kb/sec
CurlConnectionManager: sendReceive attempt 1: CancelErr=0
HTTP STATUS: 200                                                     
AS-PERF: Content-Length:                                   
AS-LIB: Sync response received (200)
The subsequent MfE failure was when the phone transitioned from the aforementioned wifi to Tmobile 3.5G (3 bars), battery power. It looks like cURL is unable to contact the server after 2 tries (error code 7 enum is CURLE_COULDNT_CONNECT) and that catches into an AS-Lib 707 error. Fair enough, sync failed for this POST attempt.

Code:
HTTP REQUEST:  POST https://m.google.com/Microsoft-Server-ActiveSync?Cmd=FolderSync&DeviceId=XXXXXXXXXX&DeviceType=SmartPhone                                   
ASDAEMON-CONN: startSession start, aWait=30 seconds                                                                                                                 
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=2                                                                                                                         
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=1                                                                                                                         
activesync: AsStatusIndicator::displayEvent(0)                                                                                                                                 
activesync: AsStatusIndicator::updateState(): Sync                                                                                                                             
ASDAEMON-CONN: Cancel connection                                                                                                                                     
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=4                                                                                                   
ASDAEMON-CONN: startSession end, ret=0                                                                                                                               
AS-PERF: Transfered 0 bytes in 30 seconds. Transfer rate is 0 Kb/sec                                                                           
CurlConnectionManager: sendReceive attempt 1: CancelErr=901                                                                                   
ASDAEMON: ICListener IAPs count = 1                                                                                                           
ASDAEMON: ICListener proxyHost: usessl = 1, proxy_host = (null)                                                                 
HTTP REQUEST:  POST https://m.google.com/Microsoft-Server-ActiveSync?Cmd=FolderSync&DeviceId=XXXXXXXXXX&DeviceType=SmartPhone             
ASDAEMON-CONN: startSession start, aWait=90 seconds                                                                                           
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=1                                                                                                   
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=4                                                                                     
ASDAEMON-CONN: startSession end, ret=7                                                                                           
AS-PERF: Transfered 0 bytes in 1 seconds. Transfer rate is 0 Kb/sec                                                               
CurlConnectionManager: sendReceive attempt 2: CancelErr=0                                                                       
CurlConnectionManager: cURL errorcode = 7, Couldn't connect to server                                                           
AS-LIB: FolderSync response received (707)                                                                                       
AS-LIB: FolderSync ends with status 707                                                                                   
AS-LIB: Action execution ends with status 707                                                                                   
AS-LIB: Synchronizing folders finished with action status 707.

Now here is where I return to the known-good sync environment at the beginning of this post. All automated or Manual attempts at sync automatically fail with no retries. I suspect there is some state the CurlConnectionManager gets in where it thinks it hit the max retry limit and will no longer try.

Code:
HTTP REQUEST:  POST https://m.google.com/Microsoft-Server-ActiveSync?Cmd=FolderSync&DeviceId=XXXXXXXXXX&DeviceType=SmartPhone
ASDAEMON-CONN: startSession start, aWait=30 seconds           
ASDAEMON-CONN: Session already completed, ret=7
ASDAEMON-CONN: startSession end, ret=7                                         
AS-PERF: Transfered 0 bytes in 0 seconds. Transfer rate is 0 Kb/sec
CurlConnectionManager: sendReceive attempt 1: CancelErr=0                   
CurlConnectionManager: cURL errorcode = 7, Couldn't connect to server
So let's try restarting AS-daemon and retry the sync (should happen on as' start)

Code:
/etc/init.d/as-daemon-0 stop
/etc/init.d/as-daemon-0 start
Sure enough, sync returns just fine:

Code:
HTTP REQUEST:  POST https://m.google.com/Microsoft-Server-ActiveSync?Cmd=Sync&DeviceId=XXXXXXXXXX&DeviceType=SmartPhone
ASDAEMON-CONN: startSession start, aWait=30 seconds
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=2                     
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=1                               
ASDAEMON-CONN: CURL-CONN-CALLBACK: Action=4               
ASDAEMON-CONN: startSession end, ret=0                     
AS-PERF: Transfered 1804 bytes in 1 seconds. Transfer rate is 1 Kb/sec
CurlConnectionManager: sendReceive attempt 1: CancelErr=0   
HTTP STATUS: 200
I will look at the code for the asdaemon when I get a chance but if anyone out there with asdaemon/n900 chops gets a chance this might help out.

shoonmcgregor 2011-12-13 03:16
Re: Mail for Exchange (MfE). Blame me here, pls
 
Are you using tmobile? If so, are you using epc.tmobile.com as your apn?


Quote:
Originally Posted by SpRoOoOo (Post 1135030)
I can confirm the cert. failure on my phone .

SpRoOoOo 2011-12-13 03:25
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by shoonmcgregor (Post 1136885)
Are you using tmobile? If so, are you using epc.tmobile.com as your apn?
Yes I am with Tmobile . And yes I am using that for my APN, For IPv4.

shoonmcgregor 2011-12-13 14:54
Re: Mail for Exchange (MfE). Blame me here, pls
 
Thank you. I went through several test cases last night to track this down and was never able to get the first fail sync on the 2 wifi networks I tested but I was always able to get the failure on epc.tmobile.com. I suspect something is getting mangled when the request is sent through tmobile's apn but I only have those high level results at this point.

I really want to test OPTIONS and POST to see if tmobile is messing/blocking something so I tried to look at the asdaemon's code last night but I couldn't find the relevant cssu git repo.

The payload appears to be very small and the return data should not be that big (no changes to contacts/cal.)

http://vivekiyer.net/2010/12/06/an-a...tions-request/

For now, this process seems to resolve the no-sync state problem:

1.) Disconnect from T-Mobile internet
2.) Connect to known-good wifi AP w/ internet
3.) /etc/init.d/as-daemon-0 restart

Edit: Looks like MfE is closed source. I'll see if I can test the tmobile issue another way.

Quote:
Originally Posted by SpRoOoOo (Post 1136886)
Yes I am with Tmobile . And yes I am using that for my APN, For IPv4.

joeD 2011-12-29 07:05
Re: Mail for Exchange (MfE). Blame me here, pls
 
I can confirm on my n900 the same scenario. I've tried using the default tmobile apn epc.tmobile.com, and the wap.voicestream.com apn. I have no issues with mfe synch when on WiFi networks. On a side note, using the same sim card (yes its been trimmed to fit) I have no synch issues with mfe on my n9.

edit: I'm using T-Mobile prepaid 4g service, not sure if that would make any difference.

kawabill 2012-01-22 07:55
Re: Mail for Exchange (MfE). Blame me here, pls
 
Anyone on the forum having a solution how to emulate a provisioning device on N900?

I think the trouble I'm having is that the new policy for our corporate servers has changed to allowing only provisioned devices.

http://code.google.com/p/android/issues/detail?id=4475

Any ideas or directions are welcome.

mr_jrt 2012-01-22 21:42
Re: Mail for Exchange (MfE). Blame me here, pls
 
Inspired by this thread I decided to give MfE a shot at last.

...well, I get all sorts of timeouts etc...I had to wipe the calendar first, and then the show-stopper.

...it kept messing up my contact's work and home emails. I have each contact with Mobile (Home) and Mobile(Work) etc, and it'd do things like turn both mobile numbers into "Work" and "Mobile", but both containing the work number, erasing the home one.

...I then noticed after a few days I had 6-7 of each contact. Had to spend several hours (even with the find duplicates plugin!) merging them all back together. Not cool.

Annoying enough, in fact to make me glance at the open source MfE project with a view to pulling that in as a CSSU replacement...but then I remembered how many things I already have on my TODO list ;)

toxaris 2012-01-31 09:20
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by toxaris (Post 972198)
Hmm, its strange, syncing calender have worked like a charm the past 6 months. Now I got the same problem.
Im syncing with Hotmail.
And the only significant thing I have done is a full re-sync a a few weeks ago, maybe its that causing the bug to apear.
Now I have reinstalled the whole phone and now Calender sync works. Strange, but I think everyone should be carefull with Full Resync. I think its better to remove the whole account and set it up again. Dont forget to do a backup, I do it the manual way too, checkout the wiki.

Also I want to point out a warning finger on Hermes.
Hermes have serveral times messed up the contact sync for me.
Last time all contacts I added photos on was deleted from my hotmail-account.
Nowdays I only add photos on my contacts manually, this doesnot mess up thing sofar.

Big Phat Jan 2012-05-29 17:04
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by cedricp (Post 972338)
Hello everybody,

I think I'm running into this bug:
https://bugs.maemo.org/show_bug.cgi?id=9943

When I try to connect, mfe is asking for AAAA record. It gets a response, but the standart kernel is not able to talk ipv6.

Is there a way to prevent mfe to ask for a AAAA and directly ask for a A record (v4)?
I recently started seeing this problem. After spending more time investigating than I care to admit I found a simple workaround (also posted to the bug report). If you set an ipv4 address for your exchange host in the dnsmasq config it will reject the AAAA request with "NODATA-IPv6" which gets us past the bug. So something like (as root):

Quote:
echo "address=/yourexchangehost.com/123.45.67.8" >> /etc/dnsmasq.conf
With the obvious replacements.

Cheers,
Jan

aerobatawa 2012-06-07 16:31
Re: Mail for Exchange (MfE). Blame me here, pls
 
Hi, for those using Mail For Exchange to gmail / m.google.com on their N900.

I recently started receiving the message "Error in communication with exchange server" when syncing MforE (calendar only in my case).
Removing N900 calendar entries and running a full resync normally resolves this, but it the full resync failed with the same error as above.
Removing the MforE connection and running the MforE connection Wizard also failed with the same error on the page where you enter m.google.com and 443 port.

Following the instructions to modify dnsmasq.conf resolved this issue. i.e.

1. Launch X terminal
2. sudo gainroot
3. cd /
4. cd /etc
5. echo "address=/m.google.com/173.194.67.193" >> /etc/dnsmasq.conf
6. exit
7. reboot N900

freemangordon 2012-06-07 17:54
Re: Mail for Exchange (MfE). Blame me here, pls
 
Guys, could you please try "FB fix" i.e. install libcurl3 from extras-devel and report if it solves the problem for you. Disable dnsmasq.conf workaround first of course :)

jehan 2012-06-07 19:08
Re: Mail for Exchange (MfE). Blame me here, pls
 
yes that fixed it

Quote:
Originally Posted by freemangordon (Post 1219071)
Guys, could you please try "FB fix" i.e. install libcurl3 from extras-devel and report if it solves the problem for you. Disable dnsmasq.conf workaround first of course :)

geodv8 2012-06-08 10:33
Re: Mail for Exchange (MfE). Blame me here, pls
 
Fantastic - MFE just started messing up and not syncing - found this, installed libcurl3 update - and it works.
Thanks!

aerobatawa 2012-06-08 13:50
Re: Mail for Exchange (MfE). Blame me here, pls
 
Hi all,

Just to confirm the Libcurl3 update works on MforE to m.google.com after backing out the dnsmasq.conf work-around. (reboot N900 after each step).

For people not clear of the process:

Libcurl3 is from extras-dev so you have to enable the Extras Devel catalogue in application manager first (you can disable afterwards):
Navigate to the application menu (tap the title bar)
Select ‘Application catalogs’
Select ‘New’
Enter a catalog name of ‘Maemo extras-devel’
Enter a web address of http://repository.maemo.org/extras-devel/
Enter a distribution of ‘fremantle’
Enter components of ‘free non-free’
Select ‘Save’

To apply the libcurl3 update:
Launch X terminal
sudo gainroot
apt-get install libcurl3
exit
exit
Reboot N900

Finally, many thanks to those commited developers providing us mere mortals with solutions.

Big Phat Jan 2012-06-09 09:35
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by freemangordon (Post 1219071)
Guys, could you please try "FB fix" i.e. install libcurl3 from extras-devel and report if it solves the problem for you. Disable dnsmasq.conf workaround first of course :)
Just another confirmation that this solves the problem.

Cheers,
Jan

shurak 2012-06-11 23:19
Re: Mail for Exchange (MfE). Blame me here, pls
 
Quote:
Originally Posted by aerobatawa (Post 1219479)
Hi all,

Just to confirm the Libcurl3 update works on MforE to m.google.com after backing out the dnsmasq.conf work-around. (reboot N900 after each step).

For people not clear of the process:

Libcurl3 is from extras-dev so you have to enable the Extras Devel catalogue in application manager first (you can disable afterwards):
Navigate to the application menu (tap the title bar)
Select ‘Application catalogs’
Select ‘New’
Enter a catalog name of ‘Maemo extras-devel’
Enter a web address of http://repository.maemo.org/extras-devel/
Enter a distribution of ‘fremantle’
Enter components of ‘free non-free’
Select ‘Save’

To apply the libcurl3 update:
Launch X terminal
sudo gainroot
apt-get install libcurl3
exit
exit
Reboot N900

Finally, many thanks to those commited developers providing us mere mortals with solutions.
Excellent! :> That solved the problem.
I would like to ask 2 things:
1) During the installation recommended package "ca-certificates". Should I install it too? (do not know if you have to do, but my n900 has several certificates are not valid in "Settings" -> "Certificate Manager". Also My date / time are correct)
2) The file "/ etc / dnsmasq.conf" is not empty. You need to empty it manually?

Thank you very much


All times are GMT. The time now is 23:20.
Page 39 of 40 « First 293738 39 40
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8