Quantcast
Channel: MFCMAPI
Viewing all 1090 articles
Browse latest View live

Source code checked in, #111648

$
0
0
Problem: Memory leak dumping msg files Fix: Uninitialize named property cache

Source code checked in, #111649

$
0
0
Problem: SmartView: Garbage in conversation index Fix: c_str

Source code checked in, #111650

$
0
0
Problem: Smart View: Memory leak Fix: free buffer

Source code checked in, #111652

$
0
0
Continuing conversion to unicode

New Post: access to impersonated cloud archive when primary mailbox is on-premises in hybrid environment

$
0
0
Hello,

First, you should be using the Plain Old XML (POX) Autodiscover endpoint to gather settings to create an Outlook profile. The SOAP Autodiscover endpoint doesn't contain all the information to configure an Outlook profile properly. My guess is that the target mailbox is using the MAPI over HTTP protocol rather than the RPC over HTTP protocol and that's why the information is not available in the SOAP Autodiscover response. Here is a way you can confirm my guess:
  1. Use Outlook's Test E-Mail Autoconfiguration tool to pull back the POX autodiscover response from the server. An article describing how it can be done can be found here:
https://technet.microsoft.com/en-us/library/ff678502(v=ocs.14).aspx

Resolve Exchange Free / Busy and Communicator Presence Issues
Specifically, the section labeled Step 3: Check Autodiscover and Exchange Web Services

If the target mailbox is indeed using MAPI / HTTP as the protocol you can either disable it on that client or you can use the Autodiscover response to configure the profile to use MAPI / HTTP.

http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx

Source code checked in, #111653

$
0
0
Problem: Memory addresses in debug output make diffs difficult Fix: Remove them

Source code checked in, #111654

$
0
0
Problem: Continue wstring conversion Fix: Convert MyOpenFile

Source code checked in, #111655

$
0
0
Problem: Continue wstring conversion Fix: Convert OutputToFilef

Source code checked in, #111656

$
0
0
Problem: Keep migrating wstring Fix: DebugPrint Part 1

Source code checked in, #111657

$
0
0
Problem: Keep migrating wstring Fix: DebugPrint Part 2

Source code checked in, #111658

$
0
0
Problem: Keep migrating wstring Fix: DebugPrint Part 3

Source code checked in, #111659

$
0
0
Problem: Keep migrating wstring Fix: DebugPrint Part 4 of 4

Source code checked in, #111660

$
0
0
Problem: Continue wstring conversion Fix: DebugPrintEx

Source code checked in, #111661

$
0
0
Problem: More wstring conversion Fix: OutputToFile

Source code checked in, #111662

$
0
0
Problem: Continue conversion Fix: Remove _Output/_OutputA

Source code checked in, #111663

$
0
0
Problem: Continued conversion Fix: Change _OutputW back to Output

Source code checked in, #111664

$
0
0
Problem: Continue conversion Fix: OutputXMLValue

Source code checked in, #111665

$
0
0
Problem: PR_CONTENT_FILTER_SCL should be more prominent Fix: Add it as a default column for messages

Source code checked in, #111666

$
0
0
Problem: Fid export broken Fix: Fix it up to work with new wstring stuff

Source code checked in, #111667

$
0
0
Problem: NameIDToStrings manages strings Fix: Convert to wstring
Viewing all 1090 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>