This bug was fixed in the package squirrelmail-secure-login - 1.4-2
---
squirrelmail-secure-login (1.4-2) unstable; urgency=medium
* Changed default configuration (using quilt):
+ $change_back_to_http_after_login = 0 (LP: #321304)
+ $sl_securePort = '443'
* debian/control:
I've noticed the same thing, and in its current state, it's unusable
without being manually changed. After installing it, it took me 2+ days
to figure out what was wrong with it and why I couldn't log in.
--
default configuration of squirrelmail-secure-login doesn't work
https://bugs.launchpad.n
That's odd; my unmodified installation of squirrelmail (I ran the config
script just to set the imap configuration), only worked after
change_back_to_http_after_login was cleared. And checking config.php, I
see $only_secure_cookies is set to true.
Ah-hah: looking at the debian changelog:
squirre
