6 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] dynamic filtering exa...
FromSent OnAttachments
Roberto PolliJan 21, 2008 3:17 am 
Lea GrisJan 21, 2008 2:48 pm 
Roberto PolliJan 22, 2008 2:07 am 
Sam VarshavchikJan 22, 2008 4:03 am 
Roberto PolliJan 22, 2008 6:07 am 
Sam VarshavchikJan 22, 2008 4:24 pm 
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: [maildropl] dynamic filtering example: req for commentsActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jan 22, 2008 4:03:48 am
List:net.sourceforge.lists.courier-maildrop

Roberto Polli writes:

Alle lunedì 21 gennaio 2008, Lea Gris ha scritto:

to reduce the number of connection to the database, the .sql_mailfilter file can be created only when the mail contains the X-CREATEFILE header

...that process depend on some untrusted cleartext string ...

it all depends on the operations you made in maildrop

the first hypotesis was to create the .sql_mailfile for each mail

How does your hypothesis deal with the sql server being down?

How does your hypothesis deal with the sql server crashing, for some reason, while you're in the middle of reading your filter rules from it, and saving it into the rule file?

How does your hypothesis deal with other messages being delivered at the same time you're installing a new rule file? Whad do they do? What locking mechanism do you intend to use, in order to guarantee atomic rulefile updates?

This is one of those things that looks great on paper, but not so great in practice.