Fix setting end datetime for events that are not all-day.
Fix generating attribute value for attendees that don't have an email address.
The menu_view preference had been removed with the redesign.

Conflicts:
	imp/docs/CHANGES
	imp/lib/Basic/Compose.php
	imp/package.xml
Bug #11518: Fix confirmation of login tasks

Conflicts:
	horde/templates/logintasks/logintasks.html.php
	horde/templates/logintasks/smartmobile.html.php
Bug: 12185 Fix bad cherry-pick.

Horde_ActiveSync_Device is not present in FRAMEWORK_5_0
BFN
Bug: 12171 Set logger on importer.
If error retrieving ACLs for a mailbox from IMAP server, fallback to defaults instead of throwing exception (Bug #12184)

Conflicts:
	imp/lib/Imap/Acl.php
Released Horde_ActiveSync-2.3.5
Development mode for Horde_ActiveSync-2.3.6
Update history instead of appending to it (=bloating)
Store Kolab_Storage_Factory in class (we need it later on)
Compute proper history prefix for Kolab objects

The IDs in the history database are always
formatted like this: "APPNAME:SHARE_ID:OBJECT_UID".

Kolab must compute the same prefix for objects
synced in from foreign clients. Otherwise client code
using the listBy() or getChanges() API (=ActiveSync)
would miss those objects.
Only consider known 'action' values for finding the latest history entry
Re-issue 'add' action for an object if the last action was 'delete'

In the Kolab world, objects can vanish
and re-appear using the same object uid.
(a foreign client is sending an update over a slow link,
 we see the delete first and minutes later the APPEND/add request)
Only issue a 'delete' action if all copies of an object are gone

Otherwise we just deleted a duplicated object or updated the original one.
(An update results in an ADDED + DELETED folder action)
Improve IMAP folder UIDVALIDITY change detection. Fixes #11807.

We stored the whole list of IMAP UIDs of a folder next
to every object. This turned out to be a major memory
and CPU time hog (see #11807).

Instead we detect a change of UIDVALIDITY at the
IMAP folder cache level (where it belongs) and pass
the information about a reset situation to the
history 'query' as additional parameter.
Full sync for the history database: Mark vanished entries as deleted
Update history instead of appending to it
Tie Kolab_Storage to Horde_History if enabled

Otherwise Kolab_Storage_Factory::createHistory()
will use the in-memory only Horde_History_Mock object.