Excellent, I've had the same problem for some time, and this fixed it instantly. Thanks!

 
PMail 4.41 on WinXP 

Just note that the scan engine and the client software isn't updated through a corporate signature feed. Only the signatures are fed this way. You need to enable clients to manually run liveupdate in order to get the product updates. This is also the same behavior since version 7.5 up to latest release.

Thank you very much. Your solution worked! Apparently it was the PMX files that were the culpret. Both my wife and I had the this same problem, and deleating those files solved the issue.

Cheers....Vince

Before jumping into this, please read this thread: ; it lays out the issues surrounding translations, and may explain why I do not necessarily approve every translation that is presented to me. I have sent mail privately to Peter about this matter as well, and he will no doubt follow up as he sees fit.

Cheers!

-- David --

[quote user="Henrydog"]

I have found files that are named ADDR13F8 and ADDR49DC that I can read with notepad. They have addresses in them. But when I start Pegasus, I don't have the address books! Suggestions?

[/quote]

Don't use any editor on those files.. They are NOT ascii. Once saved from an ascii editor, they are mangled and lost for Pegasus Mail. The files belong either in the Home Mailbox or in the Pegasus Mail program directory (which makes them systemwide) or in any other location pointed to by the environment variable PMR= (Most likeley you will not have this set).

When you have saved the files from notepad they will probably have the .txt extension added to the filename.

There must be 2 files per addressbook : ADDR13F8.PMR and ADDR13F8.PM! (basename may vary). If one of them is missing or corrupt, Pegasus Mail will fail to read the addressbook.

Ooopps....didn't see other replies and that problem was resolved.[:$]

Dear Mr. Stephenson,

Reading your message I found the way to solve problem with sending e-mails from Pegasus.

I had troble using Pegasus from november 2006.

"After installing latest version of Pegasus mail v 4.41 I can not send
e-mails via SMTP server of my Cable ISP. If I use other e-mail
software I can send e-mail via same SMTP server. With other ISP SMTP
servers sending of e-mails working fine."

I used today http://www.speedguide.net/files/TCPOptimizer.exe and start option
in program to find maximum MTU and used this value, I also checked No for MTU discovery.

I can use Pegasus mail for sending messages even if I use connection of my cable provider and all
programs also work fine now.

Kind regards,
Milan

The situation with translations is very complicated. They involve a great deal of work and co-ordination, and because of this, I am generally very cautious about taking on new languages. Each language has to have its own resource sets, its own list memberships, its own distribution and testing regime; it has to be hurried along when it falls behind, and has to be regularly told about changes and additions. Almost inevitably, I become involved any time there's a question about the intention of a string, phrase or other resource, and I have to consult with all the teams any time I plan a major addition to make sure that there are no issues associated with that.

For a time, I had a "translation co-ordinator", but that approach didn't work out, and for a time the translation process basically died altogether. I ended up resurrecting it myself, something I have very limited resources for. The only formula I found that would work was to have teams led by someone I trust (in almost every case a long-time beta tester) who would co-ordinate the process and involve me only when it was unavoidable.

I've been very lucky that the French, Italian and German translations are led by extremely good and motivated individuals who have involved me to the smallest possible extent. By contrast, I have tried three times to establish Spanish translation teams, and each time they have failed dismally. Other languages typically haven't fared much better. Please note that I am not being critical of the translators in these cases - there was a failure of process, and lack of time and involvement on my part that meant that they could never establish enough impetus to get going properly.

A lot of the problem is that people simply don't understand the enormity of the process, nor the level of technical knowledge required (it's *not* just a case of running Notepad and translating some strings). There are also problems with finding good tools to handle the process - I've now tried several, with mediocre results at best. Most people also fail to appreciate that the effort is ongoing: a translation that only works with a  single version of the program is essentially useless.

I would love to have a good Spanish translation of Pegasus Mail - it would give me the classic "EFIGS" translation set (English, French, Italian, German and Spanish) and would be useful to a great many people. The problem is that I do not have (as far as I know) a Spanish beta tester, nor even a long-time beta tester who is Spanish-speaking, and in the absence of such a person to act as a team leader, past experience makes me very reluctant to approve a team.

The situation with languages/scripts that have non-Western orthography, such as Hebrew or Mandarin, is much more complex. The program dates from a time when these languages simply weren't a consideration, and it simply hasn't ever been designed with them in mind. To handle non-Western orthography you really have to design your application from the ground up to be able to do so, and the changes required for a codebase as long-standing as mine would be very considerable indeed. I am told that Pegasus Mail can be made to work to some extent with some non-Western scripts, but if that is so, then it is largely by accident and definitely not through good design on my part. I lack the resources and language skills necessary to be able to handle these types of language changes and currently do not have an effective plan for dealing with them, other than possibly considering a complete rewrite of the program in .NET, which is not going happen any time soon (it would be at least a year's work, plus the learning curve time adapting to the new technologies).

This message is rather longer than I wanted it to be, but I feel it's important to lay out clearly what the situation is regarding this very important area. If the issue of producing new translations seems slow and unusually obtuse, it is not because I do not appreciate the value or importance of such translations - it's merely a reflection of the limits I face as a solo developer operating on minimal resources. I would love to be able to do better than I currently do, but best intentions alone are not going to do the work. *Sigh*.

Cheers!

-- David --

Doh!

Thank you very much, Han. I missed that whole group of options.

Another senior moment!

Quick update ...  Thanks for all the helpful advice to date.  I backed up the mysterious 4GB folder onto an external hard drive then deleted the original.  I think it must have been a repository for all the deleted junk mail.  No sign on any ill effects on the functioning or contents of any of the existing mail folders and I now have an extra 4GB of space.  I've also now changed the deleted mail box to continue to show what's in it so can now happily clear that when necessary.

Cheers!  Have a good week..

         Philip   [:D]
 

Brilliant.  Thank you.  The state file change worked.

Eric 

I just joined the community and began searching for a solution
to my "lost mailto" problem and found it. Thanks to Dave for
posting the question and to David for the answer.

I have been a Pegasus Mail user since 1994. I found it as an
alternative to Eudora which I hated. 

Thank you David for such a great product.    [:D]
 

If you want to be sure that all your settings etc are backed up, and you have the space on your backup device, I recomend that you backup the Pegasus Mail install folder and all sub-folders (normally c:\pmail).  If you dont have the space, you should backup all the files in the folder given to you by step 1 in David Harris's instructions above:

[quote user="David Harris"]

1: Run Pegasus Mail; choose "About Pegasus Mail" from the "Help" menu

and click the "Info" button. About four or five items down you'll see 

an item called "Home mailbox location". Write this directory name down

somewhere.

[/quote]

Not 100% sure on the Symantec front (Nortons) but it seems that the latest def is working ok now.

Well, the simplest option is to have each of these "archive" mailboxes in their own directories on your hard drive and then use the Folders -> Add Mailbox To List... menu option to mount each of the additional archive mailboxes.  You can then move or copy emails between folders in the different mailboxes.  However, you cannot simply move a folder between mailboxes (hopefully a future version will allow that).

Patrick, thank you for dropping by.

I'm now closing this thread.

Thanks, David and Barius. You finally got through to me. My ini and cfg files had gotten 'addled'. Everything worked fine when I fixed them. I still don't understand how Pegasus found any message files at all before I fixed these things. Some things, I guess, are just not worth pursuing...

Go to your pmail folder and delete every file beginning with LNK (and ending in PNL).  Restart Pegasus and there you have it. 

Thank you very much! Installing Pegasus into the C:\Pmail folder did the

trick.

I am a bit obsessive about wanting to select the location of the programs

that I install; I have a system that lets me keep track of where I will locate

programs that I install. Up until this particular installation, I was always

able to put Pegasus into my system. But this time, I have to bow to the wisdom

of David Harris, I guess!

 You probably know how relieved I am to see Pegasus in flight! [ip] [:D]

I think the request is coming from someone who has used LookOut (Outlook), this 'feature' expires messages at a date/time in the future. Of course this can be overruled, and is not compatable between all the different mail clients let alone ones that actually follow the standard.

With all the legal issues now turning up this is something that may not be in the best interest of anyone.

At the end of the day it is up to the enduser to delete the emails. CYA of electronic documents for the most part can be 'difficult'.

[quote user="dkocmoud"]

I don't understand why the original poster is not interested in using Mercury/32 to download the POP3 mail via Mercury/32's MercuryD module and have it placed into the public folder (once the next version ships, which supports delivering new mail to a public folder). [/quote]

euh... i'm not using Mercury because i'm using a other mailserver at this moment.  I know Mercury only by name... never installed it ...never seen it..
But... you made me curious ... just put my finger on the Mercury manual.... maybe i will install it and play around with it for a while

looking forward to the most intresting part (concerning this thread) ... dropping mail in a publc folder

This thread is closed for me, or resolved.

Most important things are :
Use public folders to share  mailfolders
Prevent that several users have access to a same mailbox at the time
Only share the new mail folder in a "add mailbox to list" option
Be aware that there is a "user training issue" involved

or keep it simple and
Start Pegasus Mail with the "-U <username>" commandline option to force Pegasus Mail to start up as that other user.
 

greetings and txs.