From: db <da_...@ya...> - 2003-04-04 18:37:21
|
My users get this error at times.... Fatal error: Maximum execution time of 30 seconds exceeded in /usr/local/squirrelmail-1.2.11/functions/imap_general.php on line 47 when many users try to login simultaneoulsy... --db __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com |
From: <lin...@li...> - 2003-08-19 11:27:25
|
ERROR: ERROR : Connection dropped by imap-server. Query: LOGIN "ARa...@at..." "password" I get the above error when users try to logging from one of the domain's hosted on the server, all the other domains work perfectly fine exept this one. I'm using squirrelmail 1.4.1 with courier-imap authenticating against mysql, i have checked the user premitions on the users for this domain, and they are fine , i have check the db and cant find anthing out of the ordenary.. HELP.. Many thanks .. Gregory Machin |
From: Richard G. <ric...@fh...> - 2010-08-05 08:18:52
|
Hi all, I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on CentOS 5.5 when the users wants to login, all user gets the error message "Your session has expired, but will be resumed after logging in again". No one is able to login. Yesterday everything works perfect. no changes where made!! httpd restart/Server reboot doesn't fix this problem. Whats going on? many thanks Richard |
From: Paul L. <pa...@sq...> - 2010-08-05 09:11:21
|
Please read this and review how to choose a better subject http://squirrelmail.org/postingguidelines > I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on > CentOS 5.5 > > when the users wants to login, all user gets the error message "Your > session has expired, but will be resumed after logging in again". > > No one is able to login. > > Yesterday everything works perfect. > no changes where made!! Impossible. > httpd restart/Server reboot doesn't fix this problem. > > Whats going on? You tell us. Check your logs, read the posting guidelines. Currently my crystal ball is in the shop. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Richard G. <ric...@fh...> - 2010-08-05 09:50:28
|
On 8/5/10 11:10 AM Paul Lesniewski wrote: > Please read this and review how to choose a better subject > > http://squirrelmail.org/postingguidelines sorry, was a copy/paste mistake. >> I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on >> CentOS 5.5 >> >> when the users wants to login, all user gets the error message "Your >> session has expired, but will be resumed after logging in again". >> >> No one is able to login. >> >> Yesterday everything works perfect. >> no changes where made!! > > Impossible. for me: possible ;-( > >> httpd restart/Server reboot doesn't fix this problem. >> >> Whats going on? > > You tell us. Check your logs, read the posting guidelines. Currently > my crystal ball is in the shop. ;-) I've already checked my logs (httpd/dovecot/messages/maillog/daemon.log) No errors ore something similar. I have also removed one Useraccount (from CentOS, SM pref-file, IMAP-mailbox) and recreated it. Error still exists, and for all other users. Date and time is in sync with the ntp servers. No rootkit installed ;-) Filesystems are also OK. Is there maybe are session lockfile (for the connection duration or something else) in SM available, which I should remove? as I explaned: none of our users (above 150!!!) can login to SM. everyone becomes the same error: SquirrelMail version 1.4.8-5.el5.centos.10 By the SquirrelMail Project Team ERROR Your session has expired, but will be resumed after logging in again. Go to the login page Thanks Richard |
From: michael c. <mic...@gm...> - 2010-08-05 14:45:57
|
> as I explaned: none of our users (above 150!!!) can login to SM. > everyone becomes the same error: amateur pokes out head and says. try to login user via telnet. if that is successful then have you got selinux stuff ? try turning that off. if works probably something in imap config is wonky. mick |
From: Paul L. <pa...@sq...> - 2010-08-05 20:07:38
|
>>> I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on >>> CentOS 5.5 >>> >>> when the users wants to login, all user gets the error message "Your >>> session has expired, but will be resumed after logging in again". >>> >>> No one is able to login. >>> >>> Yesterday everything works perfect. >>> no changes where made!! >> >> Impossible. > > for me: possible ;-( *Something* had to change in order for the behavior to change. It's your job to tell us what that is. >>> httpd restart/Server reboot doesn't fix this problem. >>> >>> Whats going on? >> >> You tell us. Check your logs, read the posting guidelines. Currently >> my crystal ball is in the shop. > > ;-) > > I've already checked my logs (httpd/dovecot/messages/maillog/daemon.log) > No errors ore something similar. > > I have also removed one Useraccount (from CentOS, SM pref-file, > IMAP-mailbox) and recreated it. > > Error still exists, and for all other users. > > Date and time is in sync with the ntp servers. > No rootkit installed ;-) > Filesystems are also OK. > > Is there maybe are session lockfile (for the connection duration or > something else) in SM available, which I should remove? You could start by deleting all PHP session files, or at least all those that contain SquirrelMail data. Also clear all cookies in your browser (although you might not want to do that if you want to mimic your users who probably won't be able to figure out how to do that). You could also do things like show your PHP session timeout value and try increasing it. Also show your plugins and try running with NO plugins activated to see if that helps. > as I explaned: none of our users (above 150!!!) can login to SM. > everyone becomes the same error: > > SquirrelMail version 1.4.8-5.el5.centos.10 > By the SquirrelMail Project Team > ERROR > Your session has expired, but will be resumed after logging in again. > Go to the login page -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: James B. B. <by...@ha...> - 2010-08-05 14:05:32
|
On Thu, August 5, 2010 04:04, Richard Gliebe wrote: > Hi all, > > I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on > CentOS 5.5 > > when the users wants to login, all user gets the error message "Your > session has expired, but will be resumed after logging in again". > > No one is able to login. > > Yesterday everything works perfect. > no changes where made!! > > httpd restart/Server reboot doesn't fix this problem. > > Whats going on? > > many thanks > Richard > The only time that I have seen this problem with SquirrelMail was when our webmail service was under a brute force password attack and the /var/lib/ partition filled up with php session identifiers. Check your file system free space with df. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 |
From: Paul L. <pa...@sq...> - 2010-08-05 19:52:14
|
On Thu, Aug 5, 2010 at 6:47 AM, James B. Byrne <by...@ha...> wrote: > > On Thu, August 5, 2010 04:04, Richard Gliebe wrote: >> Hi all, >> >> I get this morning a great problem with SM 1.4.8-5.el5.centos.10 on >> CentOS 5.5 >> >> when the users wants to login, all user gets the error message "Your >> session has expired, but will be resumed after logging in again". >> >> No one is able to login. >> >> Yesterday everything works perfect. >> no changes where made!! >> >> httpd restart/Server reboot doesn't fix this problem. >> >> Whats going on? >> >> many thanks >> Richard >> > > The only time that I have seen this problem with SquirrelMail was > when our webmail service was under a brute force password attack and > the /var/lib/ partition filled up with php session identifiers. > Check your file system free space with df. Note that the Lockout plugin could probably have prevented that situation. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Res <re...@au...> - 2010-08-05 23:50:26
|
On Thu, 5 Aug 2010, Paul Lesniewski wrote: >> The only time that I have seen this problem with SquirrelMail was >> when our webmail service was under a brute force password attack and >> the /var/lib/ partition filled up with php session identifiers. >> Check your file system free space with df. > > Note that the Lockout plugin could probably have prevented that situation. > That plugin is life saver, everyone should be using it, IMHO. -- Res "What does Windows have that Linux doesn't?" - One hell of a lot of bugs! |
From: Paul L. <pa...@sq...> - 2010-08-06 04:55:56
|
On Thu, Aug 5, 2010 at 9:46 PM, Richard Gliebe <ric...@fh...> wrote: > On 8/5/10 9:51 PM Paul Lesniewski wrote: >>> The only time that I have seen this problem with SquirrelMail was >>> when our webmail service was under a brute force password attack and >>> the /var/lib/ partition filled up with php session identifiers. >>> Check your file system free space with df. >> >> Note that the Lockout plugin could probably have prevented that situation. > > strange: this morning, SM works, as i should. > > Lockout plugin will be installed as soon as possible. > > FYI: > filesystems (special: /var/lib) are OK and was always OK (monitoring by > nagios) > SELinux is and was disabled. > No bruteforce attack or something similar yesterday. > login via telnet also failed. Then it's not a SquirrelMail problem. Check your IMAP server log to see why the login was rejected. If it doesn't tell you anything, your logging verbosity is too low. Further questions should be directed to the community that supports your IMAP server. > onesmore: no changes where done in SM. > PHP sessions where maybe deleted by rebooting the hole server. Unless you have a special system set up, rebooting will not purge PHP session files. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Paul L. <pa...@sq...> - 2010-08-06 07:11:26
|
On Thu, Aug 5, 2010 at 10:28 PM, Richard Gliebe <ric...@fh...> wrote: > On 8/6/10 6:55 AM Paul Lesniewski wrote: > >> Then it's not a SquirrelMail problem. Check your IMAP server log to >> see why the login was rejected. If it doesn't tell you anything, your >> logging verbosity is too low. Further questions should be directed to >> the community that supports your IMAP server. > > hhmmm. Client connects to our IMAP Server (dovecot) with > Thunderbird/Outlook/Entourage worked without any problems. Make up your mind. All IMAP clients should use the IMAP LOGIN command. You said you telnetted to your IMAP server and it failed. At the time that it failed, all IMAP clients will not work. Maybe your telnet test was incorrect. You didn't show any details. > Yesterday I've checks the dovecot.log. No Client connect errors. > > To prevent telephone terror, I've installed yesterday quick'n dirty > 'open-webmail'. > No connect problems with this app. If there were problems with SquirrelMail at the same time, then your telnet adventures should have been working at that time. If that's the case, then your PHP settings are probably borked. >>> onesmore: no changes where done in SM. >>> PHP sessions where maybe deleted by rebooting the hole server. >> >> Unless you have a special system set up, rebooting will not purge PHP >> session files. > > After rebooting the server, a 'ps' and 'lsof' doesn't showed my any php > zombi processes and any php sessions files associated with SM. > > I also took a look into /var/lib and /usr/share where SM keeps its > Files. Everything looked fine. > > anyway, I'll upgrade our SM installation to the newest release, and > looking forward to see what happens. > > If SM failes onesmore, there is open-webmail (standby) available on our > system ;-) I doubt it's SquirrelMail "failing" - instead, it's likely your IMAP server or a PHP issue. But you haven't provided enough (non-contradictory) information for us to guess any more than has been guessed. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Richard G. <ric...@fh...> - 2010-08-06 04:46:46
|
On 8/5/10 9:51 PM Paul Lesniewski wrote: >> The only time that I have seen this problem with SquirrelMail was >> when our webmail service was under a brute force password attack and >> the /var/lib/ partition filled up with php session identifiers. >> Check your file system free space with df. > > Note that the Lockout plugin could probably have prevented that situation. strange: this morning, SM works, as i should. Lockout plugin will be installed as soon as possible. FYI: filesystems (special: /var/lib) are OK and was always OK (monitoring by nagios) SELinux is and was disabled. No bruteforce attack or something similar yesterday. login via telnet also failed. onesmore: no changes where done in SM. PHP sessions where maybe deleted by rebooting the hole server. many thanks Richard |
From: Richard G. <ric...@fh...> - 2010-08-06 05:28:16
|
On 8/6/10 6:55 AM Paul Lesniewski wrote: > Then it's not a SquirrelMail problem. Check your IMAP server log to > see why the login was rejected. If it doesn't tell you anything, your > logging verbosity is too low. Further questions should be directed to > the community that supports your IMAP server. hhmmm. Client connects to our IMAP Server (dovecot) with Thunderbird/Outlook/Entourage worked without any problems. Yesterday I've checks the dovecot.log. No Client connect errors. To prevent telephone terror, I've installed yesterday quick'n dirty 'open-webmail'. No connect problems with this app. > >> onesmore: no changes where done in SM. >> PHP sessions where maybe deleted by rebooting the hole server. > > Unless you have a special system set up, rebooting will not purge PHP > session files. After rebooting the server, a 'ps' and 'lsof' doesn't showed my any php zombi processes and any php sessions files associated with SM. I also took a look into /var/lib and /usr/share where SM keeps its Files. Everything looked fine. anyway, I'll upgrade our SM installation to the newest release, and looking forward to see what happens. If SM failes onesmore, there is open-webmail (standby) available on our system ;-) Richard |
From: Richard G. <ric...@fh...> - 2010-08-06 07:42:49
|
On 8/6/10 9:10 AM Paul Lesniewski wrote: > Make up your mind. All IMAP clients should use the IMAP LOGIN > command. You said you telnetted to your IMAP server and it failed. > At the time that it failed, all IMAP clients will not work. Maybe > your telnet test was incorrect. You didn't show any details. telnet session failed meens, I also got the "session expired" error message. maybe the precompiled version of SM for CentOS 6.x is buggy. anyway, I'll install the newest tar.gz ball vom squirrelmail.org. many thanks Richard |
From: Paul L. <pa...@sq...> - 2010-08-06 07:56:27
|
On Fri, Aug 6, 2010 at 12:42 AM, Richard Gliebe <ric...@fh...> wrote: > On 8/6/10 9:10 AM Paul Lesniewski wrote: > >> Make up your mind. All IMAP clients should use the IMAP LOGIN >> command. You said you telnetted to your IMAP server and it failed. >> At the time that it failed, all IMAP clients will not work. Maybe >> your telnet test was incorrect. You didn't show any details. > > telnet session failed meens, I also got the "session expired" error message. The "session expired" error is an error message from SquirrelMail. It is impossible to get it directly from the IMAP server, since it has no knowledge of such a string. Please give accurate information and don't pollute mailing list archives that people might be using in the future to diagnose their problems. If you used telnet to try an IMAP login, then cut and paste the exact details. > maybe the precompiled version of SM for CentOS 6.x is buggy. > anyway, I'll install the newest tar.gz ball vom squirrelmail.org. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Dougan, L. A <DOU...@gr...> - 2011-06-13 19:03:01
|
SquirrelMail version: 1.4.7 Config file version: 1.4.0 Config file last modified: 10 June 2009 15:40:00 Checking PHP configuration... PHP version 5.3.6-pl0-gentoo OK. PHP extensions OK. Checking paths... After upgrading php I getting this error. Warning: Invalid argument supplied for foreach() in /var/www/nutsmail/functions/attachment_common.php on line 44. I corrected all of the errors seen below before finally getting the error seen above, "Warning: Invalid argument supplied for foreach() in /var/www/nutsmail/functions/attachment_common.php on line 44". Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/php/DB.php on line 470 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/php/DB.php on line 547 Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/php/DB.php on line 1202 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_unregister() is deprecated in /var/www/nutsmail/functions/global.php on line 209 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function eregi() is deprecated in /var/www/nutsmail/functions/imap_general.php on line 650 Deprecated: Function eregi() is deprecated in /var/www/nutsmail/functions/imap_general.php on line 651 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_unregister() is deprecated in /var/www/nutsmail/functions/global.php on line 209 Deprecated: Function session_unregister() is deprecated in /var/www/nutsmail/functions/global.php on line 209 Strict Standards: Non-static method DB::connect() should not be called statically, assuming $this from incompatible context in /var/www/nutsmail/functions/db_prefs.php on line 131 Strict Standards: Non-static method DB::parseDSN() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 520 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 551 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB.php on line 557 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /var/www/nutsmail/functions/db_prefs.php on line 133 Strict Standards: Non-static method DB::isManip() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB/common.php on line 2195 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /usr/share/php/DB/common.php on line 1217 Strict Standards: Non-static method DB::isError() should not be called statically, assuming $this from incompatible context in /var/www/nutsmail/functions/db_prefs.php on line 283 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Deprecated: Function session_register() is deprecated in /var/www/nutsmail/functions/global.php on line 191 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/php/DB/common.php:1217) in /var/www/nutsmail/src/redirect.php on line 164 Can anyone help me? |
From: Tomas K. <to...@us...> - 2011-06-13 19:23:00
|
Dougan, Linda A wrote: > > SquirrelMail version: > > 1.4.7 > > Config file version: > > 1.4.0 > > Config file last modified: > > 10 June 2009 15:40:00 > > > Checking PHP configuration... > PHP version 5.3.6-pl0-gentoo OK. > PHP extensions OK. > Checking paths... > > > After upgrading php I getting this error. > > Warning: Invalid argument supplied for foreach() in > /var/www/nutsmail/functions/attachment_common.php on line 44. > ... > Can anyone help me? > Your error code shows that you use SquirrelMail with custom modifications unsupported by SquirrelMail developers. Reported version does not indicate upgrade. You have old SquirrelMail code version running on new PHP. Technically SquirrelMail is not your webmail vendor. Contact people who created that mod and ask for updates. If you want to get help here, you must publish modifications made in that package. You can't do that for 1.4.7 as they mix proprietary images with GPLed code and only newer packages separate themes from GPL code. -- Tomas -- View this message in context: http://old.nabble.com/squirrelmail-users%40lists.sourceforge.net-tp31837031p31837151.html Sent from the squirrelmail-users mailing list archive at Nabble.com. |
From: Dougan, L. A <DOU...@gr...> - 2011-06-14 14:03:39
|
Well, do you think that you could just help me to understand the code a little? The arrow below points to where I am getting the error "Warning: Invalid argument supplied for foreach() in > var/www/nutsmail/functions/attachment_common.php on line 44." I tried using sm_print_r($attachment_common_types,debug_backtrace()) to trace back where the variable is passed but. I am just confused. I have included what I get from the trace as well. What is sqgetGlobalVar('attachment_common_types', $attachment_common_types) doing? Is it looking for the session variable and setting it or is it setting $attachment_common_types= 'attachment_common_types'? <?php /** * attachment_common.php * * This file provides the handling of often-used attachment types. * * @copyright © 1999-2006 The SquirrelMail Project Team * @license http://opensource.org/licenses/gpl-license.php GNU Public License * @version $Id: attachment_common.php,v 1.25.2.9 2006/04/14 22:27:07 jervfors Exp $ * @package squirrelmail */ /** * FIXME Needs phpDocumentator style documentation */ require_once(SM_PATH . 'functions/global.php'); global $attachment_common_show_images_list; $attachment_common_show_images_list = array(); global $FileExtensionToMimeType, $attachment_common_types; $FileExtensionToMimeType = array('bmp' => 'image/x-bitmap', 'gif' => 'image/gif', 'htm' => 'text/html', 'html' => 'text/html', 'jpg' => 'image/jpeg', 'jpeg' => 'image/jpeg', 'php' => 'text/plain', 'png' => 'image/png', 'rtf' => 'text/richtext', 'txt' => 'text/plain', 'patch'=> 'text/plain', 'vcf' => 'text/x-vcard'); /* Register browser-supported image types */ sqgetGlobalVar('attachment_common_types', $attachment_common_types); if (isset($attachment_common_types)) { // var is used to detect activation of jpeg image types unset($jpeg_done); /* Don't run this before being logged in. That may happen when plugins include mime.php */ sm_print_r($attachment_common_types,debug_backtrace()); foreach ($attachment_common_types as $val => $v) { <------------------------------------------------- if ($val == 'image/gif') register_attachment_common('image/gif', 'link_image'); elseif (($val == 'image/jpeg' || $val == 'image/pjpeg') and (!isset($jpeg_done))) { $jpeg_done = 1; register_attachment_common('image/jpeg', 'link_image'); register_attachment_common('image/pjpeg', 'link_image'); } elseif ($val == 'image/png') register_attachment_common('image/png', 'link_image'); elseif ($val == 'image/x-xbitmap') register_attachment_common('image/x-xbitmap', 'link_image'); elseif ($val == '*/*' || $val == 'image/*') { /** * browser (Firefox) declared that anything is acceptable. sm_print_r($attachment_common_types,debug_backtrace())-OUTPUT attachment_common_types Array ( [0] => Array ( [file] => /var/www/nutsmail/functions/mime.php [line] => 17 [function] => require_once ) [1] => Array ( [file] => /var/www/nutsmail/functions/imap_search.php [line] => 22 [args] => Array ( [0] => /var/www/nutsmail/functions/mime.php ) [function] => require_once ) [2] => Array ( [file] => /var/www/nutsmail/functions/imap.php [line] => 20 [args] => Array ( [0] => /var/www/nutsmail/functions/imap_search.php ) [function] => require_once ) [3] => Array ( [file] => /var/www/nutsmail/src/webmail.php [line] => 27 [args] => Array ( [0] => /var/www/nutsmail/functions/imap.php ) [function] => require_once ) ) -----Original Message----- From: Tomas Kuliavas [mailto:to...@us...] Sent: Monday, June 13, 2011 3:23 PM To: squ...@li... Subject: Re: [SM-USERS] squ...@li... Dougan, Linda A wrote: > > SquirrelMail version: > > 1.4.7 > > Config file version: > > 1.4.0 > > Config file last modified: > > 10 June 2009 15:40:00 > > > Checking PHP configuration... > PHP version 5.3.6-pl0-gentoo OK. > PHP extensions OK. > Checking paths... > > > After upgrading php I getting this error. > > Warning: Invalid argument supplied for foreach() in > /var/www/nutsmail/functions/attachment_common.php on line 44. > ... > Can anyone help me? > Your error code shows that you use SquirrelMail with custom modifications unsupported by SquirrelMail developers. Reported version does not indicate upgrade. You have old SquirrelMail code version running on new PHP. Technically SquirrelMail is not your webmail vendor. Contact people who created that mod and ask for updates. If you want to get help here, you must publish modifications made in that package. You can't do that for 1.4.7 as they mix proprietary images with GPLed code and only newer packages separate themes from GPL code. -- Tomas -- View this message in context: http://old.nabble.com/squirrelmail-users%40lists.sourceforge.net-tp31837031p31837151.html Sent from the squirrelmail-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squ...@li... List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users |
From: Tomas K. <to...@us...> - 2011-06-14 15:40:19
|
Dougan, Linda A wrote: > > Well, do you think that you could just help me to understand the code a > little? > I had to pay nutsmail for my own code in order to prove that they are breaking code license. When you bought that package, it worked and you never cared that their ToS violate original code license. Prove that you have same problem in standard latest SquirrelMail version. do var_dump($attachment_common_types) instead of sm_print_r. sm_print_r prints values and you need to know what kind of variable you are passing to foreach. sqgetGlobalVar('attachment_common_types', $attachment_common_types) is extracting 'attachment_common_types' key value from $_POST, $_GET and $_SESSION. You can find exact order in function. -- View this message in context: http://old.nabble.com/squirrelmail-users%40lists.sourceforge.net-tp31837031p31843971.html Sent from the squirrelmail-users mailing list archive at Nabble.com. |
From: Dougan, L. A <DOU...@gr...> - 2011-06-14 18:39:25
|
When I do sqgetGlobalVar('attachment_common_types', $attachment_common_types); var_dump($attachment_common_types), I get string(23)"attachment_common_types" Does that just mean that it could not find the variable? I would think that it would say something other than attachment_common_types. Linda Dougan Gainesville Regional Utilities 352-334-3400 ext 6936 -----Original Message----- From: Tomas Kuliavas [mailto:to...@us...] Sent: Tuesday, June 14, 2011 11:40 AM To: squ...@li... Subject: Re: [SM-USERS] squ...@li... Dougan, Linda A wrote: > > Well, do you think that you could just help me to understand the code a > little? > I had to pay nutsmail for my own code in order to prove that they are breaking code license. When you bought that package, it worked and you never cared that their ToS violate original code license. Prove that you have same problem in standard latest SquirrelMail version. do var_dump($attachment_common_types) instead of sm_print_r. sm_print_r prints values and you need to know what kind of variable you are passing to foreach. sqgetGlobalVar('attachment_common_types', $attachment_common_types) is extracting 'attachment_common_types' key value from $_POST, $_GET and $_SESSION. You can find exact order in function. -- View this message in context: http://old.nabble.com/squirrelmail-users%40lists.sourceforge.net-tp31837031p31843971.html Sent from the squirrelmail-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squ...@li... List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users |
From: Tomas K. <to...@us...> - 2011-06-14 19:29:31
|
2011.06.14 21:39 Dougan, Linda A rašė: > When I do sqgetGlobalVar('attachment_common_types', > $attachment_common_types); > var_dump($attachment_common_types), I get > string(23)"attachment_common_types" > > Does that just mean that it could not find the variable? I would think > that it would say something other than attachment_common_types. $attachment_common_types is an array and it depends on your browser declared capabilities. extract of key from $_SESSION is below. [attachment_common_types] => Array( [text/html] => 1 [application/xhtml+xml] => 1 [application/xml] => 1 [*/*] => 1) If I remember correctly, code in question has some fixes implemented after 1.4.8. SquirrelMail also has code changes that deal with other notices in your first email. You are using outdated SquirrelMail version written before PHP 5.3 was released. If you came up with these errors on original SquirrelMail code, people would ask you to upgrade your SquirrelMail version. All SquirrelMail versions are free. There is no point for using old version with known issues, when people give you new version with fixes for your problem. I am not a magician. I can't read your webmail code and can't see all modifications done by you and other people. I can't magically convert your modded SquirrelMail 1.4.7 to SquirrelMail 1.4.21. Instead of correcting errors in your modified version of SquirrelMail 1.4.7, get original SquirrelMail 1.4.7 version from SourceForge project site, compare it with code that you bought (diff -uwrN), realize what you are paying for and port it to SquirrelMail 1.4.21. It takes less than one hour to realize that they only replaced looks of some pages, put own credits on code written by others, bundled some plugins and fubared plugin hooks by using them backwards. Don't ask SquirrelMail or other people to support outdated code that you got from third party. You got what you paid for. The more you push, the more rude I will get. You never cared about feeling of SquirrelMail developers when you used code stolen from them. Now your system upgrade made that code unusable and it is up to you to decide whether you pay for it again or you start thinking about other people. -- Tomas |
From: Dougan, L. A <DOU...@gr...> - 2011-06-14 19:34:06
|
Wow, sorry to upset you, I just work here. I did not buy or set up any of this. I was just given the task of trying to figure this stuff out. Sorry that I bothered you. -----Original Message----- From: Tomas Kuliavas [mailto:to...@us...] Sent: Tuesday, June 14, 2011 3:29 PM To: squ...@li... Subject: Re: [SM-USERS] squ...@li... 2011.06.14 21:39 Dougan, Linda A rašė: > When I do sqgetGlobalVar('attachment_common_types', > $attachment_common_types); > var_dump($attachment_common_types), I get > string(23)"attachment_common_types" > > Does that just mean that it could not find the variable? I would think > that it would say something other than attachment_common_types. $attachment_common_types is an array and it depends on your browser declared capabilities. extract of key from $_SESSION is below. [attachment_common_types] => Array( [text/html] => 1 [application/xhtml+xml] => 1 [application/xml] => 1 [*/*] => 1) If I remember correctly, code in question has some fixes implemented after 1.4.8. SquirrelMail also has code changes that deal with other notices in your first email. You are using outdated SquirrelMail version written before PHP 5.3 was released. If you came up with these errors on original SquirrelMail code, people would ask you to upgrade your SquirrelMail version. All SquirrelMail versions are free. There is no point for using old version with known issues, when people give you new version with fixes for your problem. I am not a magician. I can't read your webmail code and can't see all modifications done by you and other people. I can't magically convert your modded SquirrelMail 1.4.7 to SquirrelMail 1.4.21. Instead of correcting errors in your modified version of SquirrelMail 1.4.7, get original SquirrelMail 1.4.7 version from SourceForge project site, compare it with code that you bought (diff -uwrN), realize what you are paying for and port it to SquirrelMail 1.4.21. It takes less than one hour to realize that they only replaced looks of some pages, put own credits on code written by others, bundled some plugins and fubared plugin hooks by using them backwards. Don't ask SquirrelMail or other people to support outdated code that you got from third party. You got what you paid for. The more you push, the more rude I will get. You never cared about feeling of SquirrelMail developers when you used code stolen from them. Now your system upgrade made that code unusable and it is up to you to decide whether you pay for it again or you start thinking about other people. -- Tomas ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squ...@li... List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users |
From: Paul L. <pa...@sq...> - 2011-06-18 07:29:41
|
Linda, On Tue, Jun 14, 2011 at 12:33 PM, Dougan, Linda A <DOU...@gr...> wrote: > Wow, sorry to upset you, I just work here. I did not buy or set up any of this. I > was just given the task of trying to figure this stuff out. Sorry that I bothered you. Your best solution is to download the newest version of SquirrelMail free from our downloads page. You have a VERY old version of NutsMail (which is NOT SquirrelMail and has made dubious copyright claims on software we have created and given away for free), and we do NOT support that software. The newest version of SquirrelMail should work in your environment. If you insist on sticking with paid software, you should contact whomever you paid to get support for it, or you could hire someone from the SquirrelMail team to help you fix your system. Good luck, Paul -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php > -----Original Message----- > From: Tomas Kuliavas [mailto:to...@us...] > Sent: Tuesday, June 14, 2011 3:29 PM > To: squ...@li... > Subject: Re: [SM-USERS] squ...@li... > > 2011.06.14 21:39 Dougan, Linda A rašė: >> When I do sqgetGlobalVar('attachment_common_types', >> $attachment_common_types); >> var_dump($attachment_common_types), I get >> string(23)"attachment_common_types" >> >> Does that just mean that it could not find the variable? I would think >> that it would say something other than attachment_common_types. > > $attachment_common_types is an array and it depends on your browser > declared capabilities. > > extract of key from $_SESSION is below. > > [attachment_common_types] => Array( > [text/html] => 1 > [application/xhtml+xml] => 1 > [application/xml] => 1 > [*/*] => 1) > > If I remember correctly, code in question has some fixes implemented after > 1.4.8. SquirrelMail also has code changes that deal with other notices in > your first email. You are using outdated SquirrelMail version written > before PHP 5.3 was released. If you came up with these errors on original > SquirrelMail code, people would ask you to upgrade your SquirrelMail > version. All SquirrelMail versions are free. There is no point for using > old version with known issues, when people give you new version with fixes > for your problem. > > I am not a magician. I can't read your webmail code and can't see all > modifications done by you and other people. I can't magically convert your > modded SquirrelMail 1.4.7 to SquirrelMail 1.4.21. > > Instead of correcting errors in your modified version of SquirrelMail > 1.4.7, get original SquirrelMail 1.4.7 version from SourceForge project > site, compare it with code that you bought (diff -uwrN), realize what you > are paying for and port it to SquirrelMail 1.4.21. It takes less than one > hour to realize that they only replaced looks of some pages, put own > credits on code written by others, bundled some plugins and fubared plugin > hooks by using them backwards. > > Don't ask SquirrelMail or other people to support outdated code that you > got from third party. You got what you paid for. The more you push, the > more rude I will get. You never cared about feeling of SquirrelMail > developers when you used code stolen from them. Now your system upgrade > made that code unusable and it is up to you to decide whether you pay for > it again or you start thinking about other people. > > -- > Tomas |
From: Rodrigo <rod...@gm...> - 2013-07-06 11:46:04
|
My problem is: without access to the inbox folder ERROR: ERROR: Could not complete request. Query: SELECT "INBOX" Reason Given: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-07-06 08:22:50] My Log is: http://pastebin.com/bGVtjY53 Please help-me! |