On Tue, July 31, 2012 12:15 am, michael crane wrote:
> I just use this stuff on my tiny home network and I don't know why I
> enabled the https stuff on my server but now with the squirrelmail.stable
> installation after a few minutes of composing I get
> "The current page request appears to have
On Tue, May 26, 2009 at 10:45 PM, Machtelt Garrels wrote:
> On Tue, May 26, 2009 at 12:12:44PM -0700, Paul Lesniewski wrote:
>> Then this is entirely unrelated to SquirrelMail. You should create a
>> test document on your server with just "Hello
>> World" and work out your Apache configuration un
On Tue, May 26, 2009 at 12:12:44PM -0700, Paul Lesniewski wrote:
> Then this is entirely unrelated to SquirrelMail. You should create a
> test document on your server with just "Hello
> World" and work out your Apache configuration until you
> can access it with https. After that, SquirrelMail sh
> Since the dawn of times I've been using Squirrelmail. Until I was
> forced to upgrade to Apache2, all went well. Since, I've googled myself
> dizzy to get HTTPS working again, but no result.
>
> I'll first give some more information about my system:
>
> OS: Debian 5.0.1
> Squirrelmail: squirrel
On 1/11/08, Zeta <[EMAIL PROTECTED]> wrote:
>
> hi there, i have a problem with squirrelmail redirecting to http after
> login instead of https.
> the scenario is:
>
> squirrelmail on linux machine on port 443 and IIS on port 80 both
> listening on same ip address.
Uh, that's "interesting"...
> s
Don Russell schrieb:
> [EMAIL PROTECTED] TU Darmstadt wrote:
>> Hello squirrelmail-community,
>>
>> I've installed & configured squirrelmail on debian linux (etch/testing)
>> with apache2 and so far it works fine! :-)
>> What I want to do now, is to secure the login process.
>> The manual tells abo
Don Russell wrote:
> [EMAIL PROTECTED] TU Darmstadt wrote:
>
>> Hello squirrelmail-community,
>>
>> I've installed & configured squirrelmail on debian linux (etch/testing)
>> with apache2 and so far it works fine! :-)
>> What I want to do now, is to secure the login process.
>> The manual tells
Don Russell wrote:
> [EMAIL PROTECTED] TU Darmstadt wrote:
>
>> Hello squirrelmail-community,
>>
>> I've installed & configured squirrelmail on debian linux (etch/testing)
>> with apache2 and so far it works fine! :-)
>> What I want to do now, is to secure the login process.
>> The manual tells
[EMAIL PROTECTED] TU Darmstadt wrote:
> Hello squirrelmail-community,
>
> I've installed & configured squirrelmail on debian linux (etch/testing)
> with apache2 and so far it works fine! :-)
> What I want to do now, is to secure the login process.
> The manual tells about the "RedirectPermanent" op
> On Mon, Oct 02, 2006 at 02:16:51PM +0200, [EMAIL PROTECTED] TU Darmstadt
> wrote:
>
>> The problem is, that configuring apache with "RedirectPermant" for
>> squirrelmail-login obviously cause a loop and the browser hangs. Why?
>
> Without having the relevant parts of your webserver's config, it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] TU Darmstadt wrote:
> What I want to do now, is to secure the login process.
> I'd like to avoid using mod_rewrite.
Have you considered the 'secure login' plugin? It works REALLY well for me.
Chris Hilts
[EMAIL PROTECTED]
-BE
On Mon, Oct 02, 2006 at 02:16:51PM +0200, [EMAIL PROTECTED] TU Darmstadt wrote:
> The problem is, that configuring apache with "RedirectPermant" for
> squirrelmail-login obviously cause a loop and the browser hangs. Why?
Without having the relevant parts of your webserver's config, it is hard
to
> Hello squirrelmail-community,
>
> I've installed & configured squirrelmail on debian linux (etch/testing)
> with apache2 and so far it works fine! :-)
> What I want to do now, is to secure the login process.
> The manual tells about the "RedirectPermanent" option that I already use
> for mailman
Dan Carl said the following on 08/29/05 10:20:
> Here's my situation.
> Internally I have two Linux servers, a commerce webserver and a mailserver
> running webmail.
> Externally I have only one public IP address.
> I want to use ssl on both servers.
> I fully understand the limitations of the HTT
Marc,
> I presume you're using apache 2.x (I'm still at 1.3.33). What
> version of php are you running? I guess it's time to see what
> came out in the most recent Redhat update and see what's changed.
>
Apache 2.0.46, PHP 4.3.2. Both installed via up2date on the 27th of July.
However I'm prett
> -Original Message-
> From: adam beecher [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 09, 2005 2:21 PM
> To: Marc Powell; squirrelmail-users@lists.sourceforge.net
> Subject: RE: [SM-USERS] HTTPS auto-discovery causing page not founf
errors
>
> Hi Mark,
>
&
Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Marc Powell
> Sent: 09 August 2005 19:41
> To: squirrelmail-users@lists.sourceforge.net
> Subject: RE: [SM-USERS] HTTPS auto-discovery causing page not
> founf errors
>
&
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:squirrelmail-
> [EMAIL PROTECTED] On Behalf Of adam beecher
> Sent: Tuesday, August 09, 2005 11:37 AM
> To: squirrelmail-users@lists.sourceforge.net
> Subject: [SM-USERS] HTTPS auto-discovery causing page not founf errors
>
> (Latest
Hello Cameron,
On Monday, March 07, 2005, Cameron Knowlton wrote...
> I meant... why does 1.50 show up dominantly as the development
> version, no 1.5.1? I wonder how many others get caught by that.
1.5.0 was the last released development version. 1.5.1 has not been
released, which is why it is
> > ?? it says 1.50 is current on the download page...
>>
>> http://www.squirrelmail.org/download.php
>>
>> what am I missing?
>
>It says that it is "Development Version". It is not stable and currently
>released development version is older than 1.4.4.
>
>--
>Tomas
>
I meant... why does 1.50 show
> ?? it says 1.50 is current on the download page...
>
> http://www.squirrelmail.org/download.php
>
> what am I missing?
It says that it is "Development Version". It is not stable and currently
released development version is older than 1.4.4.
--
Tomas
I'm running:
OS X version 10.3.6
PHP version 5.0.2
SquirrelMail version 1.5.0
>>>
>>>
>>>1.5.0 is badly out of date by now, and I think it is missing some key PHP 5
>>>compatibility fixes. If you want to use the development version of SM, you
>>>should always use a CVS snaps
I'm running:
OS X version 10.3.6
PHP version 5.0.2
SquirrelMail version 1.5.0
1.5.0 is badly out of date by now, and I think it is missing some key
PHP 5 compatibility fixes. If you want to use the development version
of SM, you should always use a CVS snapshot (download on the web site
in tar
Title: Re: [SM-USERS] HTTPS over port 80 / Cannot
re-assign $this
Cameron Knowlton wrote:
I just had an epiphany that solved at
least the HTTPS access over port 80 problem on Mac OS X, although it
did then drop another problem on me 8^)
To solve the inadvertent IMAP secure access:
1) in Server
Cameron Knowlton wrote:
I just had an epiphany that solved at least the HTTPS access over port 80
problem on Mac OS X, although it did then drop another problem on me 8^)
To solve the inadvertent IMAP secure access:
1) in Server Admin, change Mail/Settings/Advanced Settings/IMAP and POP SSL:
On 2004-07-05 17:50, Frank Bonnet wrote:
> Hi
>
> Is it possible with squirrelmail to use HTTPS only during the
> authentication session then use HTTP for normal email operations ?
>
> Thanks
>
Hello,
There's a plugin that does exactly that at the SquirrelMail website
(Secure Login). Check it out.
> SquirrelMail 1.2.9 does not support IMAPS directly - you need to use a
> wrapper like stunnel. If you are determined to make
> SquirrelMail connect
> directly to port 993, you'll need to upgrade to 1.4.0-rc2a
> and PHP 4.3.x
> (which has other issues, and I don't recommend doing)
This is good
>> I'm running (well almost) Squirrelmail 1.2.9 with Apache 1.2.7, php4.2,
>> OpenSSL 0.9.6g and imap-uw-2002 on FreeBSD 4.7-Stable. I installed
>> everything seems to be working fine - I changed squirrelmail to point to
>> port 993 for imaps and I can connect to port 993 via telnet. I can
Squirr
> Are you connecting to an Imap server running on the same box?
> If so, I think it only works if you use the regular Imap port.
> You don't really need 993 for the https login anyway.
>
> Dennis.
Thanks for the quick reply :)
That would make sense, from the point of view of what's happening. I
Richard Cooper said:
> Hi,
> I'm running (well almost) Squirrelmail 1.2.9 with Apache 1.2.7, php4.2,
> OpenSSL 0.9.6g and imap-uw-2002 on FreeBSD 4.7-Stable. I installed
> everything from the ports tree (Apache, PHP and OpenSSL were already
> isntalled and I was already running a secure website). I
30 matches
Mail list logo
