[quote user="Christopher Muñoz"]I'll send you a couple of the misbehaving email messages, so that you can have a look, whether or not there's a remedy.  

How do you want me to get them out to you? [/quote]

Preferably zipped CNM files from the new mail directory, IERenderer's About dialog provides a link for contacting me.

BTW: It could also be a CSS (style) attribute causing this: white-space:nowrap.

Under 4.61 I'm back to using IER, with satisfaction.  Under 4.52 I had to give it up, and go back to BEARHTML, because IER was crashing nearly every time I clicked on a URL link in a HTML message (although I sometimes could right click on the same link without crashing). 

Now, under 2.0.4.3 and 4.61, that problem seems to have gone away.  However:  now, when viewing the HTML part of a multipart/alternative message in a reader window (I don't use preview mode), the text of the message (unless it's encapsulated in a graphics box) routinely fails to wrap to fit the reader window, which requires me either to (i) expand the window; (ii) use the horizontal scroll bar; or, (iii) load the message into a browser window, which then frequently loses some of the graphics. 

Not a complaint, more an observation.  Presumably a byproduct of other coding changes made to deal with all the bad HTML code out there - ? 

In passing, I also note that even if Winsock services always are loaded (as per the strong IER configuration recommendation), now the winsock activity status button on the lower right status bar lights up red only when a connection is "live", which is a welcome change.  Under PM 4.52 & earlier IER versions, when winsock always was loaded, the status button always was red.  Because I do need to know when a mail server is responding or not (in order to abort the connection before PM crashes), I couldn't go to "always" on winsock loading before, because I couldn't tell what was going on over the connection.  Now, I can always load.  Very helpful.  (Actually, I didn't really notice much performance difference before, though, whether "always" or "on demand" . . . ). 

[quote user="Christopher Muñoz"]However:  now, when viewing the HTML part of a multipart/alternative message in a reader window (I don't use preview mode), the text of the message (unless it's encapsulated in a graphics box) routinely fails to wrap to fit the reader window, which requires me either to (i) expand the window; (ii) use the horizontal scroll bar; or, (iii) load the message into a browser window, which then frequently loses some of the graphics.[/quote]

You can easily solve this issue by hitting F5 or Ctrl + F5 (or using the wrap or reformat long lines option from the reader's context menu (right-click)).

>> You can easily

solve this issue by hitting F5 or Ctrl + F5 (or using the wrap or

reformat long lines option from the reader's context menu

(right-click)).  

Thanks, I am conversant with the F5 & CTL-F5 options (I use them from time to time with text messages in the reader window), but I already do have that option turned on, so that toggling F5 (or CTL-F5) just makes the problem worse. Changing the reader window font doesn't help, either. 

I'm running the reader window sized at about 50% vertical & 70% horizontal, but maximizing the window is ineffective as well.  I may try it with the current version of Bear HTML, just to see. 

[quote user="Christopher Muñoz"]Thanks, I am conversant with the F5 & CTL-F5 options (I use them from time to time with text messages in the reader window), but I already do have that option turned on, so that toggling F5 (or CTL-F5) just makes the problem worse. Changing the reader window font doesn't help, either.  [/quote]

If none of this helps its a fixed size formatting (like an invisible table) implemented by the originiator, otherwise it should be freely adjustable. I don't think I can do anything about this, but if you want me to investigate it further I need one of these messages to look at.

>> . . . but if you want me to investigate it further I need one of these messages to look at. 

 Although we may be talking by each other here to some extent -- it's not that F5 is of no effect at all, it's just that it doesn't sufficiently wrap to fit the reader window, which was not the case with the last PM 4.52 version, and it's not a table or graphics issue -- I'll send you a couple of the misbehaving email messages, so that you can have a look, whether or not there's a remedy. 

How do you want me to get them out to you?