I'm sitting here stracing things and I didn't check the basics. The fix is
always the simplest solution. If a FAQ is ever distributed with it that
needs to be added!
Thanks,
Dave
-----Original Message-----
From: cour...@lists.sourceforge.net
[mailto:cour...@lists.sourceforge.net] On Behalf Of Sam
Varshavchik
Sent: Thursday, May 12, 2005 11:30 AM
To: cour...@lists.sourceforge.net
Subject: [sqwebmail] Re: Session always expired
David Cundiff writes:
I'm using sqwebmail 5.0.1 with vpopmail 5.4.10 with the /var/vpopmail dir
mounted over NFS. The UID/GID of the vpopmail user/group is the same on
both
systems. This is a new installation. Whenever I login I get the "your
session has expired" message. The interaction between the sqwebmail
processes and the vpopmail api seems to be fine. Stracing the sqwebmail
process I see the auth go thru, then the proper mail dir being accessed.
One
strange thing is towards the end of the strace I see a 503 moved message
sent to the browser. That's when I get the session has expired message on
the login page and that's as far as I can get. Any suggestions??
The system clocks on your NFS client and server must be synchronized.
1 message in net.sourceforge.lists.courier-sqwebmailRE: [sqwebmail] Re: Session always ex...
