Off-list, Steven Lembark wrote:
> Jeremy Howard wrote:
> > So, I've written a little C function that simply passes notifications on
to
> > a Unix socket. I've also written a pre-forking Perl daemon that listens
for
> > these notifications and reads in the information passed to the notify()
> > function. These are both attached. All you have to do then is add the
Perl
> > code to implement whatever notification you need (e.g. through instant
> > messaging, SMS, etc). Search for 'TODO' in the Perl code to find where
to
> > add it.
>
> hmmm... with minimal finagling
Nice word ;-)
> this would also be used to effect
> the delivery -- sort of like an external sieve. nice thing would
> be allowing use of Mail::Filter & friends for folderizing and
> filtering spam.
>
It would be cool if Sieve was more powerful, wouldn't it? notify() isn't the
place though--it doesn't even get passed the whole message body... Hmm...
where to do this properly... Is there anything wrong with just using
procmail as so:
http://dk.egroups.com/message/postfix-users/17202
Or see:
http://www.oreilly.de/catalog/mimap/chapter/ch09.html
(search for 'Mail Forwarding and Filtering on a Black Box').
What is the performance penalty of using Procmail? Is Sieve's performance
much better? Would it be possible to embed Perl into Cyrus (a la mod_perl
under Apache) to get both fast and flexible mail processing?
