Fix wrong proposed conf
Fix from Chenglin Zhong: mapistore_message_modify_recipients is improperly invoked
Merge branch 'master' of https://github.com/openchange/openchange
Escape ldap filters with strings properly
Merge pull request #95 from Zentyal/jgarcia/escape-ldb-searches

Encode ldap filters properly
oxcstor/RopLogon: Explicitly check for MAPISTATUS code
oxcstor/RopLogon: Verify EssDN for public logons

With Public Logons, EssDN is always empty (I am testing with OL 2010)
It this case, all underlying layers are failing, because there is
no valid 'username'

Proposed fix is fallback got User DN for logged in user
emsmdbp/mailbox_init: Alwasy popoulate mailbox_object object

Previously, for public folders we just missed to populate very
important fields like: EssDN and username
Merge pull request #96 from openchange/kamenim/fix-public-folders

Fix Logon for Public mailbox store
Merge pull request #89 from sixstone-qq/ejhernandez/fix-proposed-repo-conf

Fix wrong proposed conf
Fix OOF file backend when no SIEVE scripts are there
Merge pull request #97 from sixstone-qq/ejhernandez/fix-oof-file-backend-no-sieve

Fix OOF file backend when no SIEVE scripts are there
Add a script to wipe *every* openchangedb entries for a given user.
Helpful when you want to start over with the same user and have a clean
and fresh mailbox
Merge remote-tracking branch 'openchange/master' into aterron/merge-from-oc-remote
Merge pull request #102 from Zentyal/aterron/merge-from-oc-remote

Aterron/merge from oc remote
Add free/busy permissions

* FreeBusySimple
* FreeBusyDetailed

See [OXCPERM] for details.
Merge pull request #98 from sixstone-qq/ejhernandez/add-freebusy-perms

Add free/busy permissions
oxcmsg: Implementation for partial UserDNs in ModifyRecipients call

When Outlook passes some value in RecipientRow.prefix_size, then
we should restore the full legacyExchangeDN in recipient_x500name
using szDNPrefix we supplied to Outlook during Connect op.

Signed-off-by: Kamen Mazdrashki <kmazdrashki@zentyal.com>
oxcmsg: Resolve x500dn back to sAMAccountName due to SOGo limitations atm

Despite comments, SOGo expects message_recipient->username to be
the sAMAccountName for the recipient.
Thus resolving parital x500dn to a full one brakes the backend.
Utill this is fixed, this patch is a reasonable fix for that limiatation
Merge pull request #99 from openchange/kamenim/modify-recipients-partial-x500dn-impl

RopModifyRecipients partial x500dn implementation