Hi Corrado Fiore,
I have tried few days, I cannot get it work smoothly except IMAP.
Please see what's wrong with the caldav and carddav configuration?
************************************************/
// ************************
// BackendCalDAV settings
// ************************
// Server address
define('CALDAV_SERVER', 'http://sogo.xxx');
// Port
define('CALDAV_PORT', '80');
// Path
define('CALDAV_PATH', '/SOGo/dav/%u/Calendar');///caldav.php/%u/');
// Personal CalDAV folder (calendar folder/principal)
//define('CALDAV_PERSONAL', 'home');
?>
// ************************
// BackendCardDAV settings
// ************************
// Server protocol: http or https
define('CARDDAV_PROTOCOL', 'http');
// Server name
define('CARDDAV_SERVER', 'sogo.xxxxx');
// Server port
define('CARDDAV_PORT', '80');
// Server path to the addressbook
// %u: replaced with the username
// %d: replaced with the domain
// Add the trailing /
define('CARDDAV_PATH',
'/SOGo/dav/%u/Contacts/');///caldav.php/%u/addresses/');
// Addressbook display name
// %u: replaced with the username
// %d: replaced with the domain
define('CARDDAV_CONTACTS_FOLDER_NAME', '%u Addressbook');
// If the CardDAV server support the sync-collection operation
// DAViCal supports it, but SabreDav/Owncloud doesn't
// Setting this to false will work with most servers, but it will be pretty
slow: 1 petition for the href of vcards, and 1 petition for each vcard
define('CARDDAV_SUPPORTS_SYNC', true);
On Wed, Oct 23, 2013 at 7:38 AM, Corrado Fiore <[email protected]>wrote:
> On Oct 22, 2013, at 14:19 , boyd yang wrote:
>
> > Can this solution work well for mail,calendar,contacts at the same time？
> No need to configure calendar,contacts differently?
>
> Yup, exactly. All like a real Exchange account. Plus, you get push
> email, which is a definite bonus for business users.
>
> The downside - which might apply or not to your case - is that push mail
> via Z-push (which is a PHP application) requires way more resources per
> user than SOGo itself since the TCP connection underlying the HTTP protocol
> must remain in open state.
>
> As the author of Z-push-contrib suggests, the rule of thumb is: 1.5 PHP
> processes per email user, so 1,000 users would translate to 1,500 active
> PHP processes. Of course you can set up a balanced pool of servers, but
> the point here is: don't expect Z-Push (which I love, don't get me wrong)
> to scale beautifully as SOGo does.
>
> In this light, I can understand one of the reasons why the SOGo team is
> looking for a native implementation instead.
>
> Best,
> Corrado
>
>
>
> --
> [email protected]
> https://inverse.ca/sogo/lists
--
[email protected]
https://inverse.ca/sogo/lists
