In further discussions in the Sieve WG, we found at least three systems that already had a variety of Sieve scripts that run before the user's script is executed. None of those systems used the ManageSieve protocol for configuring this environment, which means we get to be the trailblazers here and spearhead writing the RFC on how this should work.
I think there's a place for simple sorting, I just want to make sure that we think it through and make sure it plays nicely with Sieve and with aliases and so on. For example, what if we used the simple sorting to build the alias rewrite rules that are being discussed right now in another thread? The same rewrite rules could be written in Sieve using variables and subaddresses. Would it make sense for an admin to log into a ManageSieve gui to configure domain aliases like this? Aaron On Fri, Dec 15, 2006, Blake Mitchell <[EMAIL PROTECTED]> said: > Just a thought, but the simple sort may be a good candidate for the > global filtering rules people have been asking for recently. I remember > you said the sieve group was looking at such an extension, but obviously > with the simple sort method, you are not trying to target a published > spec, so there is a lot more freedom to tinker. > > Aaron Stone wrote: > ... >> >> Are there things that the simple sorting can do that Sieve cannot do? >> >> Aaron >> > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > -- _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
