Hey Nigel, I am sorry for the very late reply, I simply forgot about my post to the ML.
On 16.07.2013 19:11, Nigel Kukard wrote: > I can't see any other touching of the network code. The above bugfix is > pretty important or you may be limited to under 10 mails per second. Could you explain that in a bit more detail. Postfix can connect to quite a few policyd instances concurrently (up to a 1 on 1 ratio) and scale this way, right? You also fork multiple children to serve requests concurently in cluebringer anyways. > Which version of postfix is this btw? the error indicates that policyd > saw a connection reset from postfix, is it possible to strace one > policyd process until this happens and log everything? It's postfix 2.7.1 (Debian Squeeze actually). Since this problem occurs rather seldom and only persists for a few minutes it's not easy to catch. I might try to replicate the issue on a test machine with some script hammering postfix / cluebringer with mails. Regards Christian _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
