> On Jan 24, 2016, at 11:46 PM, Andre LaBranche wrote:
>
>
>> On Jan 24, 2016, at 2:53 PM, Kyle Silfer wrote:
>>
>> Here’s another piece of info I found out by trial and error and have been
>> meaning to report.
>>
>> Apple's Contacts client refuses to connect on nonstandard ports (for
>>
On Mon, 25 Jan 2016, Sean McBride wrote:
On Sun, 24 Jan 2016 15:48:11 -0700, Kyle Silfer said:
El Capitan?s Calendar app requires TLSv1.2 handshaking which
calendarserver doesn?t provide.
That's surprising to me, because OS X Server.app doesn't seem to support
TLS 1.2 at all. My 10.11 cale
On Sun, 24 Jan 2016 15:48:11 -0700, Kyle Silfer said:
>El Capitan’s Calendar app requires TLSv1.2 handshaking which
>calendarserver doesn’t provide.
That's surprising to me, because OS X Server.app doesn't seem to support TLS
1.2 at all. My 10.11 calendar clients are able to connect to my
10.1
> On Jan 25, 2016, at 8:57 AM, Cyrus Daboo wrote:
>
> -t Slave is not meant for normal operation.
I realize that. But it has the advantage of skipping the database checks and
(apparently) succeeds in binding to Port 8443. Neither of the other two modes
get that far.
>
> I wonder if you have
Hi Jacques,
--On January 23, 2016 at 8:13:57 PM -0600 Jacques Distler
wrote:
On the other hand, starting up the server with
bin/run -n -t Slave
gets a lot further.
And, just to complete the trilogy,
bin/run -n -t Single
gets further than
bin/run -n
but not far enough to actually
