Zitat von lst_ho...@kwsoft.de:
Zitat von Jochen Roderburg <roderb...@uni-koeln.de>:
When I have a running webmail session with activated Horde cache
and another mail program is changing something on the mail server,
the changes are not reflected on the webmail side.
At least for IMAP folders this is documented:
[cache_folders]
If set to true, note that any folders created on the server during
an IMP session that are NOT created via IMP will not be displayed
until the next login. If IMP will be the exclusive means of
accessing the mail server, or you are not concerned about this
behavior, this setting should be set to true.
Yes, I have seen and understood this particular case and have decided
that I am "not concerned about this behavior".
But for message status, delete, new etc. it's working fine here with
Cyrus as IMAP server and parallel access with Thunderbird (IMAP)
and IMP/Horde. You have to wait for refresh for sure but this is
standard IMAP behavior.
These are the cases that trouble me.
When I read now that this works in your installation and see no
warnings in the configuration dialogs, I think it is really the
correct intended behaviour that changes on the mailserver are shown
and I have a "special" problem here. General experience says then that
in such strange cases the real cause is "something completely
different".
A test scenario here:
"Old" IMP (Horde2/IMP3)
"New" IMP (Horde3/IMP4) with activated Horde cache
Thunderbird 3.1
When I sent a new mail to my account, it is shown in all three
candidates. In Thunderbird immediately, in the IMP's after a (manual
or automatic) refresh of the mailbox list.
I delete the mail now in the Old IMP (IMAP delete) and it is shown
there as deleted. In Thunderbird it is also immediately shown as
deleted. In the New IMP
it is *not* shown as deleted, and I do not find a way to persuade it
to display this correctly. No webmail refreshes help, no Browser
refreshes. I can logout and re-login. I can login on different systems
with different browsers, everywhere it is displayed as not deleted. It
even survives a complete server restart.
The only way I found to get rid of the situation is to deactivate the
Horde cache or clear the cache storage (memcached meanwhile).
Can anybody tell me how this whole thing is supposed to work
internally? How does IMP find out that something has changed on the
IMAP server and its cached version is no longer valid?
Best Regards,
Jochen Roderburg
--
IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscr...@lists.horde.org
