Return-Path: <squirrelmail-users-admin@lists.sourceforge.net>
Received: from muffin ([unix socket])
	by muffin (Cyrus v2.1.12) with LMTP; Sat, 19 Apr 2003 11:56:39 -0400
X-Sieve: CMU Sieve 2.2
Return-Path: <squirrelmail-users-admin@lists.sourceforge.net>
Received: from sc8-sf-list2.sourceforge.net (lists.sourceforge.net [66.35.250.206])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by muffin.linuxnotes.net (Postfix) with ESMTP id CAA58240CD
	for <quincy@linuxnotes.net>; Sat, 19 Apr 2003 11:56:38 -0400 (EDT)
Received: from sc8-sf-list1-b.sourceforge.net ([10.3.1.13] helo=sc8-sf-list1.sourceforge.net)
	by sc8-sf-list2.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
	id 196uGL-0002ZT-00; Sat, 19 Apr 2003 08:28:21 -0700
Received: from certiflexdimension.com ([66.137.233.209] helo=vampire.certiflexdimension.com)
	by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian))
	id 196uFe-00026s-00
	for <squirrelmail-users@lists.sourceforge.net>; Sat, 19 Apr 2003 08:27:38 -0700
Received: from VALCOR (netdork.net [66.228.134.123])
	by vampire.certiflexdimension.com (8.11.2/8.11.2) with ESMTP id h3JFOji10441;
	Sat, 19 Apr 2003 10:24:45 -0500
From: Jonathan Angliss <jon@squirrelmail.org>
X-Mailer: The Bat! (v1.63 Beta/7) Personal
X-Priority: 3 (Normal)
Message-ID: <177916556.20030419103017@certiflexdimension.com>
To: Terry Allen <hmag@ozemail.com.au>
Cc: squirrelmail-users@lists.sourceforge.net
Subject: Re: [SM-USERS] Update to latest squirrelmail Requirements
In-Reply-To: <p05200f04bac6cab8f6ed@[203\.53\.37\.182]>
References: <p05200f04bac6cab8f6ed@[203.53.37.182]>
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
X-MailScanner: Found to be clean
Sender: squirrelmail-users-admin@lists.sourceforge.net
Errors-To: squirrelmail-users-admin@lists.sourceforge.net
X-BeenThere: squirrelmail-users@lists.sourceforge.net
X-Mailman-Version: 2.0.9-sf.net
Precedence: bulk
List-Help: <mailto:squirrelmail-users-request@lists.sourceforge.net?subject=help>
List-Post: <mailto:squirrelmail-users@lists.sourceforge.net>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/squirrelmail-users>,
	<mailto:squirrelmail-users-request@lists.sourceforge.net?subject=subscribe>
List-Id: Squirrelmail User Support Mailing List <squirrelmail-users.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/squirrelmail-users>,
	<mailto:squirrelmail-users-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=squirrelmail-users>
X-Original-Date: Sat, 19 Apr 2003 10:30:17 -0500
Date: Sat, 19 Apr 2003 10:30:17 -0500

Hello Terry,
On Saturday, April 19, 2003, Terry Allen wrote...

> I posted a similar message to this a couple of weeks back, so I
> thought I'd post again, as I have received no replies.

> In any case, I am currently running Squirrelmail 1.2.11 on OSX
> 10.1.5 - I am about to update to a new server package (iTools 7) & a
> new OSX version (10.2.5) & one thing I don't want to break is
> Squirrelmail.

> I noticed in the requirements for Squirrelmail 1.4.0 that it's not a
> good idea to use PHP 4.3.x & also, Apache 2.0.x - both things which
> iTools uses.

> Can anyone outline the issues that Squirrelmail may have with Apache
> 2.0.x & PHP 4.3.1? Are these breakable issues? If so, is there any
> idea as to when they might be resolved - any assistance is really
> appreciated as I need to do this soon - many thanks.

Reading the lists over the last few months would give you an outline
of why we still suggest against using it. PHP developers "fixed" an
apparent "bug" in their session handling. In doing so, most of
squirrelmail then apparently becomes 'buggy' because of this change in
behaviour. They also fail to mention the changes they have made in the
session handling, and their instructions are not very well put. For
example, they say that you SHOULD use the vars $_SESSION or
$HTTP_SESSION_VARS to save data to the session, but in some version
doing that doesn't work (oooh... thanks... I think you may have
reminded me about PHP 4.1 and lower).

As for Apache 2.0.x, I don't see any problem any more, as they/PHP
fixed the path related issue where scripts wouldn't be able to use
relative paths to open/read other files.

-- 
Jonathan Angliss
(jon@squirrelmail.org)



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
--
squirrelmail-users mailing list
List Address: squirrelmail-users@lists.sourceforge.net
List Archives:  http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users

