Forums

Resolved
0 votes
I am considering whether to make Roundcube available to my ~30 users. From the few posts, it looks like the app is far from straightforward to get working properly. But now I see that this is posted by people who chose the free option (which I didn't know existed).

I am setting up a mail server with ClearOS 7 (Business). If I install through the Marketplace and pay the $25, am I assured a troublefree install and working solution? Can I choose which port Roundcube is available under (if I've got another application using 80 and 443)? Alternatively, is there a way to bind Roundcube to a single external IP address (Virtual Interface)?
Tuesday, June 28 2016, 06:04 PM
Share this post:
Responses (2)
  • Accepted Answer

    Tuesday, June 28 2016, 06:26 PM - #Permalink
    Resolved
    0 votes
    I don't know how troublefree the installation is. I had trouble years ago because I had a prior installation using what you call the free version. Roundcubemail is installable from third party RPM's and from source, if you see my original howto. The app came later. It uses the original sources but is configured to use system-mysql rather than mysql. It also comes with sieve filtering and, I think, another tweak.

    In the normal configuration it redirects port 80 to 443 then uses that. What else do you have on 443? If it is apache, roundcubemail is just another apache app (if such a thing exists). I run it alongside a number of other web apps - Weave, vn_stat, OpenVPN monitor and so on.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 28 2016, 06:20 PM - #Permalink
    Resolved
    0 votes
    Most of the issues seen on this forum around the RoundCube app are a result of picking up upstream packages from EPEL rather than the one's provided in the clearos-contribs repo.

    If you haven't hacked around with repos, it should be 'one click' install from the Marketplace...all the bootstrapping gets done automagically.

    Roundcube can share Apache resources (and does by default) using configlets. Eg.

    http(s)://example.com/webmail
    http(s)://example.com/owncloud
    etc.

    Yes...you can hack the Apache configlet to listen/bind to a single interface instead of the default *.80/*.443.

    B.
    The reply is currently minimized Show
Your Reply