Exceptions after using EML 2 MSG conversions and builder.BuildResponse

Hello,


We have the Aspose Total license.

Here is my code:
------------------
using System;
using Aspose.Email.Outlook;
using Aspose.Email.Mail;
using Aspose.Email;
using System.IO;

namespace ConsoleApplication4
{
class Program
{
static void Main(string[] args)
{
Aspose.Email.License emailLicense = new Aspose.Email.License();
emailLicense.SetLicense(“Aspose.Total.lic”);
bug1();
//bug2();
}
private static void bug1()
{
MapiMessage msg = MapiMessage.FromFile(@“c:\temp\imgTest4.msg”);
ForwardMessageBuilder builder = new ForwardMessageBuilder();
builder.AdditionMode = OriginalMessageAdditionMode.Textpart;
//Exception message: The name of attachment can’t be null or empty.
builder.BuildResponse(msg);
}
private static void bug2()
{
MemoryStream ms = new MemoryStream();
MailMessage mailMessage = new MailMessage();
LinkedResource res = new LinkedResource(@“c:\temp\bug.png”);
res.ContentId = Guid.NewGuid().ToString();
mailMessage.LinkedResources.Add(res);
mailMessage.Save(ms, SaveOptions.DefaultMsg);
MapiMessage streamMsg = MapiMessage.FromStream(ms);
ForwardMessageBuilder builder = new ForwardMessageBuilder();
builder.AdditionMode = OriginalMessageAdditionMode.Textpart;
//Exception message: String reference not set to an instance of a String.
builder.BuildResponse(streamMsg);
}
}
}


You can find attached the files used by the code.

I’ve marked with comment lines the places where the two exceptions are raised with their warning messages after calling builder.BuildResponse.

Please take a look and let me know what could be the problem.

Regards
Lyubo

Hi Lyubomir,

Thank you for writing to Aspose Support team.

We have investigated both these issues at our end and were able to reproduce the same with the latest version of Aspose.Email for .NET 6.6.0. These have been logged as EMAILNET-38397 and EMAILNET-38398 in our issue tracking system for further investigation by our Product team We’ll update you here once there is some information available in this regard.

The issues you have found earlier (filed as EMAILNET-38397;EMAILNET-38398) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.