> I just tried telnet 110 - Conn. refused.
> and changed my Thunderbird to 143 for his account - error.
If you can't get 110 or 143, I believe you can configure Entourage for
the Mac to use an OWA address as a server. I'm 99% sure I did it with
my 2004 Entourage on my previous Mac laptop.
Per
On 9/7/2010 12:27 PM, chuck wrote:
>I have a new client and I'm building him a web page and pointing his
> domain name to my server - that's done and life is 98% good. To this
> point he has only had email, MS Outlook Webaccess. All of his past
> emails, address book etc. are on that server
Jerry,
Some quick hints:
Security Issue:
A) stay more up to date on squirrelmail packages. That package has
known exploits.
B) use randomly generated passwords. For example, this site came up
from a quick Google search: http://www.thebitmill.com/tools/password.html
Auth Warning:
C) To al
> It's up to you to show what is different in those situations.
>
>
Out of interest, did you happen to upgrade php from 5.2.11 to 5.2.12? I
found a time bug with my system that might be larger than originally
thought.
See http://bugs.php.net/bug.php?id=50930
Regards,
KAM
---
> See above - the bug is the lack of correct environmental setup
Thanks for the quick response. Glad to know I was on the right track.
Regards,
KAM
--
The Planet: dedicated and managed hosting, cloud storage, colocatio
> Egads. It looks like that ancient version of gcc and PHP 5.2.12
> breaking dates is something we probably don't want to add workaround
> code for, since it looks like a pretty borked bug to me. I guess it's
> our use of gmdate() when setting cookie expiry (you could look at your
> cookie data
Second, the newuser_wiz plugin doesn't work with newer compatibility
versions. I *know* it is old but theoretically it should work.
I'm not sure what your theory is, but old broken code has to be fixed
before it will work. ;-)
However, it doesn't seems to work because this line in
ffect cookies
(http://bugs.php.net/bug.php?id=50930) This points to the issue with 1.5.19
being caused by a change in PHP 5.2.12 from 5.2.11.
We saw this problem manifest with phpmyadmin. AND we appear to have 1.4.19
working now.
We are currently trying a few different things to replicate / prove
> Finally, I tried to install SM 1.4.19 and 1.4.20RC2. We definitely
> saw the exact "you must be logged in to view this page" errors that
> others have complained about. From reviewing my
> webserver cookies, I appeared to have cookies for / and for /src with
> 1.4.19+
>
> Reverting to 1.4.1
