I think I've solved this issue with another message resulting in similar crashes when forwarding or replying to HTML messages with inserting the HTML into the respective TER window. Since Pegasus Mail provides any HTML it processes to the active HTML renderer for correcting issues which might crash TER I found out supported by Martin Ireland what he was doing differently with BearHtml. After modifying my processing accordingly I don't see these crashes anymore. Expect to see an IER update (providing filxes for other issues as well) soon.

Please insert this Email to your folder:  http://78.108.103.11/~fojtik/pmail/PT7CV4JK.CNM

And try to open HTML section. Pegasus mail completely crashes :(.

 I attempt to catch callstack. Pegasus mail stores some files from Dr Watson, I can upload them if neccessary.

I have libtidy 1.0.6.0 from 11.12.2013. There is no new build of this library.

This email message has content which is in 8-bit form and specified as Utf-8.  Any email message with 8-bit characters must be encoded as either utf-8 or quoted-printable and converted to Base64 form, as SMTP transport only allows 7-bit Ascii characters.

Martin

 I have really received this Email from internet.  So it is possible to send it anyway.

Yes, email is defective but Pegasus Mail should not crash. Otherwise Pmail specific mailbomb could be created.

[quote user="fojtik"]Yes, email is defective but Pegasus Mail should not crash. Otherwise Pmail specific mailbomb could be created.[/quote]

It doesn't crash on my machine, the only issue I see with IERenderer is a failure to decode the UTF-8 encoding. And with regard to crash dumps: The only reliable way to help is by taking the steps described in this post on top of the support forum.

I have reproduced a crash on two different machines.

On the second machine the Email is displayed, please click to "Attachment" tab and try to click

to "Plain text" and "HTML text", this will surely crash.

Sorry, I cannot download the latest libtidy :( - you claim 11.08.2016, 23:00 (MST): Version 2.4.9.1, but the only release available to download is from 2010. Please post it or send me it. May be tat this would fix an issue.

PS: I have reinstalled  IE renderer to 2.4.9.13, BUT THE PMAIL STILL CRASHES. Mini dump is useless for this crash because it does not find anything.

[quote user="fojtik"]I have reproduced a crash on two different machines.

On the second machine the Email is displayed, please click to "Attachment" tab and try to click

to "Plain text" and "HTML text", this will surely crash.[/quote]

No reason to yell at us. The more details you provide the better we can figure out what to do for fixing.

[quote user="fojtik"]On the second machine the Email is displayed, please click to "Attachment" tab and try to click to "Plain text" and "HTML text", this will surely crash.[/quote]

I can duplicate this now.

[quote user="fojtik"]There is no newer version of LibTidy[/quote]

Correct.

[quote user="fojtik"]BUT THE PMAIL STILL CRASHES. Mini dump is useless for this crash because it does not find anything.[/quote]

Wrong, it just created a dump on my machine after taking the steps you described above. If it doesn't do so when loaded as an extension you should try MiniDump's "stand-alone" mode as described in its ReadMe file (from its debugger section):

The package now also includes a "stand-alone" debugger (PMDebug.exe) which does essentially the same as the extension except that it does not prompt for user input and cannot grab Pegasus Mail's system configuration automatically. It may be more reliable in some cases as it does not run as part of Pegasus Mail and will not be affected by its crashes. It works like follows: [...]

(More details about how it works in succeeding paragraphs)

But aside from this you're right: The call stack doesn't help fixing this since it points to TER/HTS which we cannot easily fix ourselves:

kernel32!UnhandledExceptionFilter+0x60
WARNING: Stack unwind information not available. Following frames may be wrong.
ter32!CellBorderColorParam+0x1b201b
ter32!CellBorderColorParam+0x109a53
ter32!CellBorderColorParam+0x108380
ter32!CellBorderColorParam+0x10fff2
ter32!CellBorderColorParam+0x110785
ter32!CellBorderColorParam+0x110fb8
ter32!CellBorderColorParam+0x114049
hts32!HtsSetFontSize+0x5e0b8
hts32!HtsSetFontSize+0x12c19
hts32!HtsSetFontSize+0x129be
hts32!HtsSetFontSize+0x2bbea
hts32!HtsSetFontSize+0x2b7a7
hts32!HtsSetFontSize+0x2875a
hts32!HtsSetFontSize+0x27c69
hts32!HtsSetFontSize+0x18fa3

I might be able to do something about it by fixing my UTF-8 decoding for IERenderer, it might help avoiding the crash in TER/HTS as well.

Thanks for providing crash dumps: The crash shown in there is different from the one I could duplicate. I still have to run Pegasus Mail via my Delphi debugger for checking the UTF-8 decoding failure, but I don't know for sure whether this will fix your and my crashs at the same time.

It is good that you can duplicate crash. I am not using minidump so frequently as you do, so I can do something wrong.

I did completelly different approach, I have used Visual studio 2008 Express, attach to PMail process and then  try to open defective mail. Visual studio did not catch any callstack as it does for many other cases.

Please keep in mind that this kind of crash could be misused with black hat people to generate mailbomb and/or to inject some type of worm.

If you have some fixed DLL, I can test it :).

[quote user="fojtik"]Please keep in mind that this kind of crash could be misused with black hat people to generate mailbomb and/or to inject some type of worm. [/quote]

Pegasus Mail isn't wide spread enough to serve as a worthwhile target, nobody would really bother to create code targeting some 10,000 users worldwide.

[quote user="fojtik"]It is good that you can duplicate crash. I am not using minidump so frequently as you do, so I can do something wrong.[/quote]

Like I wrote before, the crash I can duplicate isn't the same one you encounter (comparing the call stacks of both tells me so). The one happening when opening the HTML part as attachment cannot be fixed without someone who can figure out why TER has a problem with you message, i.e. either David Harris or the developers of TER. I could fix the UTF-8 decoding failure, though, but it doesn't fix this crash either since IER isn't involved when opening HTML parts as attachments.

David Harris hasn't replied to my findings from your dump yet, so I don't have any idea how your crash can be fixed. IER isn't involved as far as the call stack tells me. So I have two more questions: What exactly do you do for getting the crash (other than opening the HTML part as attachment which is a different issue as explained above)? Is IMAP involved?

[quote]On the second machine the Email is displayed, please click to "Attachment" tab and try to click to "Plain text" and "HTML text", this will surely crash [/quote]

OK - if I do it that way, Pegasus crashes. I experienced that with other mails too. I think at that point the IERenderer isn't involved.

Anyway - why are you opening HTML (formatted version) that way? Pegasus doesn't crash, if you use the icon in the mails window for switching between text and formatted version of the mail (icon left of search-icon). Alternatively press SHIFT+A.