[SM-USERS] Development roadmap: 1.2.11 vs 1.40
Is 1.4.x going to be the follow-on to the 1.2.x versions? I'm not sure if both these versions are proceeding in parallel, or if the 1.2.x versions will be replaced by 1.4.x. I'm curious because the release date on 1.2.11 is newer than that for 1.4.0. I'll be upgrading soon from 1.2.8... is it best to skip 1.2.11 and go directly to 1.4.0? How stable is the 1.4.0 "candidate?" I'd prefer not to go through 1.2.11 if we'll all end up at 1.4.0 anyway. Thanks! Neall --- This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] warning when viewing one particular folder
The following warning appears when getting the folder list of my "sent-mail" folder. It doesn't appear when viewing any other folders. htmlspecialchars() expects parameter 1 to be string, array given in /usr/share/squirrelmail/functions/mailbox_display.php on line 91 Any clues on what it means or how to elminate? Sincerely, Neall --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] Failure in delete_move_next
Hello all. I sometimes get a "Warning: Invalid argument supplied for foreach() in /usr/share/squirrelmail/plugins/delete_move_next/setup.php on line 64" when moving a mail from one box to another. Is this something in my imeplementation? It doesn't happen all the time. Maybe this should be a "plugin list" question but this plugin comes standard with SM distro. Thanks! Neall SM 1.4.0, Apache 2.0, PHP 4.2, Redhat 9, up-imapproxy-1.1.5, phpaccelerator1.3.3r2. --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] imapproxy configuration
I had no problem running the imapproxy configuration under the same setup as yours (RH 9). You need to start the service using (as root) "service imapproxy start". Yes, their scripts are sparse, but I installed them and they worked. Try "ps aux | grep imapproxy" afterwards to see if your in.imapproxyd process is running. If you want to start it automatically at boot (say, in init level 3 or 5), then use "chkconfig --level 35 imapproxy on". I'm not a fan of directly editing .rc text files. I always use "service" or "chkconfig" commands to do that for me, automatically. Neall --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] Failure in delete_move_next
Hello all. Sorry if this is a repost.. I didn't see it show up when first sent last week. Sometimes I get a "Warning: Invalid argument supplied for foreach() in /usr/share/squirrelmail/plugins/delete_move_next/setup.php on line 64" when moving a mail from one box to another. This usually happens when moving the LAST message in my inbox to my read-mesages folder, and when moved while directly viewing the message and NOT from the message list. Is this something in my imeplementation? Maybe this should be a "plugin list" question but this plugin comes standard with SM distro. Even when I get the error, the message is properly moved. IT's just that it annoys the users. Thanks! Neall Stats: SM 1.4.0, Apache 2.0, PHP 4.2, Redhat 9, up-imapproxy-1.1.5, phpaccelerator-1.3.3r2. --- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
re: [SM-USERS] Error message report
> Date: Fri, 13 Jun 2003 15:46:25 -0700 (PDT) > From: Paul Lankow <[EMAIL PROTECTED]> > To: SquirrelMail List <[EMAIL PROTECTED]> > Subject: [SM-USERS] Error message report > Sometimes, when I delete the last email in a folder, I get the following > error message (it is displayed twice). In this case, I selected "Trash" > and hit the "Move" button. I do have the delete_move_next plug-in > installed, and use it frequently, but not this time. The email does > delete and SM keeps going -- no harm is done. > Warning: Invalid argument supplied for foreach() in >/usr/share/squirrelmail/plugins/delete_move_next/setup.php on line 64 > Regards, > Paul Bingo. I had this exact error. I posted about it (twice) here about a month ago, and got no replies. What I ended up doing is using the old php.ini from my trusty RedHat 7.3 system (php 4.2.2-17), and moving it to my SM system (also running 4.2.2-17) and RedHat 9 and the problems disappeared. Interesting that they're both running the same php version, but the 7.3 php.ini is rather different from the one in the more recent RedHat 8.0 or 9. I can send you the php.ini if you'd like, or maybe a SM expert would like to look at it. I didn't bother doing a 'diff' (against the RedHat 8.0 version) beyond acknowledging that they're different. That is, I didn't try to narrow it down to the offending statement. I had posted here maybe six months or a year ago that the php.ini versions with RedHat 8.0 and 9 do induce SM errors that the older (RedHat 7.2 and 7.3) php.ini files don't. That's obviously still true, given the delete_move_next error we've both experienced. Are you running RedHat 8.0 or 9? That would show the error is consistent. Neall --- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
