I'll answer you in private soon Beeny to not polute postfix mailing list.
Le 19/04/2014 14:44, Benny Pedersen a écrit :
if its time to test it ?
is there a maillist for this project ?
or even code download link ?
wiki ?
<>
Nicolas HAHN:
> > This is preferred usage. Closing the socket after each reply is wasteful.
>
> Thanks for the answer. Comments from Jan P. Kessler helped also.
[...]
> I see my processing childs dying after having processed 100 postfix
> requests, for the ones not dying because of the timeout.
Nicolas HAHN skrev den 2014-04-18 20:22:
This is preferred usage. Closing the socket after each reply is
wasteful.
Thanks for the answer. Comments from Jan P. Kessler helped also.
if its time to test it ?
is there a maillist for this project ?
or even code download link ?
wiki ?
This is preferred usage. Closing the socket after each reply is wasteful.
Wietse
Thanks for the answer. Comments from Jan P. Kessler helped also.
I've updated my code to keep connections opened unless a configurable
timeout. According my tests, I've new data:
- GreyLSE is now rated
Jan P. Kessler:
> > May I ask this: if we consider the policy server keep the connection
> > opened and don't close it by itself, will Postfix use the connection to
This is preferred usage. Closing the socket after each reply is wasteful.
Wietse
> Yes. I'm working on preforking (in fact, I've started to analyze
> prefork.c from Apache web server some days ago...). Threads are an
> option, but we choose forking for better isolation. Some people say
> forking and threading is basically the same in term of perfs, that's
> even written in som
Le 18/04/2014 10:17, Jan P. Kessler a écrit :
Hi,
maybe you should set up an own mailing list for GreyLSE. The are a lot
of coders at this list. If any of them would use this list to discuss
their own topics it might become somewhat confusing here.
You're right, old, historycal mailing lists e
Hi,
maybe you should set up an own mailing list for GreyLSE. The are a lot
of coders at this list. If any of them would use this list to discuss
their own topics it might become somewhat confusing here.
> - should be able to handle a lot of Postfix policy delegation requests
> per second, due to
to compile it with various DB libs... Why not...
SQL backend for greylisting and most other stuff is pretty pointless and
awkward to set up. My own perl greylister simply stores everything in
memory and easily performs 5000+ requests per second. If you need more
redundancy, you could simply
On Thu, Apr 17, 2014 at 10:05:05PM +0200, Nicolas HAHN wrote:
>
> exist. Except that the GreyLSE is built for ISP type loads (well, this is
> what I wouldl ike to focus on), and my wish was to optimize the thing
> everywhere possible. Adding abstraction layers is adding milliseconds to
> the proce
On Thu, Apr 17, 2014 at 10:55:32PM +0200, li...@rhsoft.net wrote:
> whatever backends, there needs to be at least one without an
> explicit daemon and no maintainance of the backend itself
> or a free choice
Give the OP a break, it seems he is trying to put together an
integrated tool set, rather
an no database abstraction alyer is *really not* the performance problem
to excuse a "vendor-lockin" or to say it in other words: if you start
these days a proect and the frist decision you make is what RDBMS you
will use your whole software design is broken from that moment
Again, we'll see
Am 17.04.2014 22:48, schrieb Patrick Laimbock:
> On 17-04-14 21:56, li...@rhsoft.net wrote:
> [snip]
>> frankly for a greylisting daemon there is no need for a full-featured
>> database server
>> like MySQl or PostgrSQL, in context of postfix it should at least support
>> BDB as
>> postfix does
On 17-04-14 21:56, li...@rhsoft.net wrote:
[snip]
frankly for a greylisting daemon there is no need for a full-featured database
server
like MySQl or PostgrSQL, in context of postfix it should at least support BDB as
postfix does
Why add BDB when there's LMDB? Postfix also supports LMDB and be
MySQL... :)
don't get me wrong but abstraction layers exists
http://www.tildeslash.com/libzdb/
nobody needs to write backends for every database
frankly for a greylisting daemon there is no need for a full-featured database
server
like MySQl or PostgrSQL, in context of postfix it should at l
Am 17.04.2014 21:44, schrieb Nicolas HAHN:
> In short, the GreyLSE is:
> - a daemon made with C/C++
> - needs the PostgreSQL database of the ELSE because works only with that
>
>> forget it - starting 2014 and limit to a single DB backend is crazy
>
> Hummm... It's a new tool... The possibility
In short, the GreyLSE is:
- a daemon made with C/C++
- needs the PostgreSQL database of the ELSE because works only with that
forget it - starting 2014 and limit to a single DB backend is crazy
Hummm... It's a new tool... The possibility to use other backends in the
futur is not closed speci
Am 17.04.2014 21:26, schrieb Nicolas HAHN:
> For a GNU GPLv3 open source project I'm working on - the ELSE - and about
> which I posted some time ago there, I've
> studied greylisting and various open source tools like PostGrey, or GLD (that
> seems to not be maintained any more),
> or policyd.
Hi,
For a GNU GPLv3 open source project I'm working on - the ELSE - and
about which I posted some time ago there, I've studied greylisting and
various open source tools like PostGrey, or GLD (that seems to not be
maintained any more), or policyd. I've also read
http://www.postfix.org/SMTPD_PO
19 matches
Mail list logo
