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:
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:
to 'Don't Use' (as oppo
