A continual problem. The Mime part headers say it is iso-8859-1 charset. The actual html message says it is utf-8. It is actually iso-8859-1 that has been quoted-printable encoded. The sender needs to change the default charset of their client to utf-8
I need a bit of guidance and help regarding the following situation.
Recently I installed a new computer running vista and installed the v.61 version of Pegasus.
I was able to move all my folders from the prior version running under WinXP sp3.
I modified the pcconfig.exe file with the Home and New filepath for the mailboxes but now when I launch Pegasus I receive the following error messages:
[/quote]
Something doesn't look right. Recheck your paths and proper spelling. Pegasus Mail never uses Program Files for anything by default.
Sample:
WINPMAIL.EXE directory: C:\PMAIL\Programs Home mailbox location: C:\PMAIL\MAIL\admin New mailbox location: C:\PMAIL\MAIL\admin
In older versions and installs winpm-32 and program files might have been located in c:\pmail but all new clean installs use c:\pmail\programs location. All current version installs are multi user mode ones even if only one user.
The default username is where you want to copy your old messages folders and data to on new system and install if admin is where default user was located before. Did you run installer as update or was it new clean install to new machine. Also, however you restore files make sure backup or cdrom did not mark any c:\pmail and below files with R attribute (read only) and if so remove that manually as winpmail can't work with R files.
New mail folder corruption and other problems occur once the new mail folder reaches in the 700-800 message range. This has been a know problem in previous versions and appears to remain so in v4.61. The solution is indeed to keep the new mail folder trim. Many folks use the Main folder as the working folder but I struggle with that myself. I prefer to use the new mail folder which means I must routinely clean it out by deleting messages or moving them to other folders.
One other thought, had upgraded my software firewall and this caused problems with Pegasus and large files downloaded even via browser or ftp. Found it was due to the fragmentation of the packets during inspection? Reverted to old version of the firewall and no problem, will go through all the settings to see what is different between the old/new versions.
For one user with two identities: So what's your meaning of "There is a way to attach a one Users mailbox to another Users folder list."? How to achieve my need base on attache other users mailbox to the mail user's folder and use each folder as a individual mailbox, can retrive and send mail through it?
[/quote]
I don't believe Pegasus Mail will do what you want to do. Attaching a Users mailbox to another Users folder list allow you to view mail and folders in the attached mailbox but does not allow you to send mail from that mail box nor does it allow you to retrieve new mail for of the attached mailbox unless you have a mail server retrieving mail for all users.
I assume mail is being retrieved via POP3 (if it isn't, let us know how) so the best suggestion I have is to run multiple instance of Pegasus Mail, one as each of the users. Check the "Command line options' section of the help file for specifics on the -I switch which specifies the User Pegasus starts up as and the -MS switch which allows multiple instances of Pegasus Mail to run simultaneously. I have never done this but it seems like the best workaround for what you need.
NOTE: You SHOULD NOT access the same mailbox from multiples instances at
the same time so you would not be able to have any mailboxes attached in
To answer your second question, the name "default identity" cannot be changed (as far as I know).
You can, however, change the command line that runs Pegasus so that it starts up with one of your custom, named identities. See the help file page about command line options.
Now it is all clear. If I had seen the March 2011 note on http://pmail.com/newsflash.htm I would have just disabled the IERenderer but then I probably never would have known a later working version of it was available and perhaps the discussion which ensued from my original post will be helpful for others seeking to understand what caused the problem and how to fix it.
As to releasing the IERenderer prior to the final version of IE9 being available, I would have probably done exactly the same thing in these circumstances (it worked with IE's release candidate) as I would think what are the odds Microsoft are going to change something that I rely on in my program at this late stage. I think Michael should get a vote of thanks for his work developing the IERenderer and for his time spent discussing it on this board.
James Quigley suggested the IERenderer should have been an optional install, but since Bear is no longer maintained and since the IERenderer can be disabled anyway from the toolbar I am not sure that is necessary. However, some kind of warning at the end of the install that the IERenderer may not be the final version due to the release of IE9 and, in case of problems or crashes on machines with IE9 installed, instructions on how to disable it temporarily from the Pegasus toolbar and a link to where to look for the latest IERenderer would have been very helpful.
However my guess would be we are the early adopters of IE9. I only ever applied Vista’s critical updates to my machine and when first I tried to download IE9 I couldn’t as my machine was not up to date enough to run it. That (plus I had a little extra time on my hands) gave me the incentive to download and install SP1 and SP2 then try again for IE9. Probably lots of others like me but maybe can’t be bothered bringing their machines up to date so never will get IE9 and therefore never will have this problem.
Michael, the link you posted to Bear http://www.pbear.com/htmlviewers.html probably no longer contains the information it originally did. It now seems to be descriptions of Delphi components they have developed for HTML display.