Free Support Forum - aspose.com

Could not create MapiMessage: Invalid URI: Invalid port specified

We had a new exception when a calendar’s organizer address is invalid.
For example, when the calendar’s organizer address is: FirstName, LastName invalid:nomail
It will throw exception like:

{code}
Caused by: class com.aspose.email.system.exceptions.UriFormatException: Invalid URI: Invalid port specified.
com.aspose.email.internal.b.av.a(Unknown Source)
com.aspose.email.internal.b.av.a(Unknown Source)
com.aspose.email.internal.b.av.(Unknown Source)
com.aspose.email.afn.a(SourceFile:82)
com.aspose.email.afn.(SourceFile:44)
com.aspose.email.ail$ae.a(SourceFile:737)
com.aspose.email.ail.a(SourceFile:1958)
com.aspose.email.eh.a(SourceFile:177)
com.aspose.email.ec.a(SourceFile:249)
com.aspose.email.MapiMessage.a(SourceFile:3832)
com.aspose.email.MapiMessage.a(SourceFile:3252)
com.aspose.email.MapiMessage.b(SourceFile:3373)
com.aspose.email.MapiMessage.a(SourceFile:2836)
com.aspose.email.MapiMessage.b(SourceFile:2408)
com.aspose.email.MapiMessage.fromMailMessage(SourceFile:1438)
{code}

Also, we created many calendar related bug tickets. when are you going to fix them?
There are just too many bugs with the calendar parser and it’s completely a mess.

Hi Curtis,


Thank you for posting your inquiry.

Can you please share your sample calendar file with us for this new issue? We need it to reproduce the issue at our end and forward it to our Product team for further investigation and fixing. Also, please share the issue ids of the logged tickets for your already reported problems so that we can provide you an update about these.

We regret any inconvenience caused to you in this regard.

The problem entry is:
ORGANIZER;CN=“test, test”:MAILTO:invalid:nomail

Please check attached email

Hi Curtis,


Thank you for sharing the sample EML files.

We were able to reproduce the problem at our end and have logged it as EMAILNET-38451 in our issue tracking system for further investigation. We’ll update you here once there is some update or information available in this regard.

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


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