Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > Or you could set SquirrelMail $config_location_base to https site address. Setting this variable with my rewrite rules does the job. If I use the RedirectPermanent option for apache the browser claims for non-authenticated contents in the page. Jimmi -- View this messag

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > Or you could set SquirrelMail $config_location_base to https site address. The first and the second together. The RedirectPermanent method only gives me errors after deleting messages while reading, and this $config_location_base only allows my daughter to login on non en

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Gotcha! Are the rewrite rules I use to redirect from port 80 to 443: ServerName MYSITE RewriteEngine on RewriteCond %{SERVER_PORT} ^80$ RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [L,R] RewriteLog "/var/log/rewrite.log" RewriteLogLevel 2 If I eliminate them the problem stops. U

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > > Then try sending reply. Browser should stop and output "Location: some > url" text. Check if mailbox name is encoded there twice. Then restore > original compose.php. > It shows: Location: MYSITE/src/right_main.php?mailbox=Mail%2FMYBOX&sort=0&startMessage=1 Tomas Ku

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > > Could you test your PHP settings > (http://www.squirrelmail.org/wiki/TestPHPSettings). Show all settings in > core, session and mbstring sections. > Find the file with the settings here attached. Hope this helps you for giving me some debugging option. Tomas Kuliavas

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > > You can't get such URL in replies. Such order of arguments is possible > only when you click on "Message List" link or when you resume message > writing from draft and send or save it. Mailbox name is encoded twice. > Script that might redirect you to > right_main.php?s

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > > Which script says it? Is it displayed in src/compose.php, > src/right_main.php or some other script. > Sorry, the frame is 'src/right_main.php' and the error is a response to the following address: https://MYSITE/src/right_main.php?sort=0&startMessage=1&mailbox=Mail%

Re: [SM-USERS] Slash wrongly encoded as %2F in returning path

Tomas Kuliavas wrote: > > Used SquirrelMail and PHP versions? > Squirrelmail 1.4.9a-2 and PHP 4.4.4-8, both from Debian Etch repository Tomas Kuliavas wrote: > > Which script says it? Is it displayed in src/compose.php, > src/right_main.php or some other script. > The address bar shows 's

[SM-USERS] Slash wrongly encoded as %2F in returning path

Hi, it happens anytime I write a reply from inside a folder. After sending the mail, when I should be back in the message list of MYBOX, I receive the error: ERROR: Could not complete request. Domanda: SELECT "Mail%2FMYBOX" Reason Given: SELECT failed: Can't open mailbox Mail%2FMYBOX: no such ma

[SM-USERS] Cannot login through imapproxy

Hi, on my home server, running with Debian Etch, I have uw-imapd serving my mail boxes through squirrelmail using an SSL connection. I wanted to follow the recommendation of squirrelmail documentation, therefore I installed imapproxy from Debian repositories and set it to use the port 143 to conn