I agree with Brian, things like remote images are by their names not stored with the message, but fetched when the message is opened (in Bearhtml or IERenderer). Secondly, on the same point, once the images are displayed, the page can be printed, but of course the images are binary object and cannot be handled unless by special software (bearhtml or IERenderer) that captures and handles them.
So as Brian mentioned the only way to print would be to use a utility like Notsplit (mine) and then collect up all the individual files and zip them up. That would be a lot of work, and is just duplicating what is already in existence, namely Pegasus Mail folders. But remote images are not collected in folders, so that part of the message would be missing until opened by either Bearhtml or IERenderer..
If the images are what you want, you should start saving them as you receive the messages in a directory setup for holding them.
HTH
Martin
<p>I agree with Brian, things like remote images are by their names not stored with the message, but fetched when the message is opened (in Bearhtml or IERenderer). Secondly, on the same point, once the images are displayed, the page can be printed, but of course the images are binary object and cannot be handled unless by special software (bearhtml or IERenderer) that captures and handles them.</p><p>So as Brian mentioned the only way to print would be to use a utility like Notsplit (mine) and then collect up all the individual files and zip them up. That would be a lot of work, and is just duplicating what is already in existence, namely Pegasus Mail folders. But remote images are not collected in folders, so that part of the message would be missing until opened by either Bearhtml or IERenderer..</p><p>If the images are what you want, you should start saving them as you receive the messages in a directory setup for holding them.</p><p>&nbsp;</p><p>HTH</p><p>Martin
</p>