-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Scott Lamb <[EMAIL PROTECTED]> writes:
> - it's not possible to automatically determine what's available for this, > for like a wizard to set up UCE stuff. the Sieve extension should make that > possible. But that just relegates the task to Sieve. I fail to see why standardizing on a "X-Spam" header is worse than standardizing on a Sieve "spam" extension. - From the operational point of view, the only advantage of a sieve extension is that at this point of delivery, Cyrus knows exactly whether the recipient exists, who it is, whether it is over quota etc. For instance, knowing the user would make it easier to have per-user-preferences in SpamAssassin (stored in a MySQL table.) So perhaps it would be useful to have a generic filtering extension a la Postfix content_filter in Sieve, to which all the context information of Cyrus is passed. Bob Finch's extension already goes a long way in this direction. > - users don't have as much control. I.e., they can't say "I want to use > some.random.rbl.domain" unless the admin has configured for it. I would prefer to keep the fine-tuning of SpamAssassin out of Sieve. Of course, on could imagine an extension that provides a command spamassassin "some spamassassin preference" but that precludes using, e.g., the SpamAssassin PHP configration interface. - -Hein -----BEGIN PGP SIGNATURE----- Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/> iEYEARECAAYFAjzJLZEACgkQX1+b5sUfCrSzEQCeNshIfRTdKy3X4Zh7MXAkeHbR 9rwAoIgXpZcVkEN6YT7R60esQ12GhS6U =R+8/ -----END PGP SIGNATURE-----
