[quote user="rooster"]After digging around some more, I discovered (and I apologize for this) that the problem is in the IERenderer and NOT in the "native" Pegasus HTML renderer.[/quote]

Nevertheless, could you be so kind as to forward the respective message as a zipped CNM file from your new mail directory so I can fix this issue if possible at all, at least for other users if you prefer not to use IERenderer?

It seems that PMail 4.61 has an HTML anchor error in its native HTML rendering code.  (Version 4.52 and earlier did NOT have this error.)

The problem seems to be that, when PMail encounters a clicked hotlink to an internal HTML anchor, instead of going to the named anchor it displays a "404 Not found" error screen that replaces the email message (which, by the way, seems impossible to recover from except by clicking back and forth between either the next or previous message and then back on the current message again).

For me, this situation occurs quite frequently when viewing messages in Yahoo groups.  If a message has an attachment, there's a hotlinked notice at the beginning of the message which, if clicked, is supposed to jump to the bottom of the message, where the actual hotlink to the attachment stored on Yahoo's servers is found.  Basically, the top hotlink has an anchor "href" with the value "#TopText", and the bottom hotlink has an anchor "name" with the value "TopText".  Correct HTML rendering would jump from the top hotlink to the bottom hotlink when the top hotlink is clicked.

Harvey

Please send an example message, in its entirety, to irelam@telus.net and I will see that it gets inspected and passed on if required

Martin

[quote user="rooster"]It seems that PMail 4.61 has an HTML anchor error in its native HTML rendering code.  (Version 4.52 and earlier did NOT have this error.)[/quote]

Please try again after updating IERenderer from the download section.

After digging around some more, I discovered (and I apologize for this) that the problem is in the IERenderer and NOT in the "native" Pegasus HTML renderer.  I was shocked to discover that Pegasus had the IERenderer as its default setting rather than its native renderer.  The native renderer does not exhibit the problem I described.  Thanks!

Harvey