Hi Folks, We're using qpopper version 3.11 in standalone mode (heavy traffic) on a solaris 5.6 box and the popper periodically dies with this syslog message:
Jan 2 14:10:12 someserver popper_3.11[16332]: popper_3.11: Server: accept() error: Software caused connection abort [130] I stuck my nose into the source code that was lying around a couple weeks ago and it looked like it was failing on, go figure, an accept() call. While the server is long due for both an OS and popper upgrade, does the cause and/or solution to that problem ring any bells? Is there a quick fix or is it just the heavy traffic/load the machine is under? Does anybody know if 4.0 handles this more gracefully? Thanks for the help, I hunted around online and couldn't find anything (searchable mailing list archive would be nice...) cheers, -V Hoffman Vasilios Hoffman Junior Unix Administrator Wesleyan University voice (860) 685-3142 fax (860) 685-2401
