EWS Managed API: Email sender name incorrect if loading properties of multiple emails and several emails have same email address (but different names) RRS feed

  • Question

  • Hi,

    I have an issue using the Exchange Web Services Managed API. I'm essentially implementing an 'inbox', and am essentially using two calls:

    folder.FindItems(filter, view) with the view set up with the 'idonly' property.

    The returns a 'FindItemResults<>' object containing a set of items.

    And then calling service.LoadPropertiesForItems(items, props), where the props contains all 'first class properties', which includes the sender details.

    Now, the inbox contains several emails from the same email address but with different displaynames.

    E.g. There may be one email from "Bob <dummy@dummy.com>" and another email from "Alice <dummy@dummy.com>" and another email from "Charlie <dummy@dummy.com>" etc.

    The issue is that in the information that EWS returns from the call to LoadPropertiesForItems, every email ends up with the same sender name (from the first one in the list)!

    i.e. When I enumerate through the returned items, the item.Sender.Name will always be"Bob" for every email where Sender.Address is dummy@dummy.com. 

    I have debugged this with a http sniffer just to ensure that it really is the EWS coming back with this information rather than anything in the managed layer.

    Is this a known issue? How can I work around this (without querying every single email for the sender name individually, as that would be too slow)?


    Wednesday, November 12, 2014 9:46 AM

All replies

  • Hi RJP1973,

    This is a known issue with EWS and we have a bug open for this.  However, since the name displayed is one of the names associated with the email address, this bug is prioritized low and it will be a while before it is fixed.  What is the scenario requiring a different display name while keeping the same email address?  Understanding your scenario would help us prioritize the bug better.



    Wednesday, November 12, 2014 3:10 PM
  • Hi Venkat,

    Thanks for the reply.

    The scenario is that the client receives emails from a (3rd-party) automated system. The email address from this automated system is always "noreply@<blah.com>", while the display name is used to differentiate the actual sender.

    I suspect that this kind of system will likely become more widely used, and so for us will increase in priority (obviously its a priority for our client already)!

    Just for the record, if this is a known issue do you have a bug number or equivalent for it? (I tried to search but couldn't locate it).

    Thursday, November 13, 2014 9:11 AM