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 problems like this > will occur. One thing you can do with 1.4.18 (BTW, the snapshots on > our download page are working agopain) is to turn off > $only_secure_cookies (config/conf.pl-->4-->16. Only secure cookies if > poss.) because you indicated that you are NOT using SSL but the > SSL-only flag is turned on. Changing this seeting $only_secure_cookies resolved my issue. This works fine with 1.4.7.fc9 too. I appreciate your assistance. Such awesome support on this list. I will take this opportunity to also go off an learn how to properly support SSL. Something I've been meaning to do for a long time. Thanks, Jim > > ------------------------------------------------------------------------------ > ----- > 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 > ------------------------------------------------------------------------------ ----- 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
