Closed mynpmpackage closed 2 years ago
Thanks, messageFlags will be exposed since 1.14.1-alpha.1
Thank you for exposing. I will check with 1.14.1-alpha.1 and confirm back.
As usual I am having local server cache issue and it will take few more hours to get the cache updated with 1.14.1-alpha.1 .
For now, I tried with node cli parse command with the emails in draft box and seeing different values and not 8, Do you know why?
Below are the steps I tried.
sometimes sent email copied to system folder and executing node cli parse not gives 1
Same when I tried draft email which is created and saved by me gives value as 8
messageFlags are bit fields.
To extract mfUnsent flag, try Bitwise AND operator. Bitwise AND (&) - JavaScript | MDN
Okay thanks. Does it mean, we have to check parsed messageFlags values with Bitwise AND operator to derive for draft(unsent)? And if 8 then we have consider as draft email?
Although with some coding msgreader can include sent field, imo it'd be cool if we can handle bit flag processing on local code.
// boolean
const sent = (messageFlags & 8) == 0;
const unsent = (messageFlags & 8) != 0;
Okay, thanks. I will put in local code.
Verified with alpha it works, could you please release the version 1.14.1.
Ok 1.14.1
is now ready
Thank You. I am going to use 1.14.1.
Thanks for the quick fix.
Like MailItem.Sent([https://docs.microsoft.com/en-us/office/vba/api/outlook.mailitem.sent]) ,
Could you please help me knowing which msgreader fieldsdata() parsed property represents Sent?. Sometimes this property Sent help me to decide the email is draft when Sent flag is set to false.
Is it possible to add Sent property to https://hiraokahypertools.github.io/msgreader/typedoc/interfaces/MsgReader.FieldsData.html?
Will the PidTagMessageFlags will help us when mfUnsent is not set?