Paul Lesniewski wrote:
>
> That's a very risky bet. All the software in the equation - from the
> browser to the web server to SquirrelMail all typically assume 443 ==
> SSL. It is possible to use non-SSL connections on port 443, but it's
> always going to introduce a higher probability that pro
Paul Lesniewski wrote:
>> I installed the SVN version as you requested.
>> The banner displays as:
>>
>> SquirrelMail version 1.4.17 [SVN]
>
> Looks like the script that generates snapshots stalled out in
> December. Too bad. I'll have to get with the team on that one. So
> for now, you'd
Paul Lesniewski wrote:
> Thanks for the very thorough posting. The behavior you explain is
> typical of a situation where the browser doesn't have the cookie
> needed to re-athenticate when redirecting to webmail.php. You say
> your browser is accepting them, but perhaps there is an issue with t
A recent upgrade to 1.4.14-1.fc9 appears to result
in an issue with login.
After login, I'm immediately redirected to the redirect page.
I get "you must be logged in to access this page".
I believe the actual login is working. If I use an invalid
login/password, then I get the "invalid login pas
