"acoliver" wrote: Yeah lets think of it around M3.
I read this too late and already did some changes that enable POP3/SSL. I added a new attribute to ServerMBean named "UsesSSL" that will cause the server to open a secure socket. So to support POP3/SSL (actually with this implementation it could also be IMAP, etc.../SSL) one has to configure another ServerMBean and name it accordingly, e.g.
Using this approach one can configure the server-parameters individually for secure and non-secure sessions, which might be an issue because of the different workload a secure connection causes.