Loading ...
Sorry, an error occurred while loading the content.

Re: Postfix stable release 2.8.1 available

Expand Messages
  • Jeroen Geilman
    ... My head is hanging in shame. It s caused by a remote SMTP alive check I do myself - connect, then drop. -- J.
    Message 1 of 9 , Feb 25, 2011
      On 02/25/2011 08:58 PM, Wietse Venema wrote:
      > Jeroen Geilman:
      >> I upgraded to these packages, thanks for that.
      >> However, I was hoping the fixes mentioned by Wietse would also get rid
      >> of the incessant "postfix/postscreen[25978]: warning: getpeername:
      >> Transport endpoint is not connected -- dropping this connection"
      >> messages in my logs.
      > I can't fix a "problem" that no-one tells me about.
      >> I suppose postscreen is saying the client went bye-bye without saying
      >> bye-bye, but this happens more often than there are actual delivery
      >> attempts!
      > Perhaps the problem is that you have a bad router, or a kernel with
      > a weird implementation of accept(2).
      > For example, early Linux accept() implementations would actually
      > wake up as soon as the first SYN arrived, resulting in all kinds
      > of WTF errors when someone tried to use the socket.
      > People keep trying to "improve" software all the time.
      >> It could be valuable for troubleshooting, but for day-to-day usage - I
      >> don't care.
      > Maybe there is a real problem.
      > Wietse

      My head is hanging in shame.
      It's caused by a remote SMTP "alive" check I do myself - connect, then drop.

    Your message has been successfully submitted and would be delivered to recipients shortly.