After installing IER 2.7.0.7 I had this warning from Pegasus when checking IER last version.

"cannot read the timestamp of IERenderer module"

I usually install moving files into IER dir on my server, maybe I forgot to move a file there?

If your installation process is to extract IERendererSetup.exe with InnoUnpacker and then copy the appropriate files to \Pmail\Programs and \Pmail\Programs\IERenderer on your server then I suspect that something went wrong so would try again.

You might also want to check permissions to the files in \Pmail\Programs\IERenderer.

FWIW, I run a portable version of PMail in which I update IER using the extract method. An IER update check in it worked fine.

Thank you Brian,

yes, I do extract as you wrote.

I did it again but still same problem.

I have permissions on that W server.

I don't know what would produce that warning so I we'll need to wait for Michael's thoughts.

This error usually occurs if IERenderer.dll's digital signature cannot be read - which I actually only encounter if there is none at all (like when I'm recompiling test versions without signing them during development). I'm using the signature's timestamp (coming from Sectigo's timestamp signature) because it's the most reliable version info I can get, filetimes are only file system properties and version numbers can easily be modified using any kind of resource hacker. You can check whether the timestamp signature on your file exists by right clicking IERenderer.dll, selecting the file properties and looking at the bottom of it's Digital Signature page: The first signature shown there will be my self-signed one, if opening the Details page it'll show the Sectigo timestamp like this one (it's not the one from IERenderer and its a German display):

If it's there and you get this error there must be something else preventing IER from reading and decoding the timestamp information, maybe an outdated system which cannot handle SHA-512 signatures (SHA-1 isn't safe anymore).

Hi Michael, thanks for your reply.

Your signature is there, but certificate looks missing... I tried to import the certificate but message is still there: "a successfully processed certificate chain ends in a root certificate from a Certificate Authority that is not in the local list"

Any idea?

But this doesn't matter with regard to the time stamp, it can be used and read nevertheless since it's coming from a certified time stamp provider. If you want to get rid of this error you need to import my certificate into the Windows certificate data base as a Trusted root certification authority, starting with step #3 as described here: https://techcommunity.microsoft.com/t5/windows-server-essentials-and/installing-a-self-signed-certificate-as-a-trusted-root-ca-in/ba-p/396105. But as I already wrote above: It's not required for reading the timestamp programmatically since most people won't have installed my certificate into their database either, so there may be some other access issue which I don't know of.

Did it ever work in previous cases? From which version are you trying to update? There was a version where it didn't work properly because of some coding issue, but this should be fixed in newer versions (it's mentioned in the release history for Version 2.6.6.5).

[Edit: Website updated to allow linking to single version histories]

I did as per your suggestion.

Now the certificate is properly installed (I verified too).

Problem is still there...

I'm starting to think there is something different going on:

1) clicking on links within a message, often gives this message:

"An error occurred while attempting to verify the file type of <index.php>:
12002 - Timeout dell'operazione.
Do you want to allow your browser to download it nevertheless?"

2) At certain point I had the message [IERenderer] "Access Denied" and Pegasus Mail crashed.

3) Spamhalter "traffic light" is often grey, while spam probability is very high

Maybe these things are unrelated to each other but everything is working noticeably worse than usual...

Timestamp problem itself started with 2.7.0.3. now I'm on 2.7.0.7.

This happens when doing security checks and isn't anything to worry about too much, php scripts are a common part of lots of web sites and download paths.

This should not happen, of course, and figuring out the reasons would require you to notice any patterns and forward certain messages involved (if duplicatable) or MiniDump's created by my respective tool fom https://www.pmpgp.de/pmtools/MiniDumpAndSources.zip.

Nothing I can say about this ...

What Windows version is involved?