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
I'm looking for suggestions on how to proceed with the following:
In processing very old email messages, like from 20 years ago or so, such as from Outlook Express stores, I've found that there were a fair amount of attachments hitting the exception in Attachments.cs, at about lines 332 and 367.
if (isInline && string.IsNullOrWhiteSpace(contentId))
throw new ArgumentNullException(nameof(contentId),
"The content id cannot be empty when isInline is set to true");
To initially resolve this, I forked the repo and removed the exception throws. This allows the msg conversion to complete and actually, the attachments seem fine.
Without interfering with the core functionality, I would like a way to continue with the less stringent attachment checking, for older email messages.
I've been using a forked copy of MsgKit for a such long time, but, in the end, I would really, very much, just prefer using the nuget package instead.
This is (hopefully) the only issue keeping me using the nuget package.
Any suggestions on how to proceed are very much welcome.
The text was updated successfully, but these errors were encountered:
I'm looking for suggestions on how to proceed with the following:
In processing very old email messages, like from 20 years ago or so, such as from Outlook Express stores, I've found that there were a fair amount of attachments hitting the exception in Attachments.cs, at about lines 332 and 367.
To initially resolve this, I forked the repo and removed the exception throws. This allows the msg conversion to complete and actually, the attachments seem fine.
Without interfering with the core functionality, I would like a way to continue with the less stringent attachment checking, for older email messages.
I've been using a forked copy of MsgKit for a such long time, but, in the end, I would really, very much, just prefer using the nuget package instead.
This is (hopefully) the only issue keeping me using the nuget package.
Any suggestions on how to proceed are very much welcome.
The text was updated successfully, but these errors were encountered: