I really was upset when I realized I'd had to use a "SieveBridgeClient" when wanting to use the only sieve plugin existing for TB >=128... No! sieve should be possible *directly* - with or without plugin - I don't care. But if it's forbidden for plugins to communicate directly to external ports it should be integrated into the package. This may be a positive signal to other hosters to enable sieve for customers - maybe not the really big ones... Sieve is important, and would be nice to be able to use it also on mobile devices. Thank you.