I seem to be having problems since the start of this week with messages in EWS not being picked up.
If the message has a CC, it is able to be picked up, otherwise it seems to be ignored.
Here is example code and output, we are on version 5.1.0
Dim credential As New System.Net.NetworkCredential(“user”, “pass”, “domain”)
Dim client As IEWSClient = EWSClient.GetEWSClient(“https://outlook.office365.com/EWS/Exchange.asmx”, credential)
Dim msgCollection As ExchangeMessageInfoCollection = client.ListMessages(client.MailboxInfo.InboxUri)
Console.Write(msgCollection.Count)
Dim count As Integer = 0
For Each foldinfo As ExchangeFolderInfo In client.ListSubFolders(client.MailboxInfo.RootUri)
Console.WriteLine(foldinfo.DisplayName & " " & foldinfo.TotalCount & " " & foldinfo.UnreadCount)
Next
Inbox count: 0
Calendar 8661 0
Clutter 1 0
Contacts 0 0
Conversation Action Settings 0 0
Deleted Items 5095 0
Drafts 0 0
Inbox 3 0
Journal 0 0
Junk Email 0 0
Notes 0 0
Outbox 0 0
Quick Step Settings 0 0
RSS Feeds 0 0
Sent Items 9270 0
Sync Issues 0 0
Tasks 0 0
Test 49 0
After using ListMessages, it seems that 0 items are returned from the inbox. But iterating through the folders show there are items in the Inbox.
Is it anything to do with the new Clutter feature than Microsoft have recently introduced in email?
Thanks.
Hi Narayanan,
We were able to reproduce the issue here and found that the issue occurs with messages that only have To field populated. If an email message has CC field value as well, it doesn’t raise any exception, provided there is no other message of earlier type in mailbox. We have reported this problem to our Product team by reporting it in our bug tracking system as EMAILNET-34971and shall share the feedback or fix version information once available.
PS: This issue arises only with Office365 and we were not able to reproduce it with Exchange 2010 at our end.
Same issue here all of the sudden. It has been working for years
without any changes to the code or version of Aspose on our end.
Microsoft recently introduced Clutter on their outlook.office365.com
product. Could that be a factor?
Also, Monday I was able to copy
all the unprocessed emails from one account to another in the same
domain and they were picked up by Aspose. Today that account also
stopped working.
Hope this info helps. We are in dire need of a speedy recovery.
Thanks!
Pete
Hi Pete,
We are not sure if the clutter feature could be the reason for this broken functionality, but this is definitely something at Office365 end. We tested this functionality during last week and it was working. We are in touch with our Product team about getting this resolved as soon as possible and shall share the feedback with you as it is available.
The issues you have found earlier (filed as EMAILNET-34971) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by Aspose Notifier.