Is ebox suitable to be installed as a public facing mail / web server, for example on a dedicated server in a hosting company, and to be the main MX for the domain, as well as master ldap server?
Has anyone implemented it in this way, or are there other recommendation?
Hi,
I tried to do something similar... and different.
Similar in that sense that I would like to use one ebox as "internet gateway", meaning, as you wrote, main MX, http/ftp proxy etc...
Different in the sense that I'm not comfortable with - shared - LDAP on this server exposed to internet.
Basically, for the time being, and unless I'm wrong in my understanding, such configuration doesn't work "out of the box" because postfix cannot be configured to forward email to internal mail server using LDAP entries to find maildrop server per user.
For what I understand, this could change with 1.4
Then LDAP usage is currently not flexible to permit access to external ldap server (that would be, in our case, an internal server so that accounts are not stored on server exposed on internet).
In my specific case, I'm also blocked with other constraints: I need to run Karmic on my Samba server to solve some network performance issue with Realtek but ebox on Karmic is a bit late compared to Hardy and Jaunty. Thus I can't really test master/slave.
Cheers,
Christian