![]() ![]() Compatible with "plugin updates" pluginĭescription: Works with the changes to the login form.ĭescription: Works with the focus_change plugin.Make sure to download the Compatibility plugin in order for Password Forget to function correctly. New setup.php format for better overall SquirrelMail performance.Updated for compatibility with SquirrelMail version 1.4 (NOTE - requires 1.4 from cvs as of 16/03/03).This extra decoding library provides additional support for some complex Eastern and Apple x-mac character sets. SquirrelMail Webmail decoding functions are used to display and convert messages encoded in different character sets. Updated for compatibility with plugin updates plugin/plugin specs (7,789kb) (2 d/l) Extra Decoding Library.Added ability to turn plugin off for certain known clients.Requires: SquirrelMail 1.0.1, Compatibility plugin Update to work with SquirrelMail 1.5.2+.This plugin will now also attempt to "tell" the browser not to cache usernames/passwords (by using the "autocomplete" attribute on the input form tags).Please support this plugin's development: Donate to this author The administrator may, if desired, specify a list of "known clients" for which this functionality will be disabled (for the case when some users should be allowed to harness this browser feature to their benefit when at their home computers). Please note that in some cases, the browser may still remember user credentials (perhaps on some older or more obscure browsers), however the chances that a same-named username or password field would be displayed again on that computer are very small. The browser is also asked specifically not to cache these fields. This plugin provides a workaround for this vulnerability, wherein the name of the username and password input fields is changed randomly every time the SquirrelMail login page is displayed. Especially on public-access computers, this could pose the risk of stolen user login credentials. We found that, when those were created, we rarely got time outs unless the mail box was large.Many web browsers provide the capability to store all usernames and passwords entered on any web site. This causes Courier-Imap to fail, because it needs those folders to work. What is happening is the subscribed folders do not have a new, tmp, and cur folder. We even had problems with old users who we had converted from mbox to Maildir. I'm sure this is not the optimum fix as there may be other issues that would cause parseAddress to fail. $addr_end = (strpos($address,'>',$addr_start)!=false)?strpos($address,'>',$addr_start):strlen($address) $addr_end = strpos($address,'>',$addr_start) Malformed email addresses caused parseAddress to go into a loop. I had done chmod +t $HOME and forgot to do -t. But the problem turned out to be different. In the function parseAddress (somewhere around line 435) the length of the address to parse is computed using '$j = strlen($address) ' after that I inserted 'if ($j>1000) return "" '. It seems as if squirrelmail has problems parsing a malformated address. Two of our users had a similar problem displaying their mailbox.įatal error: Maximum execution time of 30 seconds exceeded in /var/www/html/mail/functions/imap_general.php on line 4xx When a user with a huge amount of mail logs in it would give the timeout error above. I'm had a similar problem, I'm running this on debian and apache-ssl. chowning to the correct user/group fixed the problem. The files were created as root and thus I had created a file ownership problem. While tinkering with Courier-IMAP I had manually created some folders from the Linux box's command line (as root). Occasionally it would reference line 109, 111, etc. I was able to send email while logged in to the Squirrelmail web interface and said email would always go to the intended recipient(s), but I would, after 30 seconds, get the error message that Steven mentions above. My fix (and situation), however, was somewhat different. I encountered a similar error on a Debian GNU/Linux (2.2.19) setup running Apache 1.3.26, Exim 3.35 and Courier-IMAP. I suspect this is related to using postfix Maildir and courier-imap-ssl (and, in fact, may simply be a courier-imap bug). To fix it, send an email to the user in question. I found that if I added a new user, the user cannot login - you get a single-line error message:įatal error: Maximum execution time of 30 seconds exceeded in /usr/share/squirrelmail/functions/imap_general.php on line 86 I encountered this problem with debian gnu/linux, apache, postfix, courier-imap-ssl. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |