can't change roundcube's default_host setting, partially reverts 6d259a6e

The default_host setting is a part of the internal username key. We can't change that without causing Roundcube to create new internal user accounts.

On some machines localhost is defined as something other than 127.0.0.1, and if we mix "127.0.0.1" and "localhost" then some connections won't be to to the address a service is actually running on.

This was the case with DKIM: It was running on "localhost" but Postfix was connecting to it at 127.0.0.1. (https://discourse.mailinabox.email/t/opendkim-is-not-running-port-8891/1188/12.)

I suppose "localhost" could be an alias to an IPv6 address? We don't really want local services binding on IPv6, so use "127.0.0.1" to be explicit and don't use "localhost" to be sure we get an IPv4 address.

Fixes #797

The emails were not deliverable anyway.

Add SRV to the drop-down to add a custom DNS zone. I made this change on my up-to-date install and it worked without any issues.

The hotfixes were all already applied to master in original PRs. This merge merely brings over the CHANGELOG and the updated install instructions (v0.17b=>v0.17c), including to bootstrap.sh which is what triggers v0.17c being the latest release.

Make control panel login failed messages generic - don't reveal if an email address has an account on the system.

fixes Roundcube getting stuck for some people, hopefully fixes #693

hotfix - install roundcube from our own mirror, hosted in Josh's AWS S3 account, because sourceforge is down all the time

fixes #750, see #701, see #370

was df92a10e

Make control panel login failed messages generic - don't reveal if an email address has an account on the system.