Wietse Venema: > Diego Liziero: >> Mmm.. If I recall correctly I had a similar issue that has been solved >> by increasing the default_process_limit. >> >> Postfix logged the same "lost connection after CONNECT from >> localhost", but postfix was not even bound to localhost. >> >> No packet were passing on lo interface, and sniffing on the ethernet >> showed that the connections were from external ip different from >> localhost, that timed out before postfix could serve them. >> >> Is this case fixed by version 2.5.5? > > This is fixed by increasing the process limit or by removing > time-consuming anti-spam features from Postfix :-)
Yes, definitely. > Postfix reports a broken connection as coming from "localhost" only > when the kernel reports an errno of ENOTSOCK. Forgive me if I'm asking something you might have already answered, is it easy to change the wrong error message for this case to something that could point the user to the fact that the socket disappeared before postfix could serve it? or at least changing the word "localhost" with something like "unknown"? Regards, Diego.
