41 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Filter API
FromSent OnAttachments
Bernd WurstDec 30, 2006 1:08 am 
Sam VarshavchikDec 30, 2006 6:12 am 
Bernd WurstDec 30, 2006 7:36 am 
Sam VarshavchikDec 30, 2006 8:51 am 
Bernd WurstDec 30, 2006 9:08 am 
Sam VarshavchikDec 30, 2006 9:55 am 
Aleksandar LazicDec 30, 2006 10:06 am 
Sam VarshavchikDec 30, 2006 10:24 am 
Aleksandar LazicDec 30, 2006 10:32 am 
Bernd WurstDec 30, 2006 10:34 am 
Arturo 'Buanzo' BusleimanDec 30, 2006 10:37 am 
Arturo 'Buanzo' BusleimanDec 30, 2006 10:38 am 
Bernd WurstDec 30, 2006 10:45 am 
Sam VarshavchikDec 30, 2006 11:02 am 
Aidas KasparasDec 30, 2006 11:10 am 
Aleksandar LazicDec 30, 2006 11:12 am 
Sam VarshavchikDec 30, 2006 1:42 pm 
Aleksandar LazicDec 30, 2006 2:56 pm 
Sam VarshavchikDec 30, 2006 3:56 pm 
Aleksandar LazicDec 30, 2006 5:00 pm 
Gordon MessmerDec 31, 2006 10:00 am 
Lorenzo PeroneJan 7, 2007 12:27 pm 
Julian MehnleJan 7, 2007 12:56 pm 
Sam VarshavchikJan 7, 2007 3:42 pm 
Lorenzo PeroneJan 8, 2007 6:59 am 
Gordon MessmerJan 8, 2007 8:37 am 
Lorenzo PeroneJan 9, 2007 8:33 am 
Gordon MessmerJan 10, 2007 12:34 am 
Julian MehnleJan 13, 2007 10:37 am 
Alessandro VeselyJan 14, 2007 2:46 am 
Milan ObuchJan 14, 2007 5:03 am 
Lloyd ZusmanJan 14, 2007 6:23 am 
Aidas KasparasJan 15, 2007 1:28 am 
Gordon MessmerJan 15, 2007 4:01 pm 
Gordon MessmerJan 15, 2007 4:21 pm 
Julian MehnleJan 15, 2007 4:45 pm 
Sergiy ZhukJan 15, 2007 5:42 pm 
Alessandro VeselyJan 16, 2007 1:36 am 
Gordon MessmerJan 21, 2007 7:14 pm 
Alessandro VeselyJan 22, 2007 7:58 am 
Gordon MessmerJan 22, 2007 10:02 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Filter APIActions...
From:Lorenzo Perone (lope@yellowspace.net)
Date:Jan 8, 2007 6:59:14 am
List:net.sourceforge.lists.courier-users

On 07.01.2007, at 21:57, Julian Mehnle wrote:

Lorenzo Perone wrote:

I do this by calling spamc over a courierfilter for a pre-scan, using a systemwide bayes db and systemwide settings, rejecting anything over a certain threshold, and then calling it again as xfilter over maildrop, using user bayes and user settings. In this second run SA can change anything it needs and, if recognized as spam, delivers it to a $HOME/Maildir/.Spam maildir. That doesn't make the whole thing faster, but it works very well and I'm very happy with the results.

However, this is exactly the type of inefficiency that the current design of Courier is trying to avoid. Pushing the same message through SpamAssassin twice is horrendously less efficient than saving a message to disk and then re-reading it when it comes to parsing its MIME structure would be.

I agree, but I don't see an alternative to have this kind of setup, where mail over a certain threshold is rejected (resulting in a notification of the user in case it's a false positive, yet without generating backscatter) and the rest of the spam delivered, modified, to a user-spam maildir.

Well, yes, you can. Obviously you just cannot (even just theoretically) modify the same message in several different ways.

If I understood correctly the rest of this thread, at the moment it is not a good idea to modify the message even once, within a courierfilter. So it wouldn't be possible to save a modified copy, which is desired in my as well as in other setups.

But subjecting it to different per-user accept/reject rules isn't a problem.

The only, quite ugly alternative I see here: checking the message for each recipient within the courierfilter, rejecting it above a certain threshold, and below it, saving the checked, modified message copies in a temporary directory, storing it's ID in a database (for example), and then using a script in maildrop to "recover" that modified message upon delivery. But I think such a solution would really be torturing Sam's work even more ;o

It certainly would be more interesting in the future to be able to notify courier about changes, so that he can reparse it.

That said, I am very happy with the whole product and with the feedback on this mailing list (even if it is, sometimes, a bit harsh: but I learned old and new things, so thanx for all of it :))

I see. Sounds straightforward, yet the question is how widely has this been implemented.

Regards, Lorenzo