It seems like using -o on tcpserver fixed this problem. -o stops tcpserver
from calling setsockopt().
Discovered by running qmail-smtpd from inetd from where it worked just
fine.
Regards.
On Mon, Apr 03, 2000 at 09:04:53AM -0500, Bruno Wolff III wrote:
> This sounds a little like a problem tha
This sounds a little like a problem that was reported to the bugtraq
list last week.
There are some places that are sending back broken packets. From memory,
it was in response to pactkets setting socket options and these options
were sent back as data. This primarily affects linux systems.
On Sa
Greetings,
I'm having a problem whereby SMTP connections from certain mail-servers work
fine and from other servers there is a big problem (all packets appear to
disappear or get disregarded). Most of the ISP's servers fail (including the
secondary MX).
The ISP has:
1) Traced the packets as far
