You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In OutlookMessage, in the method setProperty, all the following properties are considered to identify the sender email address, leading to setFromEmail:
I think that 0x3ffa property has to be excluded from this check, as the sender is not the same person as the creator/modifier of the msg file.
On top of this, even if the message contains all the above 3 properties, if one of them includes a value in X500 data, it will not be taken into consideration, as setFromEmail forces the value set to always contain "@".
The text was updated successfully, but these errors were encountered:
sanastasiadis
added a commit
to sanastasiadis/outlook-message-parser
that referenced
this issue
Apr 18, 2024
1. the property 0x3ffa refers to the creator/last modifier of the message object and it may be unrelated to the sender of the message.
2. the setFromEmail must allow X500 data if the variable is null (and removed unnecessary/duplicated check for "@")
We have a regex somewhere that detects x500 address and since very recently we have a separate field for x500 address in Recipient (see #73 and #75). Perhaps we should have that check here as well, so we don't overwrite an email address if it is present.
In OutlookMessage, in the method setProperty, all the following properties are considered to identify the sender email address, leading to setFromEmail:
(According to: fileformat.info, exchange server protocol)
I think that 0x3ffa property has to be excluded from this check, as the sender is not the same person as the creator/modifier of the msg file.
On top of this, even if the message contains all the above 3 properties, if one of them includes a value in X500 data, it will not be taken into consideration, as setFromEmail forces the value set to always contain "@".
The text was updated successfully, but these errors were encountered: