Declare class variables
Declare class variables
Don't need to decode empty string/NULL
Don't need to decode empty string/NULL
Backport comments
Declare class variables
Declare class variables
Declare class variables
Declare class variables
Declare class variables
I am using PHP 8.2.1 and I am getting the same error 500
Correct docs, initialize variable
Capabilities cannot be assumed to be boolean
Fix typo
Fix PHP warning
Fix PHP warning
Fix PHP warning
Hack for problem where $i is used as both boolean and int
Hack for problem where $i is used as both boolean and int
Variable could be null
processParameters cutting of chars when charset and language have different length
PHP 8 fixes that never made their way into SVN
PHP 8 fixes that never made their way into SVN
sqspell_ereg error in php 7.2
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Fix: Don't feed an integer to sizeof()
Fix: Don't feed an integer to sizeof()
Fix broken parenthesis
Note, I messed the status up when I created this bug and forgot to change from "Cannot Reproduce" to "Produces Error". If one of the admins could update I would appreciate it. (I should be able to do it, but I can' find any widget to edit the original bug???)
Note, the effect of the error appears to be harmless. The message is not repeated when you refresh the message list, or read a message and return to the message list. So this may be a startup ordering issue?
1.5.2 SVN mailbox_display.php - Error indexing array with bool 'THREAD_INDENT'
Add TODO
Add TODO
The fix should actually be !isset($parseFetchResults['UID']))
1.5.2 svn Parenthesis missing functions/imap_messages.php on line 120
php error with EEST timezone
Test option page name, don't assign it
Remove extraneous reset
Explicitly declare formerly dynamic class property (deprecated PHP behavior)
Explicitly declare formerly dynamic class property (deprecated PHP behavior)
Refine last fix
Some IMAP servers are picky about extraneous spaces
Don't str_replace() on null values
Don't str_replace() on null values
Make sure $prefs_cache is initialized when resetting the cache
Make sure $prefs_cache is initialized when resetting the cache
Plugin mail_fetch class constructor Not PHP 8 conformal
Fix sqimap_get_small_header_list() for IMAP servers not tolerating trailing spaces in header fields
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
Happy New Year
C99 compatibility fixes for imap_proxy
Fix poorly written timezone parsing
Fix poorly written timezone parsing
Address book and PHP 8.x
Thanks for tracking this down. The fix will be in the next nightly tarball.
Remove use of each()
Remove use of each()
Backport fix from DEVEL
Fix PHP notice
That was a different (minor) issue that is now fixed.
Fix PHP notice
Restore line incorrectly deleted
Not sure if this is another bug or should be a part of the fix. When viewing an attachment from a bounceback, e.g., untitled-[3.2].delivery-status Here is a sample of what's in the attachment: Reporting-MTA: dns; ourdomain.edu Arrival-Date: Thu, 12 May 2022 06:26:39 -0400 Final-Recipient: RFC822; user@ourdomain.edu X-Actual-Recipient: rfc822; user@ourdomain.edu Action: failed Status: 4.4.7 Last-Attempt-Date: Tue, 17 May 2022 06:31:52 -0400 After updating to squirrelmail-20220607_0200-SVN I now see...
I have replaced while (list($k, $backend) = each($abook->backends)) { with foreach ($abook->backends as $k => $backend) { It solves the problem. Jan Sorensen On Sun, June 5, 2022 06:13, Jan Sorensen wrote: Now I get the error messages: Fatal error: Uncaught Error: Call to undefined function each() in /usr/local/apache2/htdocs/squirrelmail/src/addressbook.php:310 Stack trace: #0 {main} thrown in /usr/local/apache2/htdocs/squirrelmail/src/addressbook.php on line 310 Jan Sorensen On Sat, June 4, 2022...
Now I get the error messages: Fatal error: Uncaught Error: Call to undefined function each() in /usr/local/apache2/htdocs/squirrelmail/src/addressbook.php:310 Stack trace: #0 {main} thrown in /usr/local/apache2/htdocs/squirrelmail/src/addressbook.php on line 310 Jan Sorensen On Sat, June 4, 2022 19:19, Paul Lesniewski wrote: You can also try putting this code near the top of that file: ~~~ ini_set('display_errors', '1'); error_reporting(E_ALL); ~~~ And make sure to scroll down to the bottom of the...
Calendar Plugin
Thanks for reporting this. The code has been rewritten.
Remove use of each() and make sense of poorly named variables
Undefined variable $next in /usr/share/squirrelmail/src/read_body.php
Thanks for reporting this
Fix undefined variable notices
You can also try putting this code near the top of that file: ini_set('display_errors', '1'); error_reporting(E_ALL); And make sure to scroll down to the bottom of the page to see if errors are being listed on screen.
Without seeing an error message for this page, there isn't much we can do. I gave you some code to insert at the place where you said the error was showing in your logs, but as mentioned before, that place shouldn't have anything to do with the address book. You can insert such code at the top of src/addressbook.php and move it down step by step until you get the blank page at which point you've found the errant line/call. You might also try a vanilla installation of SquirrelMail with no customizaions...
Calendar Plugin
Undefined variable $next in /usr/share/squirrelmail/src/read_body.php
Add ability to explicitly set address book DB connection charset, though usually if database defaults are sensible this is not something to be concerned with in configuring SquirrelMail
Add ability to explicitly set prefs DB connection charset, though usually if database defaults are sensible this is not something to be concerned with in configuring SquirrelMail
Add ability to explicitly set address book DB connection charset, though usually if database defaults are sensible this is not something to be concerned with in configuring SquirrelMail
Add ability to explicitly set prefs DB connection charset, though usually if database defaults are sensible this is not something to be concerned with in configuring SquirrelMail
Just to clarify, yes, a newer version should fix this. Your patch also seems to not be for SquirrelMail, but for the login_auth plugin (although you don't state that specifically) and it removes login functionality with literals which are specifically more well suited for things like non-ASCII passwords -- this leads me to believe your system is doing something odd or your stored passwords are not in the format you think they are. Note you can also use SASL PLAIN authentication which could help you...
Thanks for addressing this issue. When do you plan to release the stable 1.5.x version?
Thanks for addressing this issue.
Sorry it took so long to add this, but we have completed this request. Thanks for your interest.
Nightly snapshots verification
change_pass-3.1-1.4.0 plugin issue with double poppassd result code
Thanks, I've updated that file as well
Fix PHP notice when property doesn't exist
Add contrib directory
IMAPproxy connection cleanup