On 04/12/2016 04:17 PM, Daniel Bareiro (daniel-lis...@gmx.net) wrote:
Hi, Steve.

On 11/04/16 12:54, Steve Ankeny (stev...@cinergymetro.net) wrote:

Thank you for confirming and the references. I appreciate it. I'll see
how I will do this implementation and will consult you any questions
that arise.

Thanks for your time.
no problem, Daniel

I am not an expert!  However, I've struggled with OpenChange, and I've
come to the conclusion the better way for my users is to use EAS with
Outlook 2013, and like you, I think the CalDav Synchronizer looks great.
According to what I was seeing in the documentation that you mentioned,
the installation seems more complex and (correct me if I'm wrong,
please) seems necessarily to requires LDAP. I have no experience with
LDAP, so I probably have to fight with this installation in the case of
do it for the first time.

Samba uses the LDAP protocol, so you use Samba instead of LDAP

IF you wish to use OpenChange, you must use the Inverse package, which is Samba 4.1.18, because OpenChange is compiled to work with that version ONLY (there's an unconfirmed rumor to the contrary)

OpenChange is required for the older versions of Outlook (2003, 2007, 2010)

However, IF you are willing to use Outlook 2013 (and above), you do not need OpenChange.

From what Rowland Penny tells us in another thread, Samba 4.1.18 has security issues and requires patching. Who's Rowland Penny? He's a moderator on the Samba mailing list which you can review here

https://lists.samba.org/mailman/listinfo/samba

So, I would recommend following the details of installing the latest Samba from their wiki

https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO

On the other hand, having a working mail server (Dovecot/Postfix), Samba for user authentication, you can use SOGo to your heart's content for calendar, contacts, address books, etc. by using the EAS/EAW protocols.

Start with a mail server, add apache and mysql, then Samba, create users and install SOGo

That's the general progression you need to follow. Most of it is in the documentation.

In the installation I did (only) for Outlook 2013 and Android clients, I
installed "sogo" and "sogo-activesync" packages (I am struck that Debian
Jessie has no the "sogo-activesync" package) in Ubuntu from SOGo
repositories. I also installed MySQL to create a database with users for
SOGo. Here these clients was connected using ActiveSync smoothly.

IF you're looking for Debian SOGo packages, use the Inverse repositories.

You can use MySQL for your user database, just follow the instructions for SQL authentication. However, you can also migrate those users to Samba by using "samba-tool" to create users in the Samba LDAP DB

Once you login to SOGo via the web interface, it will populate the mysql database.

If I understood correctly, for users with older versions of Outlook who
want to use ActiveSync, instead of having SOGo users in a MySQL database
these must be on a LDAP directory, right?

While on this way SOGo contemplates using very old versions of Outlook
living with other newer of Outlook and all homogeneously using
ActiveSync, I think it would be the only case where SOGo worth
installing. Because if we will install SOGo for Outlook clients
connecting via CalDAV/CarDAV, we could use another web application as
the case of Horde Groupware.

That will help with Address Books and Contacts, but it will not help
with receiving Mail in Outlook.
When I had configured Outlook 2013 to use ActiveSync, I remember that it
showed two mail boxes: one for the IMAP connection and another for
synchronization with ActiveSync. This could be confusing for users,
especially because that environment had an IMAP server without the
capabilities necessary to synchronize emails using ActiveSync. So in a
mailbox the users were seeing all the emails obtained using IMAP and the
other mailbox looked empty.

I'm unsure of this (no experience with it)

I always use IMAP (but I also use Thunderbird for most of my mail needs)

I only have a few Outlook clients, and they use IMAP It's the calendar they need.


That's where using EAS should work.  I'm on the same page as you as far
as not using OpenChange.  My users are long time Thunderbird users, so
using MAPI for Mail made sense, but "some" users need Outlook.

So, for those few users, I believe EAS should do the job.
Dovecot/Postfix, SOGo, Samba, no OpenChange
Yes, it is an option. Although the case of using CalDAV/CarDAV also
avoids confusion due to the double mailbox that a user might have in
Outlook if they use IMAP and ActiveSync simultaneously.


Kind regards,
Daniel



--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to