Re: [Phpgroupware-developers] Re: [Phpgroupware-users] Email Application Issues

[Daryl L. L. Houston]

Actually, they're popping in all cases.  The problem seems to transcend the 4 
minute cache.  For example, he reported the problem on Saturday.  When I came 
in on Monday and logged into gw as him, he still had the old inbox listing, 
but the messages, when clicked, pointed to new mail on the server.  It may be 
the case that I didn't let it sit for four minutes to refresh after logging 
in (and that he hadn't done so either, reporting the issue as soon as he 
noticed it and then moving on to the next thing), but even if that's the 
case, I think it's a bug that the cache doesn't refresh upon login. My kluge 
solves the problem, though whoever actually maintains the app can probably 
point to all sorts of reasons my fix is insufficient and inelegant.

D


On Monday 07 July 2003 07:52 pm, Chris Weiss wrote:
> so they are using phpgw via IMAP (? you didn't say), then logoff, then POP
> the account, then log in again all within 4 minutes time?  /me shudders
>
> Caching while using another client at the same time is known to cause this,
> but doing so past that 4 minute cache period should be fine.  This
> behaviour is improved in Anglemail with some even smarter caching.   The
> core of the problem is that POP3 is not well suited for web based email,
> and IMAP doesn't provide good functions for simultainious access.  Basicaly
> the flags set for "something has changed" simply aren't there.
>
> On a related note, I have also found that using POP3 and IMAP on the same
> account with any client at any time can cause much madness on many servers.
>
> Daryl L. L. Houston (address@hidden) wrote:
> >I figured out that this was a problem with caching and checking mail using
> >another mail client.  That is, if you check mail with groupware, your
> > inbox is cached in the database. If you then use another client to POP
> > mail and remove it from the server, the next time you check mail using
> > groupware, the cached inbox is displayed, but the links to view
> > individual messages point to messages that may or may not actually exist
> > on the server anymore. So if you have three messages in your gw cache,
> > but you pop mail through another client, the next time you check mail
> > through gw, your inbox will display the three messages, but clicking the
> > links will give you an error because the messages don't actually exist.
> > Or if you've received, say, two messages since you POPped your account
> > through another client, clicking the first two messages in gw will
> > display messages; but they're the two new messages rather than the ones
> > corresponding to the cached inbox.  There's no check to see whether or
> > not the message ID listed in the inbox matches the message ID as listed
> > on the server, and the result is the problem described below.  The fix
> > I've applied is to write a function that deletes all rows from the cache
> > for the given user upon login. This forces the cache to be rebuilt when
> > the mail application is loaded, so that any deletions not performed from
> > within gw are accounted for.  I've submitted a bug report (#4224 if
> > you're interested) and a description of the fix to savannah, though there
> > are probably more elegant ways of handling it.
> >
> >D
> >
> >On Monday 07 July 2003 10:20 am, Daryl L. L. Houston wrote:
> >> I have 9.14.506 installed and am having some bizarre issues with the
> >> email application.  The inboxes of some users are messed up.  For
> >> example, a message comes in whose subject line does not correspond to
> >> the body of the message.  It's as if the headers are being separated
> >> from the message bodies and aren't being reassembled correctly when the
> >> inbox is built.  The problem doesn't seem to run across all accounts,
> >> however.  Mine is fine.  I sent myself email both from within the
> >> groupware email app and from my thick client and from both inside and
> >> outside my network for good measure. All of my messages came in fine. 
> >> At one point (to solve a different problem, actually), I deleted the
> >> rows in phpgw_anglemail that cached the inbox of one of my users.  Even
> >> after that clean-up, he encountered this weird issue.  I just
> >> redownloaded the 9.16 branch of this app (it's what was in place before)
> >> to see if something's changed since I last grabbed it. The problem began
> >> only after I upgraded a month or so ago from 9.14.002 to the .16 branch.
> >> Thanks for any ideas or experiences you may have to share.
> >>
> >> D
> >>
> >> --------------------------------
> >> Daryl L. L. Houston
> >> Web Applications Developer
> >> Signage Solutions, LLC
> >> 865.342.8270
> >>
> >>
> >> _______________________________________________
> >> Phpgroupware-users mailing list
> >> address@hidden
> >> http://mail.gnu.org/mailman/listinfo/phpgroupware-users
> >
> >--
> >--------------------------------
> >Daryl L. L. Houston
> >Web Applications Developer
> >Signage Solutions, LLC
> >865.342.8270
> >
> >
> >_______________________________________________
> >Phpgroupware-developers mailing list
> >address@hidden
> >http://mail.gnu.org/mailman/listinfo/phpgroupware-developers
>
> _______________________________________________
> Phpgroupware-developers mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/phpgroupware-developers

-- 
--------------------------------
Daryl L. L. Houston
Web Applications Developer
Signage Solutions, LLC
865.342.8270