Re: Re: [SOGo] TB Sogo Connector - Multiple user logins

2013-03-14 Thread der.keim
Great, that worked! -- users@sogo.nu https://inverse.ca/sogo/lists

[SOGo] TB Sogo Connector - Multiple user logins

2013-03-13 Thread der.keim
Hi, I use the Sogo connector for OwnCloud, but I am not asked for user / pw to synchronize with the adress book. I assume, that l/p is taken from calendar because of the same domain. As to my knowledge there is a bug tracked for that issue, but I couldn't find any workaround for that. How can I

Re: Re: [SOGo] Funambol: Officer not working / How to workaround

2013-01-12 Thread der.keim
OK, another log from ds-server.log: Writing to Sogo works, but retrieving fails: [2013-01-12 23:53:45,471] [funambol.handler] [ERROR] [C7930FAC2C6929FC509A305F6E7BC7DE] [192.168.178.40] [fol-VU5SRUFMRFVBTDpvdXQ=] [doc] [] Error processing message com.funambol.common.pim.vcard.TokenMgrError: Lexic

Re: Re: [SOGo] Funambol: Officer not working / How to workaround

2013-01-12 Thread der.keim
Here is the complete log file where you may see that the 1 contact has been transferred correctly: ** BEGIN of Synchronization session ** 23:26:33 GMT +1:00 [DEBUG] - [UI] Hide menu 23:26:33 GMT +1:00 [DEBUG] - Synchronization URL: http://xx-netz

Re: Re: [SOGo] Funambol: Officer not working / How to workaround

2013-01-12 Thread der.keim
Thanks for the hint! I had also tried the local IP before, with 'http://' as prefix which did also not work. With the local host IP it works! Tasks and Calendar is working, but not the contacts. After transferring all contacts from Outlook to the server, I get the following message: 23:21:39 GMT

Re: Re: [SOGo] Funambol: Officer not working / How to workaround

2013-01-08 Thread der.keim
No, since the existing file was ok. 'Localhost' and port 2. -- users@sogo.nu https://inverse.ca/sogo/lists

Re: Re: [SOGo] Funambol: Officer not working / How to workaround

2013-01-07 Thread der.keim
The Funambol log says: [2013-01-06 02:24:09,548] [funambol.transport.http] [INFO] [2E71EC4F5F5A73D05F8BE6DB3693E14B] [192.168.178.40] [] [] [] Request URL: http://192.168.178.43:8080/funambol/ds/ [2013-01-06 02:24:09,548] [funambol.transport.http] [INFO] [2E71EC4F5F5A73D05F8BE6DB3693E14B] [192.168

[SOGo] Funambol: Officer not working / How to workaround

2013-01-06 Thread der.keim
Hi, I installed Funambol on top of a working Sogo installation according to the offical Sogo manual. When entering the Sogo-Officer to the Funambol server I get authentication errors. I kept the related XML officer file as is. Using the default Funambol officer lets me add users automatically an

Re: Re: [SOGo] Funambol vs. OpenChange for offline sync

2012-12-09 Thread der.keim
> With Windows Mobile, you use Funambol for an old phone, and Active Sync (using the SOGoSync - https://github.com/xbgmsharp/sogosync) for a new one. I am using a WM6.5 phone. The sync between Outlook and the phone works very well. I want to manage my contacts with Outlook, for that reason I didn'

[SOGo] Funambol vs. OpenChange for offline sync

2012-12-06 Thread der.keim
I want to synchronize my mobile phone offline via MS Outlook. Do I need OpenChange for that task, or is it sufficient to use the funambol exchange-connector / outlook-connector? I would synchronize Outlook via Funambol with Sogo (Funambol server) and then connect my mobile via USB and using Activ

[SOGo] ZEG: Outlook 2003 worked only once

2012-11-28 Thread der.keim
Hi, With the ZEG installation, I connected via Outlook 2003 to Sogo. It worked for the first time quite nice (except of missing sender names). But then no connection was possible anymore, a restart of sogo did also not help. Which log file should I investigate? What could have happened? Keim -

[SOGo] ZEG: Not working without configuring Apache

2012-11-27 Thread der.keim
Hi, I like the Zero Effort idea a lot. I tried Sogo for the first time, without reading the manual. What I didn't know: The /etc/httpd/conf.d/SOGo.conf has to be modified to get the system running. Instead of "example.com" there is still a "https://yourhostname";. The 's' of 'https' was the next