Thank you for alerting me to the -ROAM command line which I was able to get to open a user account on my Windows 7 Pro machine. The version of the Pegasus Mail I have been using on XP is 4.41 from 2006. I have just read that Windows 7 was not released until 2009 - so it is probably no wonder that the program crashed shortly after giving this alert for any folder that I tried to open : "The folder ----- is damaged and cannot be opened. Please right-click the folder and use the Reindex folder option to repair it, then try opening it again."

 I think I should start a fresh thread asking about my best upgrade route from XP. My XP machine is still working and I need to move to Win 7/using BOTH very carefully. I have only been using a test account so far - but phrases like "re-index" really scare me with the possibility of data corruption. I don't want to lose 18 years' worth of correspondence.

Thanks guys,  That worked with deleting the .pmi files and reindexing. The folder size was way under 2GB  I also created another new sent mail folder and achieved the trouble one.

Almost lost faith in Pmail but the forum comes through. Been using Pmail since late 90's as the start date in that folder was 1998.  My first company I had all the employees using Pmail and we never got viruses like people who used outlook and other mail programs back then.  

Awesome and Thanks for helping me out. Now off to IMAP  it to Gmail.  

[quote user="FJR"]

Did you run MBXMAINT on closed Pegasus?

What's the size of  FOLD4179.PMM? If greater or near 2GB, you have to split as IDW adviced you.

Delete (on closed Pegasus) the FOLD4179.PMI (Indexfile), open Pegasus, click the Folder and be patient ... it will take a while reindexing 64000 mails. :-(

If it functional again create folders as archive and split you sent-folder by moving mails there. I've created a archive-folders-hierarchie by year.

bye    Olaf

Thank you Bfluet, that's exactly what I was looking for.

"caisson,"

You are so RIGHT about many another having the same issue. They all seem to think it may have to do with their email client or AT&T which is not the case. It is an internal server error from Yahoo! that is having issues with matching their email addy and the password which to me means it is not connecting to the correct server to find the password that goes with the email addy. I have had this issue since about 2010 and have talked with AT&T even elevating to Tier 2 and they are CLUELESS!

 I have three (3) email accounts and at one time or another they each have been rejected for POP3ing my incoming mail, it has NOTHING to do with outgoing mail only the inbound. If they would just wait about 10 to 20 seconds and check mail again they will get a different server and download their mail. That is what I have been doing and not any problem just a short delay.

 When I managed to get hold of Yahoo! to see what could be done, they told me it was AT&T's problem, WRONG, my email client tells me it is a server at Yahoo! as a matter of fact here are the servers that are doing this to us:

 pop219.sbc.mail.gq1.yahoo.com, pop336.sbc.mail.gq1.yahoo.com, pop334.sbc.mail.gq1.yahoo.com, pop333.sbc.mail.gq1.yahoo.com

If any one can get this information to Yahoo! maybe we can have some results.

thanks, danke

[quote user="weamish"]Suppose there are 10 messages in a particular folder and I want to open all of them in the browser at the same time - is there some way to accomplish this, maybe a macro of some sort?[/quote]

No, and it would be a rather complex task to implement something like this since there's already enough trouble involved for even preparing just a single (HTML part of a) message properly for display, let alone several ones at once.

Thanks, but unfortunately operamail does not allow moving messages between accounts. It stores all the messages in a database and shows them by account by using a filter. A clever and efficient way, sure, but with severe limitations: you cannot drag a message anywhere.

The only possibilities I am left with are 1) convert message to a format the PM understands (mbs to mbx, but the converter I tried is too slow)  2) use an intermediate client that understands .mbs and allows export to .mbx. I am not aware of such a free alternative. The Bat! can do that (at least he import, most likely also the export) but it is a commercial client I am using on two PCs, this one I use when I am travelling. Perhaps once I am back I can try opening a fictitious account in The Bat!, import operamail messages, export them as mbx and then import them in PM. I won't be able to try before September, though.

Thank you.

The list arrived in the DList, with the addresses separated by a comma and a space. I then manually changed them to a hard return.

Ideally, your spam filter product should be detecting these types of messages but you asked about filter rules so if you are experienced with rules then you need to be looking for either a logic error or an error in the rule itself.  To determine which, place your problem rule as the first rule in the list and temporarily change the action to a "set message color" action.  This keeps a message available for testing while providing a visual indicator whether the rule worked.  If it works you know you had a logic issue within the list of rules.  If it doesn't work you know the problem is with the rule itself.  Remember that read message are not filtered so if you have messages already in your new mail folder that you want to filter you need to make sure they are marked as unread.

If you are not familiar with rules, here is a primer...

If you wish to delete messages that contain specific From: header

content the best thing to do is to open the Raw view of one of those

messages and copy the entire From: header line.  Then, in the New mail

filtering rules > Rule applied when folder is opened, create an

Expression rule and paste the From: header line in as the expression. 

Expression rules have wildcard capabilities (see the Help file for more

info) but using the copy/paste approach insures that you delete only the

messages containing that specific From: header.  If you wish to

experiment with wildcards I suggest temporarily changing the action to a

"Set message colour" action.  This will allow you to identify which

messages are being detected by the rule to insure your wildcards are not

going to cause the deletion of valid messages.

Another rule type

is the Header rules.  This is valuable for detecting content in headers

but is less specific in its detections (again, read the Help file for

info).  Examples of Header filter rules would be:

If Subject contains "viagra" Delete
If Subject contains "male enhancement" Delete

Care

must be used when using Header rules.  Such rules would delete every

message that contains "viagra" or "male enhancement" anywhere in the

Subject: header.  You would not receive that message from your wife

containing the subject "Hurry home!  Don't forget to pick up more Viagra". <G>

HTH

[quote user="Henrik Rosenø"]I just realized I can avoid the "lazy HTML" by reducing the image-files to about 1/10 using Fotosizer to convert them from PNG to JPG... Issue solved! :-) [/quote]

Congratulations ;-)!

Hi Donald,

on closed Pegasus put the folderfiles into the directory that holdes your mailbox. You're shure you converted them? There should be files with extension PMM (and possibly PMI - but the Indexfiles would be created by Pegasus if missing). You now you could have copied the files with Thunderbirds folders to same place and add / change the fileextension to mbx? Pegasus is capable reading them You should copy the mails in there  to newly created Pegasus folders.

There are some converters for addressbooks but I did it via MS Excel and tab seperated files.

Filters should be created in Pegasus. I don't know about any converter.

bye   Olaf

HI:

Trying to switch from Mozilla Thunderbird 24.40 to PMAIL 4.70:

My Email folders for PMAIL I converted from Thunderbird MBox format are here:
C:\Users\DonB\AppData\Roaming\Pegasus Mail\PMAIL Folders

1. Wherein PMAIL 4.70 do I point to these folders
2. ADDRESS BOOK Convert from Thunderbird; what format does PMAIL use?
3. Inbox Content Sorting Filters.From Mozilla..How to import to PMAIL use?

 Thanks, Donald Bock

Hi, thanks very much for your reply.

My install was to the default install path not under Program Files (64-bit) or Program Files x86 (32-bit). 

Turns out, I decided to uninstall and remove the folder and files I'd copied over before installing over top.  Then (and this was the key), I was able to do a clean install of PM.

Eureka! Of course, it was very easy to reconfigure my mail settings and test.

After, I copied back my mail and config settings from my old laptop and now everything is wonderful again.

Really, like this product! 

TCPView should enable you to see whats happening:

Is that IMAP profile the last in your profilelist?

In that case try to change the order  of the profiles (edit IMAP.PM on closed Pegasus). If on start of Pegasus the now last profile shows same problem, it seems to be a limitation of Pegasus (which I never read about).

bye    Olaf

[quote user="Jemima"]Yes, there was a dialogue asking for giving details of the encountered trouble, it began: „Pegasus Mail's system information couldn't be attached due to the actual crash conditions. Please open Pegasus Mail's 'Help' menu, select 'About Pegasus Mail...' and press the 'Info' button ...“  I was not able to open the attachment.[/quote]

You cannot open the attachment from the dialog, but only after restarting PM when it prompts you for an "auto-saved" message which you need to complete (I'll think about offering direkt access to that file from this dialog).

[quote user="Jemima"]I followed the instructions and have now sent the mail containing all requested information to the given mail address and have had the automated answer mail. I understand there will be no personal response to my message.[/quote]

You'll get a personal reply from me (but not necessarily from David Harris) once I take a look at the info you supplied, and it might even contain more details as far as I can provide without having access to the source code.

[quote user="Jemima"]However how will I (and others of whom I know they have the same problem) learn of a solution to the described hitch? I assume it will probably only be the case when version 5.0 is released and we will discover that spell check does (hopefully) work faultlessly?[/quote]

It's very likely there will be a version 4.71 not too far from now. Whether the official announcement will refer to your particular issue depends on the impact it has and it's relevance compared to other issues.

[quote user="Jemima"]If anything comes to mind which would involve to delve deeper into the workings of Pegasus and could be executed by the user in version 4.7[/quote]

If we need further assistance or can figure out a workaround you'll certainly get notified about it one way or another.

[quote user="irelam"]Please add a line Wantcss=no  in Bearhtml.ini which should stop this stuff from appearing.[/quote]

I added wantcss=no to the file, and then noticed it was there twice - I guess it was there all along.  I removed the duplicate and changed the remaining to wantcss=yes which stopped it from appearing.

Thanks

[quote user="PhilipAL"]Okay, I have twice managed to cause Pegasus to terminate abnormally this morning. I have assumed that the MiniDump process is always running, but it appears not to have caught anything.[/quote]

It might be required to use MiniDump's "stand-alone" mode where it monitors Pegasus Mail as a child process (see MiniDump's ReadMe for details).

[quote user="PhilipAL"]The trick to cause Pegasus to terminate abnormally is to wait a couple of seconds between selecting "End check" and "Cancel".[/quote]

Since it's apparently reproducable I should be able to create a dump myself or David Harris can recreate it from within his VC debugger.

[quote user="PhilipAL"]It's up to you whether you deem it worthwhile to pursue this problem.[/quote]

It's up to David Harris ...

[quote user="idw"]

[quote user="netware5"]David, I will appreciate if you provide some information about the OpenSSL library used in v.4.70 and probably when the fix will be issued if needed.[/quote]

The fix is already there, it's currently being tested for release. According to David Harris it's especially urgent for Mercury users, but not so for Pegasus Mail users.

[/quote]

Thank you very much for the information provided. As usual David is doing perfect job! Thank you David!

[quote user="LincolnF"]This problem seems to have gone away now, even with standard Pmail settings.  Telecom / Yahoo must have attended to the source of the 'Internal server error (6530)'[/quote]

So finally they did their job like they should have done to begin with ...[8o|]