Nobody really does, which I find extremely frustrating since sieve is supposed to be the Internet standard for mail filtering.
Fastmail sort of does, in that they use sieve rules; but last time I looked, they didn't have a managesieve interface, which means I can't just upload the sieve rules I have spent a lot of time creating on my home email server. I have to create them from scratch using Fastmail's rather clunky (IMO) interface.
As far as I can tell, no other email provider uses sieve at all.
They do allow you to provide Sieve scripts as text, but you do have to use the Web interface to upload them, under Advanced → Rules, so changes aren't readily automatable AFAIK. Unfortunately, I don't remember exactly where the enable button is for people who aren't using it already, since I'm already using it.
> They do allow you to provide Sieve scripts as text, but you do have to use the Web interface to upload them, under Advanced → Rules, so changes aren't readily automatable AFAIK.
Not only that, but I can't upload them using my email client, which has managesieve support already built in.
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.
> 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?
