I went to the DAWN site - the latest download there doesn't mention Windows 7 - let alone 64 bit setups. So - back to my basic question: I have a large set of "contacts" in my Yahoo.com account that I wish to import into Pegasus V 4.52. Will DAWN really work for me?
Why not? Win7 and 64 bit have nothing to do with this.
Consider the reply option selected for how long line from the original message are to be handled. If Reformat or Wrap are selected the result will then be manipulated to conform to the message width setting you have configured for message formatting. That width probably won't match the original message which can result in odd line wrapping or line breaks. Sometimes the solution is a simple as cancelling that reply and trying it again using a different setting for the long line handling. Sometimes manual manipulation is the only option.
That doesn't answer your question about why it's not automatically handled. Perhaps its not possible considering the varied formatting that messages arrive in and the user options provide users with the means of automating the process as much as possible.
First of all I wouild create a session log of the whole transaction. Go to MercurE configuration and fill in the directory and check the session log box. (Don't forget to turn it off later as they can get quite large.
With the complete detail, you will be able to see what's happening with these connections.
Is the option "Use system-defined colours in Pegasus Mail's controls" of any help? You find it at "Tools" | "Options" | "General setting" | "Basic settings". She may try it and see whether checking or unchecking it matters.
You gentlemen are working with a local copy of pmail, with local mail folders and a local inbox. The standby issue will never bite you because your files are *local*, they are always "there."
"Help" files on Microsoft windows are (de-facto, for me at least) more harm than good because I can't read the stuff because of their choice of fonts and sizes.
[A] The fonts are too small (even with the "large" option) and the choice of fonts is approximately impossible for me to read. The leters merge together on the screen. It's an eyesight thing.
I have tried using a magnifying glass, which isolates words and letters to start with, and then I find myself trying to deduce which pixels go with which letters. After all that, I try to form a word; it's a lot like Captain Midnight's secret decoder rings.
Anyway, thanks a lot for your help. I can now read my messages on my screen. Pegasus looks like a very good E-mail client.
Ok, step two might be a problem in either state.pmj or hierarch.pm:
Try the following procedure. This works to restore the functionality of the message folders or to recover from a system crash:
1. Use Help | About Pegasus Mail | Info to determine your mail directory. Exit Pegasus mail.
2. Rename the file HIERARCH.PM in your HOME mail directory to HIERARCH.SAV.
3. Run WinPMail. Your HIERARCH.PM will be re-created and should start working correctly.
Be advised that this may delete any tree structure you have created and may have to be recreated.
If it still doesn't open, do the above for state.pmj as well.
[/quote]
Hi there.
I have been having this problem with a handful of users over the past few weeks and just wanted to let you know that the above solution resolved the issue for me.
I guess I found out: regardless of the setting in the options it seems that WHEN you search, the marking of "Delete search results on exit" in the search window is critical. Without marking this the individuel search result still remain after PM exit. Otherwise not.
[quote]I don't however, understand why you have to fill out the address in
each and every message since you should have done so in the initial
dialogue box.[/quote]
I've only seen this procedure once when someone else was doing it. So I was incorrect about that - you do only need to enter the address once.
Re Spamhalter. I think for the time being I'd prefer to use just the one anti-spam mechanism (Mail Foundry). I guess spamhalter would still miss some messages that had been missed by Mail Foundry. The number coming through at present are manageable by multiple-forwarding. If things get a lot worse I'll consider adding spamhalter, but I would probably be complaining about Mail Foundry before then.
Got to the directory containing the progam and run pconfig.exe. Reset the HOME and new mail directory spec to the correct drive letter and it should worlk.
apart from wanting to see my name and message on this forum, I wanted to say thanks and congratulations to David Harris for making such a great program (fast, light, and lots of useful finetuning possibilities) and for providing it for free! Early year's message on pmail site on halting development at first gave me a 'this world ain't getting any better..' -feeling, but hopefully he has found the funds, and fresh motivation to keep on trucking.
Thomas, I know that the entry is correct, I have used this for some of
my software. I am a Product Manager for a couple of software products
and have seen this with one of them. I never thought about it in
relation to this problem. I'm sure that you are running 4.51 also. My
setup is basically the same. Do you have the same parameters in both
machines, or only on the workstation? I have not studied the effects
other than doing it on the workstation that I am running PMail on, not
the "server". What settings did you do on which machine? I am also
using Popfile and ClamAV for Mercury on the server side.
I'm running the oplocks on the workstation only here and I've just disabled the oplocks. Checkout for my settings. Everything works normally for me with disabled. I did get a real slowdown when I moved to SP3 on the server and stayed at SP2 on the workstation but that went away when it went to SP3.
I'm also running the Netware Client 32 since I'm also connecting to a Novell v3.2 system via bindery but I'm not all that sure this means anything in the scheme of things.
Thank you for your solution--the problem is solved.
Actually, I had plugged an Epson PictureMate in one time and Vista had used its own drivers and set it up as the default printer. This also explains why the HP kept starting up with a page size of 4 x 6. . . Setting the HP as the default printer solved the problem. Thanks again!
There is nothing mystical about 2Gb limit. It is the maximum positive number that can be held in a 32 bit integer. Until you migrate to Windows Vista 64 bit operating system the limit is a hardware architectural limit.
I saw a similar behaviour in the past for most of my folders, and I still do for a few of them.
Until some weeks ago, compressing my folders took me a long a time (at least, it seemed to me a long time because compressing even a relatively small folder could take 40 seconds or more). Then, I had to buy a new harddrive, re-install Windows and all programs, and moving a data files to the new harddrive. Having finished that, I saw that compressing a Pegasus Mail folder was much faster than before; the new harddrive seems to accelerate almost all disk-related activities - not surprising against the background of the fact that my old harddrive was eight years old and the "new" one is one year old.
Now, I still have some folders for which compressing takes longer than for other ones. Those folders have two things in common: compressing takes longer than for other folders, and displaying the message list takes longer when grouped views are chosen for that folder. However, I do not know yet what causes the difference between the "slow" and the "fast" folders.
So all I can do is to ask two questions: (a) Is your harddrive old? (A new harddrive might be faster for folder compressing and other disk access.) (b) Do the folders that need much time for compressing use grouped views? If so, does listing the messages in grouped views take much time in those folders?
At this point there really isn't a way of doing this, sorry. You can get a lot of it going using filtering rules (rules on the new mail folder that move all messages into the IMAP folder, and by attaching a filtering rule set to the IMAP inbox), but you can't do away with the local mailbox altogether. Realistically, this is unlikely to become an option in future, either.
As far as I know, the only "pure" IMAP client out there is Mulberry, which may (if I understand correctly) no longer be a supported product. Pure IMAP is difficult for a great many reasons, and demand is not that great (the impetus for this type of mail being largely towards webmail these days).