[9fans] now the real reason ... tls mail

["ron minnich" <rminnich@gmail.com>]

I'm following the instructions (I think) so that macos can read mail
over imap4d over tls.

I have used the openssl command to create cert.pem and imap.pem.

I have copied key.pem over and done the factotum dance:

I get something like this (not all of it)
key proto=sshrsa size=1024 ek=10001 n=etc.

Should that really be sshrsa?

error is this:
roo May 28 18:48:29 76.103.89.146!62583 tls reports recv ClientHello
	version: 0301
	random: 0000000000000000000000000000000084e03cff91e9bedc11b09821c53f7526
	sid: []
	ciphers: [2f 5 4 35 a ff83 9 ff82 3 8 6 ff80 32 33 34 38 39 3a 16 15
14 13 12 11 18 1b 1a 17 19 1 ]
	compressors: [00 ]

roo May 28 18:48:29 76.103.89.146!62583 tls reports ClientHello version 301

roo May 28 18:48:29 76.103.89.146!62583 tls reports   cipher 5,
compressor 0, csidlen 0

roo May 28 18:48:29 76.103.89.146!62583 tls reports tlsError:
factotum_rsa_open: no key matches proto=rsa service=tls role=client

roo May 28 18:48:29 76.103.89.146!62583 tls reports failed: no key
matches proto=rsa service=tls role=client

the proto in factotum is sshrsa, is there any way that can match rsa?

Even if I change that, the error changes not. Even if I add
service=tls role=client, the error changes not.

So, I am working with multiple levels of my own lack of understanding.
Any clues here?

I'm even more ocnfused since I can't figure out how macos mail is
going to deal with this, I never having seen any step where I give it
a key or certificate or some such. But, then, I have a way of screwing
this stuff up.

thanks

ron