“Exception in myassociationready.com(Aspose.Email Evaluation)”
orginal Delivery date & time : 3/17/2022 9:47 AM
Received date : 3/17/2022 4:17(UTC)
offset value : +530
Received date to univeraltime : 3/17/2022 9:47 AM
Example 2:
“RE: Update of RR2(Aspose.Email Evaluation)”
orginal Delivery date & time : 7/19/2022 3:26 AM
Received date : 7/19/2022 12:55:00 AM
offset value : +000
Received date to univeraltime : 7/19/2022 7:25:00 AM
Note : example 1 sender and receiver will be same country.
example 2 sender and receiver will be different country
In your code, you are using MapiMessage.FromStream method. This method is obsolete now. Please use MapiMessage.Load instead.
We have investigated this issue with your shared files and noticed that the delivery date and time is correct according to files.
Could you please share how are you checking original delivery date and time at your end? Please also share the screenshots of delivery date and time of EML and MSG files.
However, we have logged an investigation ticket as EMAILNET-40652 in our issue tracking system for your case. We will inform you via this forum thread once there is an update available on it.
The MapiMessage.DeliveryTime property is used to get or set the date and time a message was delivered. You can use this property to get the delivery time of EML or MSG file.
It is to inform you that we have closed the issue EMAILNET-40652 as ‘Not a Bug’.
Different delivery times are not Aspose.Email bug, but expected behavior. The MSG format is a set of Mapi properties where DateTime is always stored in UTC format. But Outlook and Aspose.Email shows DateTime properties in the local time zone of the current computer.