On Tue, 17 Jun 2003, Ben Poliakoff wrote: > Given that in many environments end user interactions with sieve scripts > are mediated by web based interfaces (that don't easily lend themselves > to authentication methods like SASL/GSSAPI), how much work might it be > to implement a separate SSL wrapped "sieves" port for timsieved?
timsieved supports STARTTLS. Why do you need a separate port? > Has anyone already done this in a patch? Would anyone else like to see > this feature be available in cyrus-imapd/timsieved? Do the developers > cringe at the thought of this feature? Yes, there's no need for a sieves port with the existance of STARTTLS. Of course, sieveshell doesn't support STARTTLS, but thats more of a function of no one having done the work. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper