[Evolution-hackers] Re: [Evolution] Sieve support

[Dan Winship <danw ximian com>]

> This generally means that it's pretty hard to create a rule-based GUI
> for it unless you add comments to the script that indicate that it's
> generated code.
> 
> Example:
> 
> # <evolution:sieverule name="Apple Newslists">
> if address :contains "From" "noreply adc apple com" {
>         fileinto "INBOX.Newsletters";
>         stop;
> }
> # </evolution:rule>

Yes, that's basically what I was imagining. The easiest way would be to
say that the user isn't allowed to edit the sieve script by hand.
Although if the server supports the sieve "include" extension, then the
evo rules could be saved to one file and then the user could include
that into the main ruleset himself.

A similar hack could be used with procmailrc (using scp to move it
to/from the mail server). (Coincidentally, I happen to have the same
rule in my procmailrc:

        :0
        * ^From:.*adc\.apple\.com
        .misc.apple/

:-)

> Whew, I finally got that 1.5 compiled from CVS. Is it actually possible
> to install the gtkhtml-component like evo-db3 and evo-openldap in a
> different location? Otherwise it conflicts with my Ximian Desktop 2.0
> installation.

Yes, just specify --prefix when autogen'ing. (That prefix will need to
be in your PATH, and you'll need to edit
/etc/bonobo-activation/bonobo-activation-config.xml)

> ps. <whining like="HIG people">Btw, perhaps I should file this as a bug
> on bugzilla in stead of whining about it here but .. to me it's not
> clear what the difference between a Rule and a Filter is in Evolution.
> Are they the same?

In the code, "rule" means "either a filter or a vfolder", but I have no
idea if that's used consistently in the UI or not. (I also tend to say
"rule" when talking about what Evo calls "filters" just because I've
gotten used to the Exchange terminology.)

-- Dan