Community Discussions and Support
Pmail 4.80 doesn't work, and, re-install of 4.71 results in errors

Windows 10 user here.


Tried installing Pmail 4.80 and the install seemed to go well. But once I opened it, none of the menu items or buttons worked.


Uninstalled, then tried re-installing my previous version 4.71.


Menu items and buttons now work, however as I click into the saved emails, I get frequent error messages with "bad address" displayed. It's a bit of a hassle to get rid of them.


(These errors appear to relate to RAM addresses within a program, and NOT email addresses.)


I can click "X" for "close" on these error messages, but this happens frequently enough that I would really like to find out how to restore 4.71 to error-free operation.


Just a guess, but I don't think the problem is with the earlier versions of Pmail.


I tried a couple of earlier versions, and they, too have this "bad address" error message.


This reminds me of occasional errors I'd see when I did some Microsoft C programming, i.e. some pointer didn't have a valid address to point to.


It looks as if installing Pmail may cause modification of program modules outside the Pmail set, such as Windows modules? That might account for an error to show up in several different versions.


Any thoughts much appreciated.


Eleanor White


Windows 10 user here. Tried installing Pmail 4.80 and the install seemed to go well. But once I opened it, none of the menu items or buttons worked. Uninstalled, then tried re-installing my previous version 4.71. Menu items and buttons now work, however as I click into the saved emails, I get frequent error messages with "bad address" displayed. It's a bit of a hassle to get rid of them. (These errors appear to relate to RAM addresses within a program, and NOT email addresses.) I can click "X" for "close" on these error messages, but this happens frequently enough that I would really like to find out how to restore 4.71 to error-free operation. Just a guess, but I don't think the problem is with the earlier versions of Pmail. I tried a couple of earlier versions, and they, too have this "bad address" error message. This reminds me of occasional errors I'd see when I did some Microsoft C programming, i.e. some pointer didn't have a valid address to point to. It looks as if installing Pmail may cause modification of program modules outside the Pmail set, such as Windows modules? That might account for an error to show up in several different versions. Any thoughts much appreciated. Eleanor White

I should mention that some of these error messages showing up in re-installed Pmail 4.7.1 report a DIVIDE BY ZERO error.


Again, an error message reminiscent of programming in Microsoft C rather than a problem in 4.7.1 itself. Suggestive of a program module outside of the Pmail set which had been modified but not restored during the uninstall.


Eleanor White


I should mention that some of these error messages showing up in re-installed Pmail 4.7.1 report a DIVIDE BY ZERO error. Again, an error message reminiscent of programming in Microsoft C rather than a problem in 4.7.1 itself. Suggestive of a program module outside of the Pmail set which had been modified but not restored during the uninstall. Eleanor White

Tried installing Pmail 4.80 and the install seemed to go well. But once I opened it, none of the menu items or buttons worked.


This is unusual. v4.80 had some bugs, but not any that would cause what you describe. The v4.81 public beta fixed those bugs and is recommended for everyone who has their Home and New mailbox in the same directory. Version 4.81 public beta has been rock solid with the exception of the Home/New mailbox issue which is easily worked around.


That said, did you install 4.80 as an upgrade to 4.71? Version 4.71 required an updated MAPIPM.DLL file which had to be manually put in place. Your installation following the 4.80 failure would not have installed that newer MAPIPM.DLL file. I don't know whether this is the cause of your problem now but getting to v4.81 is my recommendation provided your Home and New are in the same directory.


In your 4.71, go to Help > About Pegasus Mail then click the Info button. Copy the content of the resulting information and paste it into a reply. It does not contain any personal or security details. It contains the paths to Home and New which we'll need in order to advise on 4.81.


[quote="pid:57385, uid:5347"]Tried installing Pmail 4.80 and the install seemed to go well. But once I opened it, none of the menu items or buttons worked.[/quote] This is unusual. v4.80 had some bugs, but not any that would cause what you describe. The v4.81 public beta fixed those bugs and is recommended for everyone who has their Home and New mailbox in the same directory. Version 4.81 public beta has been rock solid with the exception of the Home/New mailbox issue which is easily worked around. That said, did you install 4.80 as an upgrade to 4.71? Version 4.71 required an updated MAPIPM.DLL file which had to be manually put in place. Your installation following the 4.80 failure would not have installed that newer MAPIPM.DLL file. I don't know whether this is the cause of your problem now but getting to v4.81 is my recommendation provided your Home and New are in the same directory. In your 4.71, go to Help > About Pegasus Mail then click the Info button. Copy the content of the resulting information and paste it into a reply. It does not contain any personal or security details. It contains the paths to Home and New which we'll need in order to advise on 4.81.

Many thanks, Brian! Quite a bit to digest and experiment with, and I'll be doing that next.
I'm not sure I understand where to copy the updated MAPIPM.DLL file from, and where to.
Would the copy-to destination be:
C:\pmail\Programs?
The version sitting there for 4.71 at the moment is:
2014-03-26 12:01 PM 317.952 mapipm.dll


Eleanor White


Many thanks, Brian! Quite a bit to digest and experiment with, and I'll be doing that next. I'm not sure I understand where to copy the updated MAPIPM.DLL file from, and where to. Would the copy-to destination be: C:\pmail\Programs? The version sitting there for 4.71 at the moment is: 2014-03-26 12:01 PM 317.952 mapipm.dll Eleanor White
edited Feb 19 at 11:49 pm

The MAPIPM.DLL file required by v4.71 used to be available in the Add-ons section of this forum but is no longer there. I don't know of an alternative download source. IMHO, the v4.81 public beta is your best bet. As I previously mentioned, checking the Home and New mailbox locations is important so that we can help you avoid a problem in the event they are different.


The MAPIPM.DLL file required by v4.71 used to be available in the Add-ons section of this forum but is no longer there. I don't know of an alternative download source. IMHO, the v4.81 public beta is your best bet. As I previously mentioned, checking the Home and New mailbox locations is important so that we can help you avoid a problem in the event they are different.

Just installed Pmail 4.8.1 and thanks, Brian, it does NOT appear to be showing the same error messages.


But if you have a minute, may I ask about a secondary problem?


The reason I started looking to update my Pmail from 4.7.1 was that the COMPOSE option, which reportedly allows the user to set their default typeface SETTINGS, was not shown in 4.7.1.


(The recommendation to use the COMPOSE SETTINGS option came from various google finds.)


In my installation of 4.8.1 here, I don't see a COMPOSE SETTINGS option either. Just the original compose button at top left screen.


Any tips?


Again, many thanks for your help!


Eleanor White


Just installed Pmail 4.8.1 and thanks, Brian, it does NOT appear to be showing the same error messages. But if you have a minute, may I ask about a secondary problem? The reason I started looking to update my Pmail from 4.7.1 was that the COMPOSE option, which reportedly allows the user to set their default typeface SETTINGS, was not shown in 4.7.1. (The recommendation to use the COMPOSE SETTINGS option came from various google finds.) In my installation of 4.8.1 here, I don't see a COMPOSE SETTINGS option either. Just the original compose button at top left screen. Any tips? Again, many thanks for your help! Eleanor White

In my installation of 4.8.1 here, I don't see a COMPOSE SETTINGS option either. Just the original compose button at top left screen.


Their are no "Compose Settings" per se. There ARE ways to set Fonts, both globally (default) and per message:
Globally:


  • Open the Editor window by starting a new message.
  • Access the Font Selector by either clicking on the font button in the main Pegasus Mail window (lower case blue "f") or using the Message pull-down menu and selecting Font...
  • Select your preferred font for use by the message editor window (replies and new messages).

Per message:

  • Use the font button (lower case "f") in the editor window toolbar. This works very much like changing fonts in a document editor like Word. Note: The formatting tools in the editor window are not available if you have enabled the "Disable all text styling options (never send styled mail)" option in Pegasus Mail configuration.

Edit: I forgot to mention the message width and tab settings in Tools > Options > Outgoing mail > Message formatting


[quote="pid:57407, uid:5347"]In my installation of 4.8.1 here, I don't see a COMPOSE SETTINGS option either. Just the original compose button at top left screen.[/quote] Their are no "Compose Settings" per se. There ARE ways to set Fonts, both globally (default) and per message: Globally: - Open the Editor window by starting a new message. - Access the Font Selector by either clicking on the font button in the main Pegasus Mail window (lower case blue "f") or using the Message pull-down menu and selecting Font... - Select your preferred font for use by the message editor window (replies and new messages). Per message: - Use the font button (lower case "f") in the editor window toolbar. This works very much like changing fonts in a document editor like Word. Note: The formatting tools in the editor window are not available if you have enabled the "Disable all text styling options (never send styled mail)" option in Pegasus Mail configuration. Edit: I forgot to mention the message width and tab settings in Tools > Options > Outgoing mail > Message formatting
edited Feb 20 at 7:42 pm

Please see the EDIT below.


Both your global and per-message tips work AOK.


But if you're ready for a "Twilight Zone" issue that popped up 24 hours after the installation of 4.81.1154 public beta, every sent-to-self, copy-to-self, and emails to others replied to ...


... have all been forced to TIMES NEW ROMAN, even though I send them out in Arial.


I've looked through some .INI files, and I can't see Times New Roman mentioned at all. Every font name is set to Arial.


Is this a new feature?


And if so, why did it wait 24 hours to start happening?


Thanks,


Eleanor White


EDIT: Looking around in google, I find that emailers downloading emails look to see if the as-sent font exists on the receiving computer.


If the as-sent font isn't found, a substitute font will be used to display the incoming emails.


That may mean that 4.8.1 public beta can't find Arial font definition on my PC.


However, Arial certainly exists here as it is used in many other pieces of software, and 4.8.1 public beta also found it in the first 24 hours.


Life is full of surprises!


Oh, by the way, Arial does exist, both by searching "fonts" from the PC's Start search, and in c:\Windows\Fonts>:


2019-12-07 04:08 AM 1,036,584 arial.ttf
2019-12-07 04:08 AM 980,756 arialbd.ttf
2019-12-07 04:08 AM 721,144 arialbi.ttf
2019-12-07 04:08 AM 717,428 ariali.ttf
2023-08-17 07:47 AM 175,956 ARIALN.TTF
2023-08-17 07:47 AM 180,740 ARIALNB.TTF
2023-08-17 07:47 AM 180,084 ARIALNBI.TTF
2023-08-17 07:47 AM 181,124 ARIALNI.TTF


Please see the EDIT below. Both your global and per-message tips work AOK. But if you're ready for a "Twilight Zone" issue that popped up 24 hours after the installation of 4.81.1154 public beta, every sent-to-self, copy-to-self, and emails to others replied to ... ... have all been forced to TIMES NEW ROMAN, even though I send them out in Arial. I've looked through some .INI files, and I can't see Times New Roman mentioned at all. Every font name is set to Arial. Is this a new feature? And if so, why did it wait 24 hours to start happening? Thanks, Eleanor White EDIT: Looking around in google, I find that emailers downloading emails look to see if the as-sent font exists on the receiving computer. If the as-sent font isn't found, a substitute font will be used to display the incoming emails. That may mean that 4.8.1 public beta can't find Arial font definition on my PC. However, Arial certainly exists here as it is used in many other pieces of software, and 4.8.1 public beta also found it in the first 24 hours. Life is full of surprises! Oh, by the way, Arial does exist, both by searching "fonts" from the PC's Start search, and in c:\Windows\Fonts>: 2019-12-07 04:08 AM 1,036,584 arial.ttf 2019-12-07 04:08 AM 980,756 arialbd.ttf 2019-12-07 04:08 AM 721,144 arialbi.ttf 2019-12-07 04:08 AM 717,428 ariali.ttf 2023-08-17 07:47 AM 175,956 ARIALN.TTF 2023-08-17 07:47 AM 180,740 ARIALNB.TTF 2023-08-17 07:47 AM 180,084 ARIALNBI.TTF 2023-08-17 07:47 AM 181,124 ARIALNI.TTF
edited Feb 22 at 6:09 pm

I first thought of the default reader window font but that would show up in PMAIL.INI "Font to use in message reader" entry(ies). I did not think to mention it in my previous post, thinking only about the message editor. Perhaps search PMAIL.INI again for "Font to use in message reader".


There is also a default font setting in IE Renderer configuration. Mine is set to (no default font) with a zoom of 100%.


I first thought of the default reader window font but that would show up in PMAIL.INI "Font to use in message reader" entry(ies). I did not think to mention it in my previous post, thinking only about the message editor. Perhaps search PMAIL.INI again for "Font to use in message reader". There is also a default font setting in IE Renderer configuration. Mine is set to (no default font) with a zoom of 100%.

In IERENDERER.INI, I deleted the default font name which was:


Arial Unicode MS


That FIXED the problem of Pmail not being able to "see" Windows font titled just plain ARIAL.


Emails now display in whatever font they were generated in.


But somehow my SMTP settings got messed up and I can't send. I didn't touch anything else.


No help with that requested - I'll have to do some more tinkering.


Thanks for pointing out a fix for the font issue.


Eleanor White


In IERENDERER.INI, I deleted the default font name which was: Arial Unicode MS That FIXED the problem of Pmail not being able to "see" Windows font titled just plain ARIAL. Emails now display in whatever font they were generated in. But somehow my SMTP settings got messed up and I can't send. I didn't touch anything else. No help with that requested - I'll have to do some more tinkering. Thanks for pointing out a fix for the font issue. Eleanor White

In IERENDERER.INI, I deleted the default font name which was:


Arial Unicode MS


There's no need to mess with IERENDERER.INI, IER provides a config dialog where it also shows a drop-down list of available font families. Serif fonts like Times New Roman are typically used by default in browsers (for whatever reason). If setting IER's default font it will be applied to all HTML messages, but at the top of the list you can opt for "no default font" so it will use the HTML message fonts unless there are none defined - which then would come as IE's default serif font.


[quote="pid:57421, uid:5347"]In IERENDERER.INI, I deleted the default font name which was: Arial Unicode MS[/quote] There's no need to mess with IERENDERER.INI, IER provides a config dialog where it also shows a drop-down list of available font families. Serif fonts like Times New Roman are typically used by default in browsers (for whatever reason). If setting IER's default font it will be applied to all HTML messages, but at the top of the list you can opt for "no default font" so it will use the HTML message fonts unless there are none defined - which then would come as IE's default serif font.
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft