> > Example:
> >
> > # <evolution:sieverule name="Apple Newslists">
> > if address :contains "From" "[EMAIL PROTECTED]" {
> > 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.
It looks like it does support an Include extension :
http://www.ietf.org/internet-drafts/draft-daboo-sieve-include-00.txt
Found on http://www.cyrusoft.com/sieve/
But then it's still not trivial to create a Sieve-parser to parse the
scripts Into a GUI like the Filter-editor. I guess/fear that meta-data
per rule will be necessary per rule.
> 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/
>
> :-)
> 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)
So in case I installed evolution in /opt/evo/ then I have to edit
/opt/evo/etc/bonobo-activation/bonobo-activation config.xml, right?
I want to keep the Evolution which I have installed with Ximian Desktop
2.0
> 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.)
_______________________________________________
evolution-hackers maillist - [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution-hackers
