-
Adopted. Thank you.
2010-01-05 08:56:45 UTC in SquirrelMail
-
You are using a very old version (you don't give any information about your environment). The first error you found was fixed in August 2006. The second one is likely also fixed in our latest version.
2010-01-05 08:13:29 UTC in SquirrelMail
-
Thanks for the feedback.
2009-12-20 20:23:10 UTC in SquirrelMail
-
Another change was just made to 1.4.20 SVN a couple days ago. I suggest you download the newest 1.4.20 snapshot and try again. If you STILL see a problem, you'll have to provide more details about your IMAP server and the kind of search you are performing.
2009-12-18 07:11:12 UTC in SquirrelMail
-
pdontthink committed revision 13878 to the SquirrelMail SVN repository, changing 2 files.
2009-12-18 06:46:16 UTC in SquirrelMail
-
pdontthink committed revision 13877 to the SquirrelMail SVN repository, changing 1 files.
2009-12-14 21:18:29 UTC in SquirrelMail
-
Looks a little like quoteString() is broken in this case. What about var_dump($escape); ?.
2009-11-24 07:59:51 UTC in SquirrelMail
-
However, the ESCAPE clause is typically only needed if the escape character is something other than \. If we remove it from this query, we gain compatibility with setups that appear to be broken as in the submitter's case. OTOH, adding ESCAPE to all DB searches is more consistent and adds even more clarity to the code.
2009-11-24 07:53:09 UTC in SquirrelMail
-
pdontthink committed revision 13872 to the SquirrelMail SVN repository, changing 1 files.
2009-11-19 20:09:06 UTC in SquirrelMail
-
Thanks for your interest and contribution.
The solution you describe is not the definitive way to implement one-time passwords. This kind of functionality can differ wildly between implementations, therefore is a perfect candidate for a plugin (there are already a couple OTP plugins). Please consider plugin implementations. There is a hook that is called during the error display which...
2009-11-14 05:51:11 UTC in SquirrelMail
