I am using php 4.3.3 with apache 2.0.47. However, I have
to admit that I cannot reproduce this error on a continous
basis therefore I assume that it is the browser's cache
issue. Other than that, I don't know enough about SM's
codes to comment.
Michael.
Chad Morris said:
> That was a good thoug
Hi List,
Two week ago, I have posted an email mentionning a bug with
squirrelmail (v1.4.x) and Internet Explorer (all version of IE).
(cf http://article.gmane.org/gmane.mail.squirrelmail.user/14148 )
This bug is very annoying because I can't upgrade my squirrelmail.
So, I have try to underst
You forgot to CC: the list. Sorry I didn't have the time to respond til now.
>> If you are concerned about bug fixes and the like, why aren't you using
>> the newest version of SM? 1.2.x is quite old by now. Upgrade to 1.4.2
>> and these things are already fixed. If you find bugs there, we are
> Warning: Cannot add header information - headers already sent by (output
> started at /webmail/squirrelmail-1.4.2/plugins/secure_login/config.php:90)
> in /webmail/squirrelmail-1.4.2/src/webmail.php on line 59
Given that line 90 should be the last line in the file, you probably have
an extra car
Using SM 1.4.2 on apache 1.3.26 on RH7.1
I have installed the compatibility plugin and secure_login.
The login page is fine, however when I login, instead of getting my Inbox,
I get:-
Warning: Cannot add header information - headers already sent by (output
started at /webmail/squirrelmail-1.4
Dear SM community,
I'm running SM on an Apache HTTP server but need to be able to access it
through HTTPS over stunnel (bound to loopback), as well. Everything works
without problems as HTTP, including through an ssh tunnel
(unsurprisingly). When trying to access the server as HTTPS
