Joshua Tauberer 6d259a6e12 use "127.0.0.1" throughout rather than mixing use of an IP address and "localhost" ... 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		2016-05-06 09:10:38 -04:00
..
autodiscover_config.php	z-push autodiscover should use the primary hostname for the mail server and not the domain part of the email address (both may work, but the primary hostname is more likely to have a signed SSL cert)	2014-08-19 11:49:20 +00:00
backend_caldav.php	use "127.0.0.1" throughout rather than mixing use of an IP address and "localhost"	2016-05-06 09:10:38 -04:00
backend_carddav.php	use "127.0.0.1" throughout rather than mixing use of an IP address and "localhost"	2016-05-06 09:10:38 -04:00
backend_combined.php	simplify zpush configuration files, no need to preserve copyright message	2014-08-12 11:12:10 +00:00
backend_imap.php	use "127.0.0.1" throughout rather than mixing use of an IP address and "localhost"	2016-05-06 09:10:38 -04:00