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 the fact it creates a child (with a max limit) for > each Postfix request, but, and this is maybe where I could see a Does that mean, that it forks when a new request arrives? Keep in mind that process forking is very expensive. Take a look at preforking (simple, lots of examples) or multi-threaded models (more complex but even more efficient). > I wanted to ask to this Postfix community if you think it would be > better to provide the GreyLSE as a standalone tiny software with its DB > schema doing only greylisting, or if having it as an add-on like today, > useable with the ELSE and its big database, integrated in the ELSE Web > UI, and integrating more features, would be something that could have > the preference of the community potentially using this kind of > software... Maybe not a question for this mailing-list... I don't know. Well, there are lots of existing and working "standalone" applications for greylisting (in fact I don't miss any features with the ones I use). So maybe it might be more promising to concentrate on the ELSE plugin approach - imho of course. > A question on Postfix (and sorry if it is an idiot one): > For now, the GreyLSE wait a Postfix connection, read the data related to > "a unique recipient", and provides the answer to postfix for this > recipient then close the TCP connection. I've seen in > SMTPD_POLICY_README.html, that Postfix can continue to send data > (keeping the same instance name) to the same TCP connection if the > policy server don't close it. > 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 > send any policy requests to the policy server for all recipients related > to the same email (same instance name) and THEN close the connection to > the policy server, or will it continue to use the same connection until > eventually it is closed by the policy server, whatever is the email in > processing (so the same TCP connection is used for multiple unrelated > emails)? Yes, the last option. It will reuse the connection: "On active systems a policy daemon process is used multiple times, for up to $max_use <http://www.postfix.org/postconf.5.html#max_use>incoming SMTP connections." [http://www.postfix.org/SMTPD_POLICY_README.html]. So, where is your code? Did I miss a link? Jan
