Hi,
We need to know which encoding of email body is. But property BodyEncoding returns null when we using POP3 protocol or IMAP4 and UTF8Encoding when we use EWS. Return value of this property doesn’t dependence on email, I see that it dependence on only protocol.
I’ve tested on 18.3 and 18.6.
I’ve attached sample for reproduce the problem.
Regards,
Irina
AETest.zip (4.4 KB)
The behaviour seems specific to protocol. An investigation ticket with id: EMAILNET-39032 has been logged to further look into it. We’ll update you here as some information or a fix version is available in this regard.
Hi Kashif,
Thanks for quick response. I’ve attached sample for POP3 protocol, but issue is reproducible for all protocols.
It’s critical issue for our customers. We are looking forward to receive updates from you as soon as possible.
Regards,
Irina
We have recorded your concerns against the logged issue and will update you here once there is some information available in this regard.
Hi Kashif,
Our customer has raised the severity of the issue. Could you please escalate it?
Regards,
Irina
If you want to move the issue to priority support for which you have subscription, please open a ticket on Paid Support forum with this ticket id.
Hi Kashif,
Yes, I want to move the issue to priority support. But I cannot create issue on Paid Support. I see the following message: Your subscription has been expired, kindly renew your subscription.
Could you please help me?
Regards,
Irina
We have prepared hotfix for this issue. Please download it from attachment here.EMAILNET_39032.zip (2.6 MB)
[quote=“cap.aspose, post:9, topic:179018”]
Hi Kashif,
Any plan to include this hot-fix into official (patch) release?
Regards,
Irina.
It will be part of the upcoming release of Aspose.Email for .NET 18.7 which will be available for download in a week time. We’ll update you here once the fix version is available for download.
Hello Kashif!
I’ve tried Hotfix with IMAP4 protocol and plain text and html formatted messages, but I do not see any difference between 18.6 version and this Hotfix version.
Property BodyEncoding is still null for both PlainText and HTML mail messages.
Seems like Hotfix doesn’t fix the issue.
We expect to get actual mail bode encoding there for all email protocols supported, but not null value.
Thanks!
Regards,
Olga.
We have tested the hotfix version at our end and it works well. Please verify that you are referencing the hotfix dll properly at your end. If the issue still persists, please share a test account credentials with us having few emails that we can use to reproduce the problem at our end for assisting you further.
Hello Kashif!
Sorry, it’s my fault: wrong DLL was copied and linked.
Fix works, please include it in your new release.
Thanks!
Regards,
Olga.
Thank you for sharing your feedback. We are glad your issue is resolved. Please feel free to write to us if you have any further query related to API.
Hello Kashif,
Do you have more specific ETA for the upcoming release of Aspose.Email for .NET 18.7?
Thanks.
The fix version will be available early next week. We’ll notify you here as soon as it is available for download.
The issues you have found earlier (filed as EMAILNET-39032) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by kashif.iqbal
Hi Kashif,
I’ve downloaded Aspose Email .NET 18.7 and I’ve done some tests. The fix seems to work fine for POP3 and IMAP4 protocols. But property BodyEncoding still returns always UTF8Encoding for EWS protocol. So, the fix is incomplete.
Could you please fix BodyEncoding for EWS protocol also?
Regards,
Irina