Re: postscreen: getpeername: Transport endpoint is not connected

2009-12-13 Thread Wietse Venema
Stefan Foerster: > After a few years of Postfix, one usually knows all warnings and > errors it reports. With the addition of postscreen(8), there appeared > two new warnings that I don't know yet: > > postscreen[8790]: warning: getpeername: Transport endpoint is not connected > postscreen[8790]:

Re: postscreen: getpeername: Transport endpoint is not connected

2009-12-13 Thread Stefan Foerster
* Sahil Tandon : > On Sun, 13 Dec 2009, Stefan Foerster wrote: > > postscreen[8790]: warning: getpeername: Transport endpoint is not connected > > postscreen[8790]: warning: write unknown_address:unknown_port: Connection > > reset by peer > > I think these messages in your log correlate with a '4

Re: postscreen: getpeername: Transport endpoint is not connected

2009-12-13 Thread Sahil Tandon
On Sun, 13 Dec 2009, Stefan Foerster wrote: > After a few years of Postfix, one usually knows all warnings and > errors it reports. With the addition of postscreen(8), there appeared > two new warnings that I don't know yet: > > postscreen[8790]: warning: getpeername: Transport endpoint is not co

postscreen: getpeername: Transport endpoint is not connected

2009-12-13 Thread Stefan Foerster
After a few years of Postfix, one usually knows all warnings and errors it reports. With the addition of postscreen(8), there appeared two new warnings that I don't know yet: postscreen[8790]: warning: getpeername: Transport endpoint is not connected postscreen[8790]: warning: write unknown_addres