-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, 29 Feb 2008, Stephan Bosch wrote:
Hello Stephan,
I've had a discussion about this issue with one of the editors of the
OK, I'll change that.
All clients I know have no problem with this as they are tested against CMU ManageSieve. How did you encounter this? Are you writing your own client or did you find one that breaks?
Actually, I roll my own implementation in order to debug a problem with Horde Groupware Webmail Edition v1.0.5, where one function behaves differently when using TLS or not, http://bugs.horde.org/ticket/6338 .
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHy65uVJMDrex4hCIRAtr7AKCTpa+vgozNPvffQtgg3hxfzmflpgCgxf+p 04ioDp3lGzDKYLzjLfLE5BE= =YzA9 -----END PGP SIGNATURE-----