IER update

Michael

posted Nov 7 '19 at 11:52 am

[quote user="TonyQuick"]To be clear, and you probably know this already, my users have their mailbox location set to .\MAILBOX, but the location is actually configurable and doesn't have to be under the user's home directory at all. When you look at the info in Help | About Pegasus Mail | Info... you will see two mail box locations, "Home mailbox location:" and :New mailbox location:" Hopefully, you're using the configuration information for the mailbox location and not just "MAILBOX"[/quote]

Thanks, Pegasus Mail maintains Registry entries keeping this information and provides a runtime access API for extension developers, these are the sources I'm using, no need to worry ;-)

[quote user="TonyQuick"]To be clear, and you probably know this already, my users have their mailbox location set to .\MAILBOX, but the location is actually configurable and doesn't have to be under the user's home directory at all.&nbsp;When you look at the info in Help | About Pegasus Mail | Info...&nbsp; you will see two mail box locations, "Home mailbox location:" and :New mailbox location:"&nbsp; Hopefully, you're using the configuration information for the mailbox location and not just "MAILBOX"[/quote]Thanks, Pegasus Mail maintains Registry entries keeping this information and provides a runtime access API for extension developers, these are the sources I'm using, no need to worry ;-)

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Michael

posted Oct 17 '19 at 5:47 pm

Since nobody (except for Martin Ireland) appears to have read (or at least told so) my final reply to the IER and Viewer.pm thread I'm now opening an new thread here announcing my latest IER update solving at least the image display issue some people encountered with recent releases to get at least some more feedback, I hope - or should I say I'm afraid?

I can now at least tell that IER's image display issue has been solved after detecting a Windows "feature" I didn't ever expect to exist at all in combination with IE's special handling of long filenames with blank spaces that exclusively affects only MS browsers as far as I can tell. Whether the browser submenu issue has finally been fixed (some users just don't seeing it at all) I still can't tell for sure since the final tests still have to be done, but I have been redesigning its handling completely. If your'e interested in more details please take a look at IER's version history, I'll just provide a link to the ominious Windows feature here which even most people who encountered the image display issue very likely don't know having been struck by. Here's the download link, BTW ...

PS: Disabling 8.3 filenames on some systems (by sys-admins?) and using percent encoding (by me) for blanks in long filenames caused IE & IER to fail in loading images properly, to make a long story short ...

Since nobody (except for Martin Ireland) appears to have read (or at least told so) my final reply to the IER and Viewer.pm thread I'm now opening an new thread here announcing my latest IER update solving at least the image display issue some people encountered with recent releases to get at least some more feedback, I hope - or should I say I'm afraid? I can now at least tell that IER's image display issue has been solved after detecting a Windows "feature" I didn't ever expect to exist at all in combination with IE's special handling of long filenames with blank spaces that exclusively affects only MS browsers as far as I can tell. Whether the browser submenu issue has finally been fixed (some users just don't seeing it at all) I still can't tell for sure since the final tests still have to be done, but I have been redesigning its handling completely. If your'e interested in more details please take a look at <a mce_href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx" target="_blank" href="/files/folders/community_add-ons_for_pegasus_mail/entry24145.aspx">IER's version history</a>, I'll just provide a <a mce_href="https://support.microsoft.com/en-us/help/121007/how-to-disable-8-3-file-name-creation-on-ntfs-partitions" target="_blank" href="https://support.microsoft.com/en-us/help/121007/how-to-disable-8-3-file-name-creation-on-ntfs-partitions">link to the ominious Windows feature</a> here which even most people who encountered the image display issue very likely don't know having been struck by. Here's the <a mce_href="/files/folders/24145/download.aspx" href="/files/folders/24145/download.aspx">download link</a>, BTW ... PS: Disabling 8.3 filenames on some systems (by sys-admins?) and using percent encoding (by me) for blanks in long filenames caused IE &amp; IER to fail in loading images properly, to make a long story short ...

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Brian Fluet

posted Oct 18 '19 at 3:40 am

MIchael, I saw your post and apologize for not acknowledging and expressing appreciation for your efforts. I know that's not what you're after but it's genuine so should be expressed. Thank you!

As for IER, I don't use email in a way that I would notice its benefits or shortcomings. I had a brief intense interest in it when configuration options and VIEWER.PM utilization were added but that was my intellectual curiosity at play.

    The browser submenu works for me
    So I'm as happy as can be.
    Upgrading IER you see
    Just isn't a priority.

Ok, that's embarrassing, but I'm posting it anyway. I hope it provides a lighthearted moment for somebody. [:)]

Brian Fluet

MIchael, I saw your post and apologize for not acknowledging and expressing appreciation for your efforts.&nbsp; I know that's not what you're after but it's genuine so should be expressed. Thank you! As for IER, I don't use email in a way that I would notice its benefits or shortcomings.&nbsp; I had a brief intense interest in it when configuration options and VIEWER.PM utilization were added but that was my intellectual curiosity at play. &nbsp;&nbsp;&nbsp; The browser submenu works for me &nbsp;&nbsp;&nbsp; So I'm as happy as can be. &nbsp;&nbsp;&nbsp; Upgrading IER you see &nbsp;&nbsp;&nbsp; Just isn't a priority. Ok, that's embarrassing, but I'm posting it anyway.&nbsp; I hope it provides a lighthearted moment for somebody.&nbsp; [:)]Brian Fluet

Michael

posted Oct 21 '19 at 10:23 am

[quote user="Brian Fluet"]

    The browser submenu works for me
    So I'm as happy as can be.
    Upgrading IER you see
    Just isn't a priority.

Ok, that's embarrassing, but I'm posting it anyway. I hope it provides a lighthearted moment for somebody. [:)][/quote]

Thanks, Brian, it does. Since you're an "influencer" [;)] I'm glad you took notice!

[quote user="Brian Fluet"]&nbsp;&nbsp;&nbsp; The browser submenu works for me &nbsp;&nbsp;&nbsp; So I'm as happy as can be. &nbsp;&nbsp;&nbsp; Upgrading IER you see &nbsp;&nbsp;&nbsp; Just isn't a priority. Ok, that's embarrassing, but I'm posting it anyway.&nbsp; I hope it provides a lighthearted moment for somebody.&nbsp; [:)][/quote]Thanks, Brian, it does. Since you're an "influencer" [;)] I'm glad you took notice!

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

David H. Lipman

posted Oct 23 '19 at 4:26 pm

Michael:

Is there a Silent install parameter for IERendererSetup.exe ?

Michael:Is there a Silent install parameter for IERendererSetup.exe ?

Michael

posted Oct 23 '19 at 4:44 pm

[quote user="David H. Lipman"]Is there a Silent install parameter for IERendererSetup.exe ?[/quote]

Yes, that's how Pegasus Mail's installer uses it, why do you ask? It requires a couple of additional commandline parameters.

[quote user="David H. Lipman"]Is there a Silent install parameter for IERendererSetup.exe ?[/quote]Yes, that's how Pegasus Mail's installer uses it, why do you ask? It requires a couple of additional commandline parameters.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

David H. Lipman

posted Oct 23 '19 at 6:05 pm

I scripted a process so I was looking if I would extend it.

shell 'wget -N "https://idw-doc.homepage.t-online.de/PMUtils/IERenderer.zip" --no-check-certificate'
run 'unzip -j -o IERenderer.zip'

I scripted a process so I was looking if I would extend it. &nbsp;&nbsp;&nbsp; shell 'wget -N "https://idw-doc.homepage.t-online.de/PMUtils/IERenderer.zip" --no-check-certificate' &nbsp;&nbsp;&nbsp; run&nbsp;&nbsp; 'unzip&nbsp; -j -o IERenderer.zip'

Michael

posted Oct 23 '19 at 6:15 pm

[quote user="David H. Lipman"]I scripted a process so I was looking if I would extend it.[/quote]

OK, the commandline is <IERendererSetup /SP- /VERYSILENT /SUPPRESSMSGBOXES "[PMBaseDir]">, where [PMBaseDir] is the directory which WINPM-32.EXE is located in, e.g. "X:\PMAIL\Programs\".

[quote user="David H. Lipman"]I scripted a process so I was looking if I would extend it.[/quote]OK, the commandline is &lt;IERendererSetup /SP- /VERYSILENT /SUPPRESSMSGBOXES "[PMBaseDir]"&gt;, where [PMBaseDir] is the directory which WINPM-32.EXE is located in, e.g. "X:\PMAIL\Programs\".

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

David H. Lipman

posted Oct 23 '19 at 6:29 pm

Danke Michael.

David H. Lipman

posted Oct 25 '19 at 2:31 am

FYI

Function Get_IERenderer()
 cls
 GoThere("E:\STUFF\PMail")
 $T1=GetFileTime("IERenderer.zip")
 shell 'wget -N "https://idw-doc.homepage.t-online.de/PMUtils/IERenderer.zip" --no-check-certificate'
 $T2=GetFileTime("IERenderer.zip")
 if ($T1 <> $T2)=1
 EndProc("WINPM-32.EXE")
 del "C:\PMAIL\IN\MAILBOXP.LCK"
 shell 'unzip -j -o IERenderer.zip'
 shell 'IERendererSetup.exe /SP- /VERYSILENT /SUPPRESSMSGBOXES C:\PMAIL '
 sleep 5
 run $cmd+" start /MIN C:\PMAIL\winpm-32.exe "
 endif
EndFunction

FYI Function Get_IERenderer() &nbsp;&nbsp; &nbsp;cls &nbsp;&nbsp; &nbsp;GoThere("E:\STUFF\PMail") &nbsp;&nbsp; &nbsp;$T1=GetFileTime("IERenderer.zip") &nbsp;&nbsp; &nbsp;shell 'wget -N "https://idw-doc.homepage.t-online.de/PMUtils/IERenderer.zip" --no-check-certificate' &nbsp;&nbsp; &nbsp;$T2=GetFileTime("IERenderer.zip") &nbsp;&nbsp; &nbsp;if ($T1 &lt;&gt; $T2)=1 &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;EndProc("WINPM-32.EXE") &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;del "C:\PMAIL\IN\MAILBOXP.LCK" &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;shell 'unzip -j -o IERenderer.zip' &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;shell 'IERendererSetup.exe /SP- /VERYSILENT /SUPPRESSMSGBOXES C:\PMAIL ' &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;sleep 5 &nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;run $cmd+" start /MIN C:\PMAIL\winpm-32.exe " &nbsp;&nbsp; &nbsp;endif EndFunction

Joerg

posted Oct 27 '19 at 5:08 pm

Moin Michael,

Now I've updated our network Pmail installation with IER 2.6.2.12. Setup from a client machine to the server run properly without errors and also Pmail is showing all html mails as it should. Will further observe and report any weird behaviour. Thanks for your effort.

Gruss aus Rostock

Moin Michael,Now I've updated our network Pmail installation with IER 2.6.2.12. Setup from a client machine to the server run properly without errors and also Pmail is showing all html mails as it should. Will further observe and report any weird behaviour. Thanks for your effort. Gruss aus Rostock

Brian Fluet

posted Oct 27 '19 at 8:30 pm

Joerg,

I'm curious how you handled the VIEWER.PM file. My understanding is that the current IER will update the VIEWER.PM file located in the mailbox directory of the user from which it was installed when the one in the Pegasus Mail\Programs directory isn't accessible. I'm assume your server installed Pegasus Mail\Programs is secured from users just like mine is so did you copy the resulting VIEWER.PM file to the \Programs directory or did you place a copy in each mailbox directory?

Joerg,I'm curious how you handled the VIEWER.PM file.&nbsp; My understanding is that the current IER will update the VIEWER.PM file located in the mailbox directory of the user from which it was installed when the one in the Pegasus Mail\Programs directory isn't accessible.&nbsp; I'm assume your server installed Pegasus Mail\Programs is secured from users just like mine is so did you copy the resulting VIEWER.PM file to the \Programs directory or did you place a copy in each mailbox directory?&nbsp;

Joerg

posted Oct 28 '19 at 9:10 am

Hi Brian,

The last time I updated the IER (v2.6.2.2) I described my problems with the viewer.pm here: http://community.pmail.com/forums/post/51071.aspx.

Nevertheless my update procedure was the same this time, of course after making a backup copy of the entire Pmail directory. But this time (v2.6.2.12 - how frequent Michael is updating his program? [:D]) we don't experience any crashes etc., at least nobody of my users have claimed anything this Monday morning - keeping fingers crossed.

I don't take care of the central viewer.pm, which resides in pmail\programs. It seems this file will be updated by single Pmail instances during day by day work. The last change date is of this morning, after users did start their work.

I don't restrict the access to Pmail\programs. All "Authenticated Domain Users" have "change" permissions. Due to security reasons this is not the best way, but since I was not able to solve the problem with our central address book (http://community.pmail.com/forums/thread/50998.aspx) I kept the permissions as they are.

Additional viewer.pm files reside in each user mailbox folder. My own viewer.pm looks like this:

1;.dat;-;W:\Apps\Fentun\fentun.exe
1;.vcs;-;\\marsrv4\pmail$\programs\pmical.exe
1;.ics;-;\\marsrv4\pmail$\programs\pmical.exe
1;.pdf;-;C:\Program Files\Nitro\Pro 11\NitroPDF.exe

and has not been updated for a long time.

In general I don't like to deal with viewer.pm again on each IER update. And I don't understand the functionality completely. I only install the IER update and check whether Pmail is able to open html mails without crashing. [;)]

Hi Brian,The last time I updated the IER (v2.6.2.2) I described my problems with the viewer.pm here: <a mce_href="/forums/post/51071.aspx" target="_blank" title="http://community.pmail.com/forums/post/51071.aspx" href="/forums/post/51071.aspx">http://community.pmail.com/forums/post/51071.aspx.</a>Nevertheless my update procedure was the same this time, of course after making a backup copy of the entire Pmail directory. But this time (v2.6.2.12 - how frequent Michael is updating his program? [:D]) we don't experience any crashes etc., at least nobody of my users have claimed anything this Monday morning - keeping fingers crossed.I don't take care of the central viewer.pm, which resides in pmail\programs. It seems this file will be updated by single Pmail instances during day by day work. The last change date is of this morning, after users did start their work. I don't restrict the access to Pmail\programs. All "Authenticated Domain Users" have "change" permissions. Due to security reasons this is not the best way, but since I was not able to solve the problem with our central address book (<a mce_href="/forums/thread/50998.aspx" target="_blank" title="http://community.pmail.com/forums/thread/50998.aspx" href="/forums/thread/50998.aspx">http://community.pmail.com/forums/thread/50998.aspx</a>) I kept the permissions as they are.Additional viewer.pm files reside in each user mailbox folder. My own viewer.pm looks like this:1;.dat;-;W:\Apps\Fentun\fentun.exe 1;.vcs;-;\\marsrv4\pmail$\programs\pmical.exe 1;.ics;-;\\marsrv4\pmail$\programs\pmical.exe 1;.pdf;-;C:\Program Files\Nitro\Pro 11\NitroPDF.exeand has not been updated for a long time.In general I don't like to deal with viewer.pm again on each IER update. And I don't understand the functionality completely. I only install the IER update and check whether Pmail is able to open html mails without crashing. [;)]

Joerg

posted Oct 29 '19 at 9:09 am

Hi Brian,

The last time I updated the IER (v2.6.2.2) I described my problems with the viewer.pm here: http://community.pmail.com/forums/post/51071.aspx.

Nevertheless my update procedure was the same this time, of course after making a backup copy of the entire Pmail directory. But this time (v2.6.2.12 - how frequent Michael is updating his program? [:D]) we don't experience any crashes etc., at least nobody of my users have claimed anything this Monday morning - keeping fingers crossed.

I don't take care of the central viewer.pm, which resides in pmail\programs. It seems this file will be updated by single Pmail instances during day by day work. The last change date is of this morning, after users did start their work.

I don't restrict the access to Pmail\programs. All "Authenticated Domain Users" have "change" permissions. Due to security reasons this is not the best way, but since I was not able to solve the problem with our central address book (http://community.pmail.com/forums/thread/50998.aspx) I kept the permissions as they are.

Additional viewer.pm files reside in each user mailbox folder. My own viewer.pm looks like this:

1;.dat;-;W:\Apps\Fentun\fentun.exe
1;.vcs;-;\\marsrv4\pmail$\programs\pmical.exe
1;.ics;-;\\marsrv4\pmail$\programs\pmical.exe
1;.pdf;-;C:\Program Files\Nitro\Pro 11\NitroPDF.exe

and has not been updated for a long time.

In general I don't like to deal with viewer.pm again on each IER update. And I don't understand the functionality completely. I only install the IER update and check whether Pmail is able to open html mails without crashing. [;)] Then I forget it.

Hi Brian, The last time I updated the IER (v2.6.2.2) I described my problems with the viewer.pm here: http://community.pmail.com/forums/post/51071.aspx. Nevertheless my update procedure was the same this time, of course after making a backup copy of the entire Pmail directory. But this time (v2.6.2.12 - how frequent Michael is updating his program? [:D]) we don't experience any crashes etc., at least nobody of my users have claimed anything this Monday morning - keeping fingers crossed. I don't take care of the central viewer.pm, which resides in pmail\programs. It seems this file will be updated by single Pmail instances during day by day work. The last change date is of this morning, after users did start their work. I don't restrict the access to Pmail\programs. All "Authenticated Domain Users" have "change" permissions. Due to security reasons this is not the best way, but since I was not able to solve the problem with our central address book (http://community.pmail.com/forums/thread/50998.aspx) I kept the permissions as they are. Additional viewer.pm files reside in each user mailbox folder. My own viewer.pm looks like this: 1;.dat;-;W:\Apps\Fentun\fentun.exe 1;.vcs;-;\\marsrv4\pmail$\programs\pmical.exe 1;.ics;-;\\marsrv4\pmail$\programs\pmical.exe 1;.pdf;-;C:\Program Files\Nitro\Pro 11\NitroPDF.exe and has not been updated for a long time. In general I don't like to deal with viewer.pm again on each IER update. And I don't understand the functionality completely. I only install the IER update and check whether Pmail is able to open html mails without crashing. [;)] Then I forget it.

Michael

posted Oct 29 '19 at 9:57 am

[quote user="Brian Fluet"]I'm curious how you handled the VIEWER.PM file. My understanding is that the current IER will update the VIEWER.PM file located in the mailbox directory of the user from which it was installed when the one in the Pegasus Mail\Programs directory isn't accessible. I'm assume your server installed Pegasus Mail\Programs is secured from users just like mine is so did you copy the resulting VIEWER.PM file to the \Programs directory or did you place a copy in each mailbox directory?[/quote]

Just for avoiding any confusion about this: The IER setup doesn't modify any VIEWER.PM file at all. IER itself attempts to modify the one in Pegasus Mail's ... \programs\... directory first and doesn't do anything else if succeeding. If it fails it modifies the one in the mailbox of the user who just started his Pegasus Mail instance. This is not connected to the installation in any kind, just to the user instance start-up and will be repeated anytime another user launches his account.

Since I finally detected the real reason behind the image display failure issue I could have dropped all this, but IMO it could very well become a future security issue once again (due to some major company's wisdom [;)]) to only allow loading of images using their proper filename extensions. And the purpose of adding media file types and mime types to VIEWER.PM is to force Pegasus Mail to pass on embedded media files with their proper filename extensions attached when extracting those files from messages for IER and BearHtml.

And with reagard to the crash Joerg encountered: I was able to duplicate it during my tests for modifying the implementation of all this so I could fix it - but I don't remember the details anymore.

BTW: Does anyone of you know anyone who encountered the missing browser context menu issue? I'm still waiting for someone to confirm or deny its further existance after putting lots of efforts into trying to fix it without being able to ever duplicate it ...

[quote user="Brian Fluet"]I'm curious how you handled the VIEWER.PM file.&nbsp; My understanding is that the current IER will update the VIEWER.PM file located in the mailbox directory of the user from which it was installed when the one in the Pegasus Mail\Programs directory isn't accessible.&nbsp; I'm assume your server installed Pegasus Mail\Programs is secured from users just like mine is so did you copy the resulting VIEWER.PM file to the \Programs directory or did you place a copy in each mailbox directory?[/quote]Just for avoiding any confusion about this: The IER setup doesn't modify any VIEWER.PM file at all. IER itself attempts to modify the one in Pegasus Mail's ... \programs\... directory first and doesn't do anything else if succeeding. If it fails it modifies the one in the mailbox of the user who just started his Pegasus Mail instance. This is not connected to the installation in any kind, just to the user instance start-up and will be repeated anytime another user launches his account. Since I finally detected the real reason behind the image display failure issue I could have dropped all this, but IMO it could very well become a future security issue once again (due to some major company's wisdom [;)]) to only allow loading of images using their proper filename extensions. And the purpose of adding media file types and mime types to VIEWER.PM is to force Pegasus Mail to pass on embedded media files with their proper filename extensions attached when extracting those files from messages for IER and BearHtml.And with reagard to the crash Joerg encountered: I was able to duplicate it during my tests for modifying the implementation of all this so I could fix it - but I don't remember the details anymore.BTW: Does anyone of you know anyone who encountered the missing browser context menu issue? I'm still waiting for someone to confirm or deny its further existance after putting lots of efforts into trying to fix it without being able to ever duplicate it ...

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Brian Fluet

posted Oct 29 '19 at 12:36 pm

I had forgotten that VIEWER.PM updated on start of Pegasus Mail after doing the IER update. [:$]

I had forgotten that VIEWER.PM updated on start of Pegasus Mail after doing the IER update.&nbsp; [:$] &nbsp;&nbsp;

Michael

posted Oct 29 '19 at 4:50 pm

[quote user="Brian Fluet"]I had forgotten that VIEWER.PM updated on start of Pegasus Mail after doing the IER update. [:$][/quote]

Honestly, I wouldn't even have tried to let it do the installer (I'm sure it would be possible) because this would have been a nightmare to debug ...

[quote user="Brian Fluet"]I had forgotten that VIEWER.PM updated on start of Pegasus Mail after doing the IER update.&nbsp; [:$][/quote]Honestly, I wouldn't even have tried to let it do the installer (I'm sure it would be possible) because this would have been a nightmare to debug ...

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

TonyQuick

posted Nov 5 '19 at 12:54 am

Thanks for the update. I don't check for updates to Pegasus often since it has been mostly stable for us. I found the update for IERenderer 2.6.2.12 on Friday (Nov 1) and installed it on a network installation of Pegasus 3.73.639. The first thing I noticed was that with my default browser set to Edge, I could open links from emails in the browser normally. I opened several emails and everything looked good.

Until Monday morning...

Some users were getting a run-time error 217 at 06E6C532, after which Pegasus would close. (Actually, only one person recorded the address, the others only reported the error number). All of the users who reported this error have no viewer.pm in the PMAIL folder, and they would not have write access to the Pegasus programs folder.

A few noticed that HTML formatted emails cannot be scrolled with the mouse wheel. (Actually, that's happening on my computer too.)

Replying to and printing HTML formatted emails is very slow at times, causing the Pegasus title bar to show Not Responding for several seconds.

I had to revert IERenderer back to 2.4.10.3 (that's the version we were using before) for now.

Also, not sure if it matters, but I was unable to use the installer on my network installation and had to use InnoUnpacker to extract the files and copy them into the Pegasus programs folder.

Not sure what information I can provide to help track down the problems, but will do what I can.

Regards,

Tony

Thanks for the update. I don't check for updates to Pegasus often since it has been mostly stable for us.&nbsp;I found the update for IERenderer 2.6.2.12 on Friday (Nov 1) and installed it on a network installation of Pegasus 3.73.639.&nbsp; The first thing I noticed was that with my default browser set to Edge, I could open links from emails in the browser normally. I opened several emails and everything looked good.Until Monday morning...Some users were getting a run-time error 217 at 06E6C532, after which Pegasus would close.&nbsp; (Actually, only one person recorded the address, the others only reported the error number). All of the users who reported this error have no viewer.pm in the PMAIL folder, and they would not have write access to the Pegasus programs folder.A few noticed that HTML formatted emails cannot be scrolled with the mouse wheel. (Actually, that's happening on my computer too.)Replying to and printing HTML formatted emails is very slow at times, causing the Pegasus title bar to show Not Responding for several seconds.I had to revert IERenderer back to 2.4.10.3 (that's the version we were using before) for now.&nbsp;Also, not sure if it matters, but I was unable to use the installer on my network installation and had to use InnoUnpacker to extract the files and copy them into the Pegasus programs folder.Not sure what information I can provide to help track down the problems, but will do what I can.&nbsp;Regards,Tony&nbsp;

Michael

posted Nov 5 '19 at 11:18 am

[quote user="TonyQuick"]Some users were getting a run-time error 217 at 06E6C532, after which Pegasus would close. (Actually, only one person recorded the address, the others only reported the error number). All of the users who reported this error have no viewer.pm in the PMAIL folder, and they would not have write access to the Pegasus programs folder.[/quote]

They shouldn't need to have as I wrote in a previous reply. I though I had already taken care of such cases, maybe I have to look at it again. It might take a while because I'm currenty migrating the code to a more recent version of my programming environment for bringing it all to Windows 10 and future support of pure 64bit environments.

[quote user="TonyQuick"]A few noticed that HTML formatted emails cannot be scrolled with the mouse wheel. (Actually, that's happening on my computer too.)[/quote]

There might already be a fix in my current test code due to the above mentioned migration attempts :-)

[quote user="TonyQuick"]Replying to and printing HTML formatted emails is very slow at times, causing the Pegasus title bar to show Not Responding for several seconds.[/quote]

This is an issue I don't have any ideas about regarding my code since it doesn't only depend on IER, so I have three questions to begin with:

Is this a new issue as compared to IER 2.4.10.3?
Can you figure out a common pattern of such messages?
If you can, would it be possible to get sample messages to duplicate it?

One hint, though: As messages being printed, forwarded or being replied to must be dealt with by Pegasus Mail's built-in HTS/TER module the printer comes into play (which doesn't matter for IERs display). Could there be some kind of printer access issue be involved, i.e. the respective machine's Windows default printer not being connected to the network? There's a pretty simple test for this issue: Simply change the respective machine's default Windows printer temporarily to Generic / Text Only for testing and you'll immediately see its effects.

[quote user="TonyQuick"]Some users were getting a run-time error 217 at 06E6C532, after which Pegasus would close.&nbsp; (Actually, only one person recorded the address, the others only reported the error number). All of the users who reported this error have no viewer.pm in the PMAIL folder, and they would not have write access to the Pegasus programs folder.[/quote]They shouldn't need to have as I wrote in a previous reply. I though I had already taken care of such cases, maybe I have to look at it again. It might take a while because I'm currenty migrating the code to a more recent version of my programming environment for bringing it all to Windows 10 and future support of pure 64bit environments. [quote user="TonyQuick"]A few noticed that HTML formatted emails cannot be scrolled with the mouse wheel. (Actually, that's happening on my computer too.)[/quote]There might already be a fix in my current test code due to the above mentioned migration attempts :-) [quote user="TonyQuick"]Replying to and printing HTML formatted emails is very slow at times, causing the Pegasus title bar to show Not Responding for several seconds.[/quote]This is an issue I don't have any ideas about regarding my code since it doesn't only depend on IER, so I have three questions to begin with:<ol><li>Is this a new issue as compared to IER 2.4.10.3?</li><li>Can you figure out a common pattern of such messages?</li><li>If you can, would it be possible to get sample messages to duplicate it?</li></ol><div>One hint, though: As messages being printed, forwarded or being replied to must be dealt with by Pegasus Mail's built-in HTS/TER module the printer comes into play (which doesn't matter for IERs display). Could there be some kind of printer access issue be involved, i.e. the respective machine's Windows default printer not being connected to the network? There's a pretty simple test for this issue: Simply change the respective machine's default Windows printer temporarily to Generic / Text Only for testing and you'll immediately see its effects. </div>

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

TonyQuick

posted Nov 5 '19 at 4:49 pm

I found that the users who are getting the run-time errors are not using the default home mailbox location. They actually do have a viewer.pm but it's in their home mailbox folder which is MAILBOX, not PMAIL. (You may be wondering why? These are users who have worked here a long time and at one point in time we were having space issues on the volume where the home directories are stored.)

Strangely, I'm not seeing the scrolling issue this morning. Not sure what to make of that...

Regarding the printing and reply issues, it may well be a network printer issue. I haven't been able to reproduce it on my machine which has a directly attached printer, and the users who reported the problems have their default printer set to a shared printer. When I looked at their stations today, I'm not seeing the issue there either.

So, it appears I only have the issue with the non-default home mailboxes at this point.

Regards,

Tony

I found that the users who are getting the run-time errors are not using the default home mailbox location. They actually do have a viewer.pm but it's in their home mailbox folder which is MAILBOX, not PMAIL. (You may be wondering why?&nbsp;These are users who have worked here a long time and at one point in time we were having space issues on the volume where the home directories are stored.)Strangely, I'm not seeing the scrolling issue this morning.&nbsp; Not sure what to make of that...&nbsp;Regarding the&nbsp;printing and reply issues, it may well be a network printer issue. I haven't been able to reproduce it on my machine which has a directly attached printer, and the users who reported the problems have their default printer set to a shared printer.&nbsp; When I looked at their stations today, I'm not seeing the issue there either.So, it appears I only have the issue with the non-default home mailboxes at this point.Regards,Tony&nbsp;&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history