I tried to reply to that message from a different PC (Win 7 32bit).

It looks that in any way, Pegasus seems to not like at all replying to that message, it start behaving strange, slowing down, graphic appearance of parts of Pegasus (e.g. buttons) are affected/ disappearing and finally it goes freezing itself in a few clicks,

Even if I can discard the reply, Pegasus seems to remain unstable and it needs to be restarted.

Trying same thing with IErenderer turned off takes Pegasus to immediate crash.

I hope this can help.

In my office we have Pegasus Mail on a file server and about 15 clients running it.

Sometimes, HTML messages with logos and tables can crash Pegasus.

Most of our people don't deal with such messages, while just a couple of them are receiving and replying to HTML messages with logos and tables. Those messages keep growing because of the "conversation" going back and forth with customers and each side just press "reply" keeping all the previous conversation.

 When one of those messages reach a size which I don't know (but the last one was about 900kB), Pegasus tries hard to show it in the preview, then it can open it (slowly) but if you press "Reply" keeping HTML formatting, Pegasus crashes.

(Sometimes I have an "Access violation" message but when it happens, Pegasus don't seem to crash.)

Here is the PMdebug dump.

 -----

Win70/S8R - 32bit + Internet Explorer 11.00.9600.19081 +
Pegasus Mail 4.73 + Brother HL-5340D series (Copia 1) +
IERenderer 2.4.10.3 (BearHtml 4.9.9.1)

Pegasus Mail's system information couldn't be attached due to the actual
crash conditions. Please open Pegasus Mail's 'Help' menu, select 'About
Pegasus Mail...' and press the 'Info' button: Now select all dialog text,
copy it using 'Ctrl + C' and paste it into this message using 'Ctrl + V'.

Pegasus Mail for Microsoft Windows
Copyright (C) 1992-2018, David Harris, all rights reserved
Electronic mail to support@pmail.gen.nz.

WinPMail version: Version 4.73.639, Mar 30 2018, build ID 639
Language resources: Standard UK English resource set
Extension Manager version: 1.14
Operating mode: Standalone
User name and ID: giuliett, 0
Windows version: 6.1
Windows flag word: 0
WINPMAIL.EXE directory: N:\Disco2\pegasus\Programs
Home mailbox location: N:\DISCO2\USERS\giuliett
New mailbox location: N:\DISCO2\USERS\giuliett
TMP environment variable: C:\Users\GIULIE~1\AppData\Local\Temp
TEMP environment variable: C:\Users\GIULIE~1\AppData\Local\Temp
LAN-based SMTP support: N, N, N
NetWare MHS support: N, N, N
Built-in TCP/IP support: Enabled
  - WINSOCK version: WinSock 2.0
  - WINSOCK path: WSOCK32.DLL
Commandline: -i giuliett
Active -Z options: 32768
PMR variable: (None)
PML variable: (None)
MAI variable: (None)
NB variable: (None)
Autofiltering folders: 0 (0 active, 0 inactive)
Last new mail count: 18
Message size soft limit: 0 bytes
Message size hard limit: 0 bytes
Attachment size soft limit: 0 bytes
Attachment size hard limit: 0 bytes

=> Please also add some descriptional text to explain what happened before
Pegasus Mail "crashed"!

Replying to big (900kB) HTML message with "preserve HTML formatting"
option enabled. If option is disabled, reply is prepared, Pegasus doesn't
crash.

-----

Thanks if somebody can help. :)

[quote user="NickStick"]Thanks if somebody can help.[/quote]

Sorry, no, this isn't the dump: It's attached to the message you copied the information from into your post here. The only thing you need to do is send this message including its attachment to the address already inserted as its recipient. It would also be helpful to get such a crashing message for trying to duplicate the issue, zipped up "as is" and attached to another message to <beta-reports [at] pmail.gen.nz>. You can figure out its filename by right clicking it and selecting Message properties, the location would be the New mailbox location you already posted (if its the same user).

I've really tried to make it as easy as possible to provide a crash dump, but I really wonder why some people don't just send the message and instead try something more complex for doing so. It's somehow like college students trying to figure out the most complex answer they can think of instead of just the one everyone else would give [8-)] ...

Nevertheless: Thanks for trying to help. If you would prefer a more confidential way of providing a sample message please let me know.

Oh, sorry.

Actually I was confused by the fact that no recipient was automatically inserted in debug message.

I'll provide shortly.

Thank you very much.

[quote user="NickStick"]Actually I was confused by the fact that no recipient was automatically inserted in debug message.[/quote]

Well, this shouldn't happen, of course.

[quote user="idw"]

[quote user="NickStick"]Thanks if somebody can help.[/quote]

...The only thing you need to do is send this message including its attachment to the address already inserted as its recipient.

It would also be helpful to get such a crashing message for trying to duplicate the issue, zipped up "as is" and attached to another message to <beta-reports [at] pmail.gen.nz>. You can figure out its filename by right clicking it and selecting Message properties, the location would be the New mailbox location you already posted (if its the same user).

...

[/quote]

 Done, both things. :)

[quote user="NickStick"] Done, both things. :) [/quote]

Thanks a lot!

[quote user="NickStick"]Thanks if somebody can help.[/quote]

Tried replying to the sample message you provided and didn't get a crash on Windows 7 64bit. It might have been fixed inadvertantly though by the changes I applied for another IERenderer update not yet released. Taking a look at the dump will take a bit more time than I can afford today, you'll get another reply ASAP.