Aspose Adding Additional Quotes In Mail Message Appointment Alternate View - Cannot Then Convert To Mapi Message

Aspose.Email Product Family
1

I have a calendar invite. I am trying to convert it first to MailMessage and then to MapiMessage. During mail message creation, Aspose is adding additional quotes in the appointment alternate view before every quote in the calendar invite attendees. As a result of this, the conversion to mapi message is failing. Could you please advise.

My calendar invite is as below -

BEGIN:VCALENDAR
PRODID:-//Events Calendar//iCal4j 1.0//EN
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20210708T024937Z
DTSTART:20210809T173000
DTEND:20210809T180000
SUMMARY:Progress Meeting
TZID:America/Mexico_City
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TU,FR;COUNT=3
LOCATION:Meeting Room 16
UID:0b852e32-a6d1-4b77-b45b-f9f4aa4e03fc
ATTENDEE;ROLE=REQ-PARTICIPANT;CN=Developer 1;DELEGATED-TO=“mailto:dev1@mycompany.com”;RSVP=TRUE:mailto:test@test.com
ATTENDEE;ROLE=OPT-PARTICIPANT;CN=Developer 2:mailto:dev2@mycompany.com
ATTENDEE;CN=Developer 4:mailto:dev4@mycompany.com
ORGANIZER;CN=Developer 3:MAILTO:dev3@mycompany.com
END:VEVENT
END:VCALENDAR

During conversion to MapiMessage, the exception that I get is

com.aspose.email.system.exceptions.UriFormatException: Invalid URI: The format of the URI could not be determined: ""mailto

2

Hello @gs01,

Thank you for writing to our forum.

Could you please provide a code sample for investigation?

Thank you.

3

Hi

The code sample is as below -

...
MailMessage mailMessage = new MailMessage();
...
Appointment appointment = Appointment.load(
				new ByteArrayInputStream(appointmentBytes),
				APPOINTMENT_LOAD_OPTIONS);
alternateView = appointment.requestApointment();
mailMessage.getAlternateViews().addItem(alternateView);
...
MapiMessage mapiMessage = MapiMessage.fromMailMessage(mailMessage, MAPI_CONVERSION_OPTIONS);
4

@gs01
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): EMAILJAVA-35202

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

1 Like
5

Thank you @sergey.vivsiuk .
Could you provide a rough timeline so that I can track this?
I am also assuming that the fix will go in a new release with a version upgrade. Is that correct?

Any piece of information will be very beneficial.

Note: We (Global Relay) are paid customers and pay for Aspose word and email.

6

Hello @vsingh52,

The new version 23.8 will be released by the end of next week, before Sep 7

7

That’s fantastic! Thank you so much @sergey.vivsiuk.
Once we have the new version, we will do the needful at our side to verify the fix.

9

@sergey.vivsiuk Will it be possible to add this fix to version 21.2.1 as that is the version we are currently on and if we upgrade it will create lot of testing work for us ?

10

@vsingh52,

We have prepared the hotfix release 21.2.0.1

11

@sergey.vivsiuk That is a great news. Could you make that fix available in the maven repo Aspose Repository Browser /java/repo/com/aspose/aspose-email/ ?

Thank you

12

@vsingh52,

Sorry, but this fix is not intended to be published in a public maven repo.

13

Hi @dmitry.samodurov,
Could you explain the reason for that?

Regards
Varun

14

Hello @vsingh52,

We decided to add this fix to maven. Sorry for the confusion.

15

Thanks so much @dmitry.samodurov

16

Could you please confirm that the hotfix release (21.2.0.1) is based on our version (21.2.1)? From the numbering, it seems that the hotfix might be on an earlier version to ours? When testing the hotfix, we found that the LinkedResource class is missing the getContentDisposition method. If the hotfix is not based on version 21.2.1, then could you please provide us with a hotfix for version 21.2.1. Thanks.

17

Hello @gs01,

Your issue is taken for investigation. We’ll contact you as soon as we have results.

Thanks for reporting your case.

18

Hello @gs01,

This is my fault and the hotfix release 21.2.0.1 was based on version 21.2
We have published to maven hotfix 21.2.1.1 for version 21.2.1
We’re sorry to keep you wait. Thanks for your patience.