Thank you very much for your help!!

I solved the problem and I can send and receive Pegasus Mail again.

It appeared that the Firewall of Norton Internet Security blocked Pegasus Mail.

Best wishes and thanks again,

Pedro Snoeijer

Hi,

thank you all for your help.

The problem fixed itself with an oldschool Windows-Restart.

Maybe windows held a lost reference to a broken newmail and
SPAMHalter was not able to delete this fragment
after moving a copy to the junkfolder and
retried it all the time?

Bye for now and many thanks to the creators of PM and SH!

jcp

When you make changes to the rquotes.r *source* file, you then have to compile it with the RESCOM.EXE utility, which ships with Pegasus Mail in the Resources subfolder under the Pegasus Mail program directory (usually C:\PMAIL), and then copy the resulting rquotes.rsc resource file to your mailbox directory as an rquotes.pms file.

From the sample rquotes.r file:

##
##   Sample source for a suitable RQUOTES.PMS for use in
##   Pegasus Mail v3.0/WinPmail variable signatures.
##
##   Compile this source using ResCom.exe, by issuing the
##   command "ResCom RQUOTES.R", then copy the resulting
##   RQUOTES.RSC file into your home mailbox as RQUOTES.PMS.
##
##   So, the sequence of commands looks like this:
##
##      C:\PMAIL> rescom rquotes.r
##      C:\PMAIL> copy rquotes.rsc f:\mail\9000001\rquotes.pms
##
##   The general format of this file is a collection of text
##   resources; each text resource is a multiline group of
##   quoted strings, ending with \n wherever you want a line
##   break.
##
##   To activate your variable signature, place the characters
##   ~! in your signature file at the point where you want the
##   substitution to occur.
##

In the example above, F:\mail\9000001\ is presumed to be your mailbox directory (as it would be in a NetWare bindery mode environment).  More likely, it will be something like C:\PMAIL\MAIL\Fred.

See thread:

[quote user="Thomas R. Stephenson"]There is no folder specified here.  If you are trying to get it to query for a folder name then use Tools | Options | Copies to self "If making a copy to self, ask at send time which folder to put it in"  

When this control is checked, Pegasus Mail will ask you to select a folder into which the copy to self should be placed at the time you send the message. When this option is enabled, the Default copy-to-self folder name field is ignored.[/quote]

That did it, Tom.  Thanks.

--peter m.  

Go to the directory containing winpm-32.exe (should be c:\pmail\programs on a new install) and run the program pconfig.exe.  Set the standalone HOME and NEW mail directory spec to c:\pmail\mail\~8 then save and exit.  It should now be pointing to your multiuser installation and when you enter "John" for the user name it should get your old mail.

No, sorry - there's no selective confirmation facility in the program at this stage.

Cheers!

-- David --

[quote user="David Harris"]

To get around that, I would disable message preview automatically after any crash, and the user could select this option to turn it back on:

[/quote]

So the workaround is :

Cause Pegasus to crash then don't push the button, hey presto - no preview [:D] 

Now just need a toolbar button to crash the program ! 

Your .PM! address book index file is corrupted.  Unfortunately we don't have any modern internal tools to repair address books.  There is the old dos-based PMIMPORT.EXE utility that you can extract from the PMAIL/DOS version (v3.5 is available from the download web site).  PMIMPORT can extract the data from the address book, you can then check it and clean up any duplicates, then reimport it into a new address book.  Note that you can use the Tab key in PMIMPORT to bring up a file/directory selector window when in a field that asks for a filename.

[quote user="dkocmoud"]The -Z 1024 commandline option must be used every time, not just once.  [/quote]

Yes, I know. The shortcut I usually use (in fact it's in the start-up folder, so i won't have to do it manually) has this parameter. However, because I saw something that I did not see early on, I dropped it here. The parameter suppresses the symptoms, it is not solving the problem. Maybe someone with more knowledge of the subject finds the info is usefull.

And yes, I know the problem is not a Pegasus-bug. I've reported the bug also by the company whose software I think is tot blame.

However, no hard feelings here. 

The file affected is main.pmm.  Moving it makes no difference. 

Any other ideas about how to break it up or extract the mail?

Thanks

Graeme 

Seeing your mention of the default mailbox installation location made me think ... Does it matter that I always install PMail to c:\Program Files\ ? Also is there a tweak that will allow installation of default mailbox *at the outset* in, say, the Documents folder. Maybe there's something I haven't figured out that's staring me in the face here, but this possibility would make my data back up routine just that bit simpler.
Best regards, Keith

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 --