Thanks for the info.  Any sources for what is needed?  What about Mobile?  Has that been tested and working, or do I need further setup for that as well?  It seems that if one will work, the other should as well.  Both use RPC over HTTPS.

Looking at the logs wasn't much help, but when I login via a browser session using the URL like so:

https://mail.server.dom/SOGo/Microsoft- … server.dom I am prompted for my username and password.  Once those are provided, I am redirected (to an obvious error page) to http://127.0.0.1:20000/SOGo/so/user@server.dom/Mail

Looks like maybe the setup script has an error in it where it is setting up the proxy pass wrong.  I guess it is worth mentioning that I am using Nginx, not Apache2.

Also, I am not looking for full native Outlook support, only ActiveSync support.  There is a major difference.  As I said, ActiveSync uses RPC over HTTP (or HTTPS if you want it secure).  Outlook 2013 has a full implementation of ActiveSync, so all you need to do is add the account as the correct type and it isn't using MAPI, but RCP over HTTPS.

I'm not quite sure what will happen if you try to login to this url directly, I suggest you ask in SOGo mailing list instead.

But one thing is sure, native outlook support requires OpenChange + Samba4.

Just for the record, I am following this tutorial, which is exactly what iRedmail is using for their SOGo config.  I mean, it is as if they copy/pasted this into the setup script.

http://www.iredmail.org/docs/sogo-cento … nc-support

I finally found time to work with this again.  I ended up going back to RoundCube, calendar functions would be nice, but push email is nicer! 

I setup iRedmail using MySQL and Nginx, wrapped up the whole setup, added a couple of users and tested to make sure all was working good.

Once that was done, I installed Apache2 (I am on Debian Wheezy), then setup a second IP address and bound Apache2 to that IP address.  I then setup mod_rewrite to rewrite all HTTP to HTTPS.

Once that was tested good, I installed D-Push from the Debian repos.  apt-get install d-push, let it work it's magic and then set the needed configuration in the BackendIMAP and config.php.

Once that was done, I restarted Apache2 with service apache2 reload and setup a test account that I created when I setup iRedmail.  All works like a charm.

I currently have about 125 users using it on a daily basis, has been running for about a week and a half now and no problems at all.  It does use some resources, but not a lot.  I am running iRedmail on 8 core 16GB RAM system.  Once I get it loaded up with around 1500-2000 users, I will try to update and let everyone know how it is runnning.

If anyone would like more indepth instructions or need any assistance, feel free to reply to this thread and I will chime in as soon as I can.

In my opinion, this adds functionality to iRedmail that makes it out perform systems like Kolab or Zimbra.  Now all I need is parity in functionality from the calendar perspective and I will start replacing all of my email servers running those other two with iRedmail.

Thank you for such a great project, I really appreciate it and hope you keep it going!

Right.  They are not the same, but provide similar functionality.  Z-push or D-push provide for RPC over HTTPS (or HTTP), which is much easier to configure from an end user perspective, with only needing to provide a single url in nearly any modern email client, not just Outlook.  It also provides for auto discover, which reduces support calls by a metric ton!

So, yes, you can use IMAP IDLE, but you can also use ActiveSync and reduce configuration headaches...which is what I was shooting for.