On Tue, Oct 20, 2009 at 12:22 PM, David C. Rankin
<drankinatty@xxxxxxxxxxxxxxxxxx> wrote:
> On Monday 12 October 2009 11:56:33 am Tomas Kuliavas wrote:
>
> Thomas,
>
> I just found this thread. After yesterdays updates to 1.5.2 svn (Rev
> 13866), I have the exact same problem, but unfortunately, plugins are not my
> problem. I have used squirrel mail for years, and aside from a few issues in
> the past, I haven't had any problems. I don't know what's going on here. I can
> log into the imap server (dovecot) with kmail and thunderbird or from the
> command line. The server this the same openSuSE 10.3 box I have been running
> for a couple of years. The apache2 logs look fine and my other web apps work
> (eGroupWare and Gallery2), so I know it isn't a php or apache2 config issue.
> So I'm kind of baffled.
>
> Below is what I have done from following this thread and your discussion with
> the OP. I have tried to include all of the information you asked for. If I
> need to provide anything else, just let me know and I'm happy to do it. I put
> my answers inline below for context. (I just pray that it is real sqmail
> problem and not some utter stupidity on my part -- it's has happened....
>
> Thanks in advance for any help or advise you can give.
>
>> Chris Riley wrote:
>> > Thanks for getting back to me so quickly.
>> >
>> > On Mon, Oct 12, 2009 at 11:11 AM, Tomas Kuliavas <
>> >
>> > tokul@xxxxxxxxxxxxxxxxxxxxx> wrote:
>> >> > Base URL detected as: https://<HOSTNAME>.com/squirrelmail/src
>> >> > (location base autodetected)
>> >>
>> >> 1. Is base URL detected correctly? It must match URL displayed in
>> >> browser's address bar.
>
> YES, both http and https
>
> 2. Create test script with
> ---
> <?php
> session_write_close();
> ini_set('error_reporting',E_ALL);
> ini_set('display_errors',1);
> var_dump(session_start());
>
> Done, response:
>
> bool(true)
> No write errors for both http: and https:
>
>>
>> Find out why login is redirected to http:// URL. SquirrelMail login form
>> sends data to src/redirect.php, redirect.php sets authentication cookies
>> and redirects users to src/webmail.php, webmail.php creates frameset with
>> left_main.php and right_main.php frames. All scripts use same base URL
>> detection functions and https://.../src/redirect.php should not redirect
>> to http://.../src/webmail.php unless some plugin breaks redirection
>> process. Turn off all plugins.
>>
>
> DONE.... Squirrelspell and Calendar are the only plugins I had enabled.
> Removing them makes no difference. No users can log in and attempts to login
> immediately return you to the page that says:
>
> ERROR
> You must be logged in to access this page.
> Go to the login page
>
> It's like it's stuck in a loop?
It's been reported that 1.5.2 does this when using PHP 5.3. I have no
idea what versions the OP was using, but this is likely your problem.
I haven't had the time to test this, but you should first make sure
you are getting the right cookies set in the browser (please show
them). Also, please indicate what session storage mechanism you are
using.
You can try, for example, commenting out the session_regenerate_id()
call on line 87 of src/redirect.php, but I have no idea if that's got
anything to do with the problem.
>> Make sure that SquirrelMail scripts are not modified and you don't have any
>> custom links/images/css in webmail interface. Invalid image or css link
>> might redirect users to login page, which destroys session.
>>
>
> HMM... I do have a link back to my home page, but it should be correct. I
> simply set the Signout Page under Organization Preferences:
>
> 5. Signout Page : 3111return.html
>
> The page is a simple redirect that has worked for the past couple of years:
>
> <html>
> <head>
> <title>3111Skyline, Nacogdoches, Texas -- Freedom For All</title>
> <meta http-equiv="REFRESH" content="0;url=http://nirvana.3111skyline.com";>
> </head>
> <body>
> </body>
> </html>
>
>
> I removed it and tested with: $signout_page = ''; Unfortunately, no help. I
> have tried both FireFox 3.5 and Opera 10 -- same results. Running
> /src/configtest.php was fine. The only warning was the php short tags warning
> which is normal. The complete test ouput is here:
>
> http://www.3111skyline.com/download/bugs/sqmail-configtest-OK.txt
>
> The access log shows the following for each login attempt with opera shows:
>
> 192.168.6.102 - - [20/Oct/2009:14:09:50 -0500] "POST
> /squirrelmail/src/redirect.php HTTP/1.1" 302 -
> 192.168.6.102 - - [20/Oct/2009:14:09:50 -0500] "GET
> /squirrelmail/src/webmail.php HTTP/1.1" 200 1924
>
> Attempts with firefox show:
>
> 192.168.6.102 - - [20/Oct/2009:14:12:14 -0500] "POST
> /squirrelmail/src/redirect.php HTTP/1.1" 302 -
> 192.168.6.102 - - [20/Oct/2009:14:12:14 -0500] "GET
> /squirrelmail/src/webmail.php HTTP/1.1" 200 1924
> 192.168.6.102 - - [20/Oct/2009:14:12:15 -0500] "GET
> /squirrelmail/src/style.php? HTTP/1.1" 200 159
>
> The error log does not produce a warning on the login attempt or redirect,
> but I did find the following warning that were produced by configtest.php:
>
> [Tue Oct 20 13:38:42 2009] [error] [client 192.168.6.102] PHP Warning:
> date(): It is not safe to rely on the system's timezone settings. You are
> *required* to use the date.timezone setting or the date_default_timezone_set()
> function. In case you used any of those methods and you are still getting this
> warning, you most likely misspelled the timezone identifier. We selected
> 'America/Chicago' for 'CDT/-5.0/DST' instead in
> /srv/www/htdocs/squirrelmail/src/configtest.php on line 190
> [Tue Oct 20 13:38:42 2009] [error] [client 192.168.6.102] PHP Warning:
> date(): It is not safe to rely on the system's timezone settings. You are
> *required* to use the date.timezone setting or the date_default_timezone_set()
> function. In case you used any of those methods and you are still getting this
> warning, you most likely misspelled the timezone identifier. We selected
> 'America/Chicago' for 'CDT/-5.0/DST' instead in
> /srv/www/htdocs/squirrelmail/src/configtest.php on line 896
>
> Neither look bad as sqmail selected the correct timezone. So I'm stumped and
> need some advise from the smart people on squirrelmail. What in the heck is
> going on?? What to check/test next. I'm happy to do the grunt work. Thanks.
--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
