[Isomorphic]

We've made a change in this area (again) to restore previous behavior in SC/SGWT 12.1 and 13.0, since existing templates may rely on parsing. By default, template content up to the subject line will be parsed looking for "to:" and "from:" lines.

If this causes a problem, as is reported here, you should call setMessageParseMode() to set parsing mode to "None" if you have access to the message instance, or you can set:

mail.message.defaultParseMode: None

in your server properties file to globally disable parsing.


In SC/SGWT 13.1, we've changed the default to "None" (no parsing), so you shouldn't need to do anything there to avoid the issue reported here. Users who are relying on header parsing to populate the "to" and "from" fields of the message in SC/SGWT 13.1+ can add

mail.message.defaultParseMode: Header

to their server properties file to get the old behavior back.

[Isomorphic]

This is fixed and will be available for download in nightly builds since Nov 15 (tomorrow) across all versions since 12.1.

[Isomorphic]

Apologies for the delay, we are looking into this and will follow up soon.

[Blama]

Hi Isomorphic,

could you have a look here? This seems to be happening again for me.

Thank you & Best regards
Blama

[Blama]

Hi Isomorphic,

could you have a look here?

Thank you & Best regards
Blama

[Blama]

Hi Isomorphic,

it seems this is happening again (using v12.1p_2022-08-10). I noticed it today. The big difference is that I updated JavaMail from the mail.jar you provide with javax.mail-1.6.2.jar.
My code and server.properties stayed the same. I just stopped Tomcat, replaced the Jar and restarted.

Does you change perhaps only work with the old mail.jar?
If so, can I somehow force the different parsing also in my 12.1p version?

Best regards
Blama

[Isomorphic]

That's basically a backcompat API for people who may have depended on the previous behavior of parsing headers out of body content.

[Blama]

Hi Isomorphic,

by chance I found the new method TemplatedMailMessage.getMessageParseMode() in 13.1d. MailMessageParseMode itself is already doc'd in 13.0p.

Out of interest: Am I right in thinking that this works similar in previous versions (12.0p, 12.1p), but wasn't configurable?

Best regards
Blama

[Isomorphic]

Similar to what you guessed: content was potentially interpreted as headers due to the use of parse().

[Blama]

Hi Isomorphic,

I retested with v12.0p_2021-08-11 and it's working as expected.

Out of interest: What was the issue here?

Thank you & Best regards
Blama

[Isomorphic]

We have applied a fix for this issue which will be available as of tomorrow's builds (Aug 11).

Please, let us know if you see any other issues on this part.

Regards
Isomorphic Software

[Blama]

Hi Isomorphic,

could you reproduce this one?

Thank you & Best regards
Blama

[Blama]

Hi Isomorphic,

also happening with v12.0p_2021-07-06/PowerEdition Deployment for me:

=== 2021-07-27 12:33:56,600 [main] INFO ISCInit - Isomorphic SmartClient/SmartGWT Framework (v12.0p_2021-07-06/PowerEdition Deployment 2021-07-06) - Initialization Complete

Are you sure you changed the text for elephant?
This is what my screenshot looks like after clicking the button:

Best regards
Blama

[Isomorphic]

We couldn't reproduce the error with the latest build of 12.0p. Please, try with that.

Regards
Isomorphic Software

[Blama]

Isomorphic,

it is just return request.execute().

package com.smartgwt.sample.server.listener;

import javax.servlet.http.HttpServletRequest;

import com.isomorphic.datasource.DSRequest;
import com.isomorphic.datasource.DSResponse;

public class Animals {

    public DSResponse mailFetch(DSRequest request, HttpServletRequest servletRequest) throws Exception {
        return request.execute();
    }
}

Best regards
Blama