[KLUG Members] Re: help with cyrus imap ...

[Peter Buxton]

On Mon, Jun 21, 2004 at 01:24:40PM -0400, Bruce Smith was only escaped
   alone to tell thee:

> > Note that SIEVE is not a turing machine, there are deliberately lots
> > of things it can't do.
> 
> If I have a large list of email addresses in a text file I want to
> "white list", there is no way I could have sieve read a file?  And I'd
> have to create hardcoded rules for these?

No, and yes.

It's not so bad... you can automate the creation of Sieve files with a
script and then load them on your server.

> And there is no way for sieve to call an external program (C/bash/...)
> and test the return code or have it pass parameters to sieve?

No.

> I'm tempted to have sendmail use procmail for it's delivery, and have
> procmailrc deliver it's result to cyrus-imap via a pipe ...  but I
> suppose that's a bad idea?  Any reasons besides the extra overhead?

< cue heavy breathing... >

"Yes, Bruce.... < breathes > Join me and we'll write sed and awk scripts
and self-modifying .procmailrc files... < breathes, clenches fist > You
have no idea of the power of the Dark Side!"

But seriously, you can do it with cyrdeliver, assuming you leave it
setuid/gid, or if lmtpd creates its Unix Domain socket with the right
permissions.

Yeah, procmail and cyrdeliver are two more fork-execs, but for one user
you won't really notice. Especially under 2.6.x. But you MAY notice if
all your users do it. Maybe.

-- 
Though nothing is wasted, everything is spent. -- Annie Dillard