23.11 new MessageValidator.Validate

Aspose.Email Product Family
1

Hello,

The new validator does not have MessageValidationError.LineNumber like the old one?
Mentioning the problematic line number is useful for debugging.
Anyway not a big issue…

The thing is that if Tnef will be supported too? What’s your idea about it? :slight_smile:

2

Hello,
There are some incorrect results by the new MessageValidator.Validate

  1. mhtml:
    MsgConvert.zip (20.2 KB)
    Error description: “From” header contains invalid address “SavedbyBlink”: ‘@’ character is missing.

Well, save some simple pages using IE/Edge, to see SavedbyBlink.

  1. emlx:
    EMLX.zip (279.5 KB)
    All of my emlx files are failed validation, even if use Aspose to save something as emlx.
    Actually, Aspose itself is not saving emlx files in the fully standard format, the trailing emlx data is not generated.
    Error description: Given stream has incorrect format.
3

Thanks, we’ll check it out and get back to you.

1 Like
4

@australian.dev.nerds
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): EMAILNET-41299

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

Hello and thanks so much for logging the issue, just asking about the Tnef inclusion, what’s your comment, useful? :slight_smile:

6

Hi @australian.dev.nerds

We do not plan to support TNEF validation due to the complexity of implementation and unknown demand for this feature

For MSG format this does not make sense, for EML format it will be added in the near future.

In our opinion, this is not a bug but a feature. We validate the message in accordance with rfc standards and in this case the error description is correct.

This bug will be fixed in logged issue.

1 Like
7

Yep, Msg and Oft are binary, but Eml, Mht and Emlx can have line number, very useful info, actually the source code exists in the old validator class!

Just please note that this happens for mht / mhtml files saved by Microsoft browsers, and not for Eml.

Thanks so much for your kind attention, if you’re going to mark emlx emails without trailing data as invalid, remember that Aspose Email itself does not generate that ending part when saving as Emlx (a feature I hope some day gets implemented, to be able to make fully valid emlx files).

8

Thanks for your thoughts.

1 Like
9

Thanks for the fix, great :slight_smile:

10

Thank you too.