search

felix / gross

Greylisting of suspicious source (exported from code.google.com/p/gross)
Other
5 stars 0 forks source link

Separate policy servers and greylisting engine #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What's the problem with the current implementation?
If there is a problem with the greylisting engine, such as running out of
allocatable memory or available file descriptors, the entire engine dies,
causing Postfix to reject every piece of mail with a temporary failure code
and the message "Server configuration error".

What would you like to be done?
Separate the policy servers from the greylisting engine so that if the
greylisting engine dies it doesn't take the policy servers down with it. 
This means then that if the greylisting engine dies and can't be contacted
by the policy server, the policy server can respond to Postfix with "DUNNO"
so that the message is allowed through to any other rules in the filtering
chain.

Original issue reported on code.google.com by skaa...@gmail.com on 18 Sep 2008 at 12:41

GoogleCodeExporter commented 9 years ago 
A general Postfix policy proxy server could be useful tool with other policy 
servers, also. I'll have to think about 
this.

Original comment by eino.tuominen@gmail.com on 25 Sep 2008 at 10:50

GoogleCodeExporter commented 9 years ago

Original comment by eino.tuominen@gmail.com on 1 Dec 2008 at 11:02

GoogleCodeExporter commented 9 years ago 
Hey, thanks for accepting my enhancement idea.  I hate to sound pushy, but what 
kind
of timeframe would you put on developing this?

Original comment by skaa...@gmail.com on 1 Dec 2008 at 9:18