Thanks Wietse! I was indeed closing the connection, however after sending my action= reply. Why would Postfix then think there's an error. Before coding it this way, I also checked your manual and there was nothing about closing or not closing the connection (when there is no error).
Anyway, I removed it, but it turned out everything got even slower instead of faster; Postfix connections came in 1 per 5 or 6 seconds or so. So then I realized I can only configure 1 client side socket for Postfix (I was using a unix domain socket / pipe), which logically should create a problem too. So I just changed everything into tcp sockets, result: Not closing the client socket myself: Slow. With closing the client socket myself: Yeeee, fast!!! I am happy now, I guess switching over to tcp did the trick! -- View this message in context: http://postfix.1071664.n5.nabble.com/Postfix-check-policyd-service-no-concurrent-connections-tp82254p82258.html Sent from the Postfix Users mailing list archive at Nabble.com.
