3 ms·
We don't provide MANAGESIEVE because we don't trust the Cyrus implementation code to be safe to provide over the internet! No in-principle objection to doing i
by brongondwana 11y ago
We don't provide MANAGESIEVE because we don't trust the Cyrus implementation code to be safe to provide over the internet! No in-principle objection to doing it otherwise.
My ideal would be to manage sieve scripts via an IMAP annotation, but maybe that ship is well and truly sailed.
- pdonis 11y ago> We don't provide MANAGESIEVE because we don't trust the Cyrus implementation code to be safe to provide over the internet! I'm not sure I understand. MANAGESIEVE means you send and receive text over a socket connection, which can be secured with TLS. If the text you get back is not valid per the managesieve protocol, you simply ignore it and send back an error; you don't need to trust any code on the client side and you don't need to provide any code over the internet. What is the implementation code issue?