Bug #76663 [Nab]: fwrite(): send of X bytes failed with errno=32 Broken pipe

Edit report at https://bugs.php.net/bug.php?id=76663&edit=1 ID: 76663 Updated by: requinix@php.net Reported by: standus at post dot cz Summary: fwrite(): send of X bytes failed with errno=32 Broken pipe Status: Not a bug Type: Bug Package: *General Issues Operating System: CentOS, linux, windows PHP Version: 7.0.31 Block user comment: N Private report: N New Comment: >in Documentation is not anything about "Notice message" when it will fail. There is >only return false on fail. ??? fwrite works with PHP streams, which can be files or sockets or other resources. It is not possible to document every possible way that this function could present an error. E_NOTICE happens because it is a socket, and the write operation on the socket had a problem. I do not know if it is possible to get the errno from a failed fwrite on a socket. Regardless, you should *not* use @ because having those error messages is *good* because they tell you of a real problem. The code should be checking the return value from fwrite - not just for an error but in case the write operation did not transmit all the data expected, which could cause the remote server to abort the connection, which could be the source of your problem. >Its impossible catch it ? You can "catch" notices and other error messages with set_error_handler(). >Nobody knows solution because it does not exists ! Just because nobody knows the solution does not mean there is no solution at all. Except there is a solution: the code you are using is old and flawed, but you should not be using this method to verify email addresses at all so it does not matter. Previous Comments: ------------------------------------------------------------------------ [2018-07-25 17:48:33] spam2 at rhsoft dot net don't try to verify mail by bother the MX - period you can't handle grexlisting, tarpits and a ton of other spamfiter measurements only a proper smtp server which retries repeatly and handles temporary errors as defined in the according rfcs the whole point on the smtp server side is to kill spam scripts like yours - i just let you wait 15 seconds, then respond with 450 and expect that you come with the same ip not sooner than 5 minutes or you have to wait 10 minutes as Mailadmin in clear words:let the world in peace with your crap script ------------------------------------------------------------------------ [2018-07-25 17:26:08] standus at post dot cz I tried already many times and many channels and nobody knows answer. Nobody knows solution because it does not exists ! ------------------------------------------------------------------------ [2018-07-25 17:24:28] standus at post dot cz And what about my arguments: 1. in Documentation is not anything about "Notice message" when it will fail. There is only return false on fail. ??? 2. Its impossible catch it ? ------------------------------------------------------------------------ [2018-07-25 16:54:11] requinix@php.net Sorry, but your problem does not imply a bug in PHP itself. For a list of more appropriate places to ask for help using PHP, please visit http://www.php.net/support.php as this bug system is not the appropriate forum for asking support questions. Due to the volume of reports we can not explain in detail here why your report is not a bug. The support channels will be able to provide an explanation for you. Thank you for your interest in PHP. ------------------------------------------------------------------------ [2018-07-25 16:50:09] standus at post dot cz This problem happened to me every day with any long time running script. And it has not solution. Thats why I wrote this bug because I mean it must be solved in PHP function code. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=76663 -- Edit this bug report at https://bugs.php.net/bug.php?id=76663&edit=1