MailMessage.ReversePath Parse Error

Aspose.Email Product Family
1

Hello,
As the docs says nothing:

Wanted to confirm if is this the same as Return-path?
If so, after I load this attached email into MailMessage, MailMessage.ReversePath Is Nothing returned, while it exists inside the email headers.
Parse error?

eml.zip (8.2 KB)

2

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): EMAILNET-40943

You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.

1 Like
3

Hello,
One more issue related to this Return-path is that when loading msg it returns <> as Return-path
If it does not exists, an empty string should be returned, no server will return <>
Is this normal? Because will not happen for all messages!
Sample:
WindowsApplication1.zip (247.8 KB)

4

@australian.dev.nerds,

I have added additional info to the ticket. Thanks.

5

Hi @australian.dev.nerds

this issue has been fixed, the fix will be available in the next release at the end of February

This is not an Aspose.Email bug. If you inspect the original msg file with a third party application (such as OutlookSpy or MFCMAPI), you will see that the PR_TRANSPORT_MESSAGE_HEADERS property contains a Return-Path header with a value of <>. See attached screenshot.screen2.jpg (604.9 KB)