Re: [Phpgroupware-users] emails from other account to be seen

[Chris Weiss]

I don't know where it would happen.  The theory (which I have done no
testing on) would be this:

1) user logs in and reads some email
2) user brings up the login screen (maybe via a bookmark) WITHOUT
clicking logout
3) php sees the user already has a sessions but phpgw think there
isn't one because they ended up at the login page
4) phpgw runs the login for the user and php sees the exsisting
session and overwrites only the values it was asked to
5) some values from the email cache remain and you get your issue.

The tricky part is this:  I think the session is "autocreated" in
phpgw to allow for things like sitemanager to work.

I don't know why you don't have the anglemail table, it should have
been created on the last update, it's been there since phpgw
0.9.14.something.  I highly suggest adding the table by going into
setup and uninstaling and reinstaling the email app (this will not
remove any settings).  Not only should this fix the problem, it will
give you a nice performance boost too.



On Tue, 05 Oct 2004 21:52:22 +0200, Dirk H. Schulz
<address@hidden> wrote:
> Hi Chris,
> 
> I do not have a phpgw_anglemail table in this database.
> 
> --On Dienstag, 5. Oktober 2004 13:29 Uhr -0500 Chris Weiss
> <address@hidden> wrote:
> 
> > do you have a phpgw_anglemail table?  I kind of expected to see one in
> > the logs but didn't.  The ONLY way phpgw can do this is if the
> > phpgw_anglemail exsists, is being used, and something in the query is
> > cauing it to grab rows from other users.  Otherwise it HAS to be the
> > IMAP server.  Mabe the IMAP server is caching some auth itself?
> 
> No, not that I know. It is a courier imap server. I have it running on
> quite a lot machines, and we never had anything like that.
> 
> >
> > However, if the table does not exsist, some caching is done in the
> > session, and if the user doens't explicitily logout (which I'm not
> > sure but it seems they weren't always) then the cache from one session
> > might be able to merge to the next.  If you have the table then this
> > can't happen as it's all grabbed explicitly by the login id.
> 
> Then it must be that. But if the session cache from one session can be
> merged into that of another session that sounds quite horrible. Where does
> this merging happen?
> 
> Thanks for looking into the issue.
> 
> Dirk
> 
> 
> 
> 
> _______________________________________________
> Phpgroupware-users mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/phpgroupware-users
> 
>