First thing to try is to move all *.cnm files out of your mailbox directory (.cnm files are messages in your New Mail folder, one per message).  Test Pegasus Mail.  If no crash then you need to isolate the problem .cnm file (if the crash still occurs, skip the rest of the paragraph).  First look for any with 0 byte size.  If you find any, there is a pretty good chance they are causing the problem so move the others back into the mailbox directory and test.  If you still crash then move them all back out and move a small number back at a time testing between batches until the crash occurs.  Now work with that batch to isolate the problem file.  This is a trial and error process which can be tedious if you keep a lot of message in the new mail folder.  It will be easier to isolate a problem file if you empty the new mail folder between batches by moving the messages to a different Pegasus Mail folder after each successful test.

If moving of the .cnm files did not resolve the crash problem then look at the date stamp of a file named HIERARCH.PM located in the mailbox directory and see if it was last modified around the time that problem started occurring.  If so, it is possible that the HIERARCH.PM file has become corrupted.  Fixing this requires restoring from a backup (which in your case would need to be from before the problem started occurring) or rebuilding the HIERARCH.PM file.  In either case the first step is to get the existing copy out of the way.  With Pegasus Mail closed, rename the existing HIERARCH.PM file to something like HIERARCH_PM.BAD. 

Restore HIERARCH.PM from a backup if you are so

lucky as to have one from before the problem started occurring.  If that is not an option, Pegasus Mail will rebuild the HIERARCH.PM file automatically the next time it starts.  Be advised that a rebuild of the HIERARCH file will result in the loss of any filing tray structure you had in your folder list.  All folders in the Pegasus Mail folder list will be at the root level. 

If you do not know where your mailbox directory is located, open Pegasus Mail and click the Info button located in the Help > About Pegasus Mail... screen.  Look for the "Home mailbox location" entry. 

Also, in the Announcement and FAQS section of this forum is a post titled "How to deal with crashes and hangs/freezes" which you might find useful.

Thanks for the reply.

MouseKeys works quite nicely.  Not as fast as I would like (even with it set to maximum speed) so, for me, it is about a push between grabbing the mouse and using MouseKeys.  Unless the mouse is far away (I have three screens arranged horizontally, so if I have pmail in the right hand monitor and the mouse is at the top left corner of the left hand monitor that is quite a distance to cover) in which case grabbing the mouse will always be quicker.

 On those bad days, though, when control of the mouse is elusive, MouseKeys is a wonderful alternative.

 Not as nice as just hitting ENTER when the attachment type is already highlighted, though!

 Thanks again

mike

Peter,

Perhaps we should continue this conversation offline - my email address is irelam@telus.net    The Mapi.dialog flag is only to access the proprietary Microsoft MSExchange and the Outlook client interface, for things such as the Mail folders and address books. To use this would require the writing of a whole email client. The best you could do is to write a POP3/IMAP4 client to fetch email from a server. Address books are in all cases proprietary/copyrite protected so accessing them programatically is next to impossible. MsExchange is a database application based on MS Sql, and needs database programming techniques.

The non-Microsoft MAPI dlls, including mine, are only intended to be used by file sending functions such as Send_To in Windows Explorer 

Perhaps you could indicate to me what you are trying to achieve, in an offline conversation, and I may be able to offer some suggestions. 

Cheers

     Martin 

Hmm ... how did you convert the files?

The folderfiles of Netscape have MBX-Format. You should simply copy that files (not the msf - only the folderfiles with no extension) somewhere else, rename the files, so that they have the extension ".mbx" and point Pegasus to that folder. That's all. Pegasus should show you a list of folders and you may move the mails in to folders in Pegasus-format.

bye    Olaf

Delete a user would not delete the public folder so now you just have to find it.  When you created it you would have specified a path to the directory where the public folder was to reside.  The public folder itself is a directory named with a .mai extension (eg: SAMRA.MAI) that contains message files with .cnr extensions.  If you don't remember the path you can search for either the *.mai directory or *.cnr files.

[quote user="RS11"]

I want to leave mail on the server, but when I retrieve new mail it download everything every time is there a setting

to download just new mail?

Thanks 

[/quote]

Check the block in Download controls section when you Edit pop3 , Tools, Internet options receiving. You have to burrow down to that tab which is several clicks into the settings under Internet Options.

I just signed up to this forum to share my experience just in case it helps anyone.  I enabled 'Content Control' (via 'Tools', 'Spam and Content Controls', 'Content Controls') and the next time I started Pegasus it froze at the splash screen on 'opening new mail folder' (or similar).

I tried many time but it just wouldn't get past this point.  Following the advice given in other posts in this thread I moved all the .CNM files to a temporary folder.  Pegasus then started okay and I was able to disable the Content Control definition. I quit Pegasus, moved the .CNM files back, and opened Pegasus again. All was well, and loaded correctly.

I should add that I'm a long-time Pegasus user (since 1998) and I'm also guilty of having several thousand emails in my New Mail Folder.  I wouldn't do that at work, but...

Thanks once I found the right one on the back up drive and copied it across, it worked a treat.

Cheers

Graeme

I found the offending file and deleted it and am back in business. Sorry for the intrusion.

Thanks everybody. Jim's guidance worked like a charm.

This problem solved totally to my satisfaction. I still think the item should be made more explicit, and be in the help files; it is SUCH a useful tool.

I'll be bringing a much more serious problem to these pages later .... Brian

The (probably postfix) smtp server you are sending mail through is having intermittent problems talking to it's auth db (probably load related - either under-resourced or being dos'ed).

So it's not your (or pmail's) issue, and there is nothing you can do (except change providers or badger them to solve it).

Gah!

I've just pasted the message into Word and the link does in fact contain two @ symbols. The message is encoded as base 64 so the raw view is meaningless.

Sorry! 

Thanks

IIRC in XP it's C:\Documents and Settings\user\SendTo

Locate the created files in Windows Explorer. Rename the filetypes to CNM.  Copy these newly renamed files into your NewMail directory. To find the NewMail directory, inside your Pegasus Mail click on Help. Then click the "About..."  menu item, and then the "Info" button.

HTH

Martin 

Thanks - that was it - hidden behind main screen.

Became visible after I reduced the size of the panel Now the new dialogue box appears on top as previously.

B

There probably were angle bracket but the content that was provided with the failed delivery messages sent to postmaster only showed From: firstname,lastname@domain.com. 

This user has come back into the office so I have since discovered that the failures were on messages that she was trying to forward.  The hotmail address was in the cc list.  She doesn't remember whether she was bouncing or forwarding with edits but says messages sent directly to the hotmail address go fine.  That's all I need to know.  No need to dig into this any further at this time.

Big chance your address book has been hijacked, in which case you might have a trojan on board.

I seem to have fixed this by removing all the .cnm files out of my mailbox then putting them back

Consider SNOWY the server and SATCHEL the client.  Make no changes to SNOWY, just run pconfig on SATCHEL to point to the mailboxes on SNOWY.   Test the path to the \MAIL directory on SNOWY from SATCHEL using Windows Explorer to confirm you are using a valid path in pconfig.  Make sure you have full control permission to \MAIL (including subfolders) from SATCHEL.

Alternatively, there is no need to run the Pegasus Mail installed on SATCHEL because you can share the installation that is on SNOWY.  A shortcut to winpm-32.exe on SNOWY from SATCHEL is how you do it. 

A few additional points:

1)  You don't need your wife to exit Pegasus Mail when you want to use it.  Pegasus Mail can handle being run by multiple users.  It is the act of accessing the same mailbox simultaneously by multiple users that must be avoided.

2)  There is an executable in the Pegasus Mail executables folder named wssetup.exe (stands for WorkStationSetup).  Running this makes the registry entries and other system changes needed for a PC to run a Pegasus Mail installation that resides on another machine.  You won't need to do this because you have already had Pegasus Mail installed on SATCHEL but this is important for anyone else considering doing this.

3)  Be very careful when opening pmail.cfg with an editor.  It is one of the few configuration files in Pegasus Mail that can be easily broken by manual editing.  An inadvertant extra space or space deletion is all it takes.