Phil Dibowitz wrote:
>
> Ken Murchison wrote:
>
> >
> > Yeah, these entries might be missing from the 2.0.x manpages.
> >
> > tls_cert_file: <none>
> > File containing the global certificate used for ALL
> > services (imap, pop3, lmtp).
> >
> > tls_key_file: <none>
> > File containing the private key belonging to the
> > global server certificate.
> >
> > tls_ca_file: <none>
> > File containing one or more Certificate Authority
> > (CA) certificates.
> >
> > tls_ca_path: <none>
> > Path to directory with certificates of CAs.
> >
> >
>
> But again, I don't think it's just that they're missing from the man pages....
> because 'imapd -s' gives "invalid option -s"
You can't run imapd from the command line, so any option errors are
bogus. Check the imapd(8) manpage, it CAN do imaps.
> It seems that the imapd from 2.0.x doesn't support secure imap. If I can't run
> 'imapd -s' then 'master' can't run 'imapd -s' and if 'master' can't run 'imapd
> -s' then there will be nothing to answer once a secure connection is made to
> port 993.
Try connecting to your imaps port using:
openssl s_client -connect localhost:imaps
and I bet you'll see errors in imapd.log complaining about missing tls_*
options.
FYI, I added imaps/pop3s support to imtest/pop3test in CVS.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
