The problem is not clicking on a link in a message and opening it in a browser, but going from message to message in Pmail.

During 8-9 seconds nothing is happening when I select a next message from the tree. I see the cache-hits counting messages then in the status bar and finally this next message start to be rendering in the body window.  Sometimes this counting goes to 200, but mostly 20-30.

As stated, I have disabled cache also, but  I don't seem to see a difference.

So the sequence f.e. I do is:

1. After reading a mail, I move it to a folder
2. The next message is selected automatically
   
3. There is a delay of 8-9 seconds during which I see the cache count going on in the status bar.
4. Then only the message appears in the body window.

I don't seem to have had this in a previous release of Pmail, but I don't remember when it started.

I think earlier releases didn't have this cache system.

Pmail 4.63 in wine.

Now my issue of 'invalid variant type' is solved I can address the issue of delay in rendering due to cache hits.

When selecting another mail to display I see in the status bar the n° of cache hits done. Often 20-25, but in case up to 200.

This causes a considerable delay. I learned recently on the forum that the cache contains images, but I don't see very much the use of this as I didn't set to render images from the net.

I looked in the manual and in the options, but didn't find a way to disable this behavior.

Is there a possibility?

I don't believe you can set a limit on cache hits but you can set a limit on cache days.  Click on the toolbar IERenderer icon (the Pegasus superimposed over the Internet Explorer icon) and select Configure.  The second entry is where you can set the number of cache days.  I rarely allow remote graphics in Pegasus preferring to view graphics intensive message in Firefox so I keep my cache days set to zero.  The cache days is days from last access.  When I changed my setting to zero my image cache did not empty as expected.  I discovered that my daily AV scanner was changing the last accessed dates so my image cache never emptied until I did it manually.  Other folks reported their image cache adjusts normally so this seemed to be a problem associated with the AV scanner I was using.

[quote user="bfluet"]I don't believe you can set a limit on cache hits but you can set a limit on cache days.  Click on the toolbar IERenderer icon (the Pegasus superimposed over the Internet Explorer icon) and select Configure.  The second entry is where you can set the number of cache days.[/quote]

His (or her?) issue sounds a lot like (s)he's using BearHtml instead of IERenderer and I'm afraid there's nothing that can be done about it. Only Martin Ireland can tell for sure, though ...

[quote user="idw"]His (or her?) issue sounds a lot like (s)he's using BearHtml instead of IERenderer and I'm afraid there's nothing that can be done about it. Only Martin Ireland can tell for sure, though ...[/quote]

If so, there is a cache days setting in the bearhtml.ini file.  I assume it works the same way as the setting in IERenderer.  BearHTML doesn't have the nice configuration GUI the IERenderer has but can be configured manually via the .ini file.

[quote user="bfluet"]If so, there is a cache days setting in the bearhtml.ini file.  I assume it works the same way as the setting in IERenderer.[/quote]

I'm afraid this won't help since image download is said to be disabled. In such a case BearHtml does kind of a "simulated download" while actually replacing the remote images with a local stub and there's no switch for turning this off AFAIK.

Coding WantCache=false in Bearhtml.ini will stop checking cache directory for existing file and simply load the Default.bmp to create a gray box. Standard behaviour.  This preserves the document shaping to show the position and size of an image, the image can then be obtained from cache to avoid remote file fetching.  WantCache is a session parameter so changing its current setting lasts until it is recoded and Pegasus Mail is restarted.

Martin 

Thank you all for the answers.

My previous issue could only be solved by disabling IE rendering. So I can't apply suggestion in this area.

 I work now with

WantBl=Yes
WantIEcache=No

Wantcache=No 

(I tries false also)
cache-days=0 

 Up to now I still have the msg cache-hits:XX, downloads: 0, total XX.

So I suppose that nothing can be done.

The rendering of a next message is about 9 seconds, which I feel as long.

I probably have to live with it. I can't remember when this started.

I don't know as what you are seeing is abnormal.  I just tested rendering a WindowsSecrets newsletter in Pegasus and it took about 14 seconds (using BearHTML).  I have image caching disabled in BearHTML.  The same WindowsSecrets newsletter renders in about 1 second in Firefox but I am sure that many of the images are in the Firefox cache so this isn't a fair comparison.  Still, it could be an interesting test if you haven't been opening messages in a browser..

I really don't understand this thread. I get a total of 120 cache'd images displayed in 4 seconds. If I empty cache (shift + Ctrl +Y) it takes about 15 seconds to remote fetch all of these. I have a high speed link to my ISP so download time is very fast always, but will never beat a local hard drive cache, either IE or Bearhtml cache produce similar results. The intent of cache is to speed up display of second and subsequent message loading.

If you don't want the images, just select "manual load images" in Menu Tools/Options/Incoming Mail/Message reader.   Finally what I think you are seeing is the effect of FF, IE, and IERenderer  requesting multiple remote file fetches at the same time, whereas Bearhtml fetches one at a time (and will continue to do so).

Martin