Bug #51653 [Fbk->NoF]: setting imap_timeout() too low can lock directories

Edit report at https://bugs.php.net/bug.php?id=51653&edit=1 ID: 51653 Updated by: php-bugs@lists.php.net Reported by: travis at shadowglen dot com Summary: setting imap_timeout() too low can lock directories -Status: Feedback +Status: No Feedback Type: Bug Package: IMAP related Operating System: Linux PHP Version: 5.2.13 Assigned To: cmb Private report: N New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. Previous Comments: ------------------------------------------------------------------------ [2020-10-16 13:54:04] cmb@php.net This doesn't look like a bug in PHP (but rather in libc-client), or do you have evidence otherwise? ------------------------------------------------------------------------ [2010-04-24 14:48:38] travis at shadowglen dot com Description: ------------ The following was placed at the top of a mailing list script, which logs into an account to check for messages, then repackages the message and sends it to the mailing list subscribers using the mail() function. imap_timeout(IMAP_OPENTIMEOUT, 2); imap_timeout(IMAP_READTIMEOUT, 2); imap_timeout(IMAP_WRITETIMEOUT, 2); imap_timeout(IMAP_CLOSETIMEOUT, 2); Later in the script, I call imap_open(), specifically using connection to {localhost:993/ssl/no-validate-cert} if this makes a difference, unsure. Periodically ran into an issue where the mail() call would simply stop returning true -- but for the directory the script is located in only. I set up a second script, that simply tests the mail() function -- I place it in the directory where the locked-up script is located and mail() returns false. Any other directory, mail() will return true. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=51653&edit=1