Debian Port - Completed with Instructions

The server is all Java so no issue there. Most of the issues would lie in creating the pre-compiled binaries, packaging and installer. Hard to say without trying it. First step would be to get postfix, OpenLDAP, etc all built. Currently we ship with pre-compiled binaries for Fedora and Red Hat. Ideally we'd like to have a pre-compiled binary download for several distributions, and then a distribution agnostic source download. It's on our list to expand to more platforms out of the box. We just haven't got around to it yet.

The server is all Java so no issue there. Most of the issues would lie in creating the pre-compiled binaries, packaging and installer. Hard to say without trying it. First step would be to get postfix, OpenLDAP, etc all built. Currently we ship with pre-compiled binaries for Fedora and Red Hat. Ideally we'd like to have a pre-compiled binary download for several distributions, and then a distribution agnostic source download. It's on our list to expand to more platforms out of the box. We just haven't got around to it yet.

-kevin

Have you patched or modified any of the thirdparty apps you include: Postfix, Openldap, sleepycat, or cyrus-sasl, etc? Or can we use the versions that come default with Debian?

modifications to thirdparty

cyrus-sasl/saslauthd modified to include calling to zimbra server for authentication (postfix/sasl auth). A few small configuration related changes to SA and amavisd-new. We also rely on iptables (for now anyway) to work properly - so that we can map port 80 -> port 7070 and not have to worry about running tomcat as root. I can not think of anything else we have made significant changes to.

cyrus-sasl/saslauthd modified to include calling to zimbra server for authentication (postfix/sasl auth). A few small configuration related changes to SA and amavisd-new. We also rely on iptables (for now anyway) to work properly - so that we can map port 80 -> port 7070 and not have to worry about running tomcat as root. I can not think of anything else we have made significant changes to.

So then we need to execute your versions of cyrus-sasl and amavisd-new. The other standard apps (postfix, ldap, etc) can be used as is and not your versions. We need to use your port forward for 80 -> 7070 if we don't want to run apache or another app as a proxy server correct?

You don't *have* to use the versions we ship. However it may be a safer option, to compile them that way. We've tested with them internally, and our tools are configured to expect them in certian install paths. Doesn't mean it not impossible to swap out for local versions but there may be some hidden issues.