I have recently setup a new mail-in-a-box (v60) and have noticed that ActiveSync is not working. It is important to mention here that my mail-in-a-box status page is not reporting any issues whatsoever and SSL certificates have been generated and assigned.
I have tried accessing ActiveSync on mail clients ‘Mail’ and ‘Gmail’ both applications report that they are unable to add the email due to security concerns.
Has anyone else been able to get ActiveSync working with v60?
I’m not specifically sure how easy or long it will take for a fix to come as @JoshData doesn’t seem to maintain the Z-Push setup. I really wish I was a “coder” I’d like to be able to get to a place were I can make a pull-request. Any idea who was maintaining Z-Push in MiaB?
vim /usr/local/lib/z-push/backend/caldav/caldav.php
then “escape key” then : type “setnu” then enter (this gives you line numbers)
go to line 847
make sure it says this:
might need a “i” key for insert at some point here – sorry I dont know if you know vim or not…
Just a warning. After using Z-Push today with the changes indicated in my last post above, it turns out that it’s unstable. I saw strange behavior like mail folders and emails disappearing and reappearing, endless loading, etc. I also saw many errors in the Z-Push log regarding array out-of-bounds in carddav.php. It’s really not usable in this state.
I think the fundamental problem is that from what I understand, Z-Push does not yet officially support PHP 8.x. I don’t think @JoshData can do anything about it until PHP 8.0 support is added upstream by the Z-Push project. In this post, someone installed PHP 7.4 to get Z-Push to work; I don’t know what other implications this may have for MIAB - perhaps @JoshData could let us know if this is a good idea.
Any chance this issue will be fixed in an upcoming MITB release? I really don’t want to be going around messing with the filesystem just in case the patch in an upcoming release conflict with these file edits and causes it to break even more.