My goodness. Such an easy fix for a problem I've been having for a very long time. Several factors have been moving me away from Pegasus and this was one of them. Unfortunately, changing the Windows Default Printer may not be an easy thing to get used to. I'll try it for awhile and see if it works out.

I don't remember when I first experienced the "extremely slow Pegasus" problem but it has been at least two years, and very frustrating to say the least.

Thanks,
Ken Long
Albuquerque, NM - USA 

The file location of your current installation will help determine whether you should do a clean install then transfer file or not. If Pegasus Mail is installed in C:\PMAIL with the mailboxes in C:\PMAIL\MAIL then you can copy the entire contents of C:\PMAIL to the new machine then do an install (upgrade) of Pegasus Mail v4.63 to that same location.  Running the Pegasus Mail installer is required so that the new machine will know Pegasus Mail is there and can be configured as the default mail program.  I have had success doing this in reverse as well.  I do a new install but don't do any configuring then I copy the entire C:\PMAIL folder from the old install overtop of the new install overwriting all files.  Worst case, you delete C:\PMAIL from the new machine and start again.  The important thing here is that the paths MUST be identical on both machines and must not be anywhere inside of the \PROGRAM FILES folder.  Make sure to keep your old install intact until all is well on the new machine.

If you are not sure where Pegasus Mail is installed go to  Help | About Pegasus Mail and click the Info button.  These three lines will tell you where Pegasus Mail is installed and where the mailboxes are.

WINPMAIL.EXE directory;
Home mailbox location:
New mailbox location:

If Pegasus Mail is not currently installed in C:\PMAIL then do a new install on the new machine, configure it including creating users (same as in your old install), then copy message files, folder files, address book files, etc. from the mailbox folders on the old machine to the same mailbox folders on the new machine.  Start with all .cnm files (new mail messages), all .pmm and .pmi files (folders and associated indexes) and all .pmr and .pm! files (addressbooks and indexes).  There is a guide to Pegasus Mail filenames and extensions that can

be valuable in determining any other files to copy.  Find it at:

http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html

There should not be a need to overwrite any files during the copy process as the files in the new mailbox folders are mostly configuration files which you don't want to disturb.

Tip:  Use the configuration screens from the old Pegasus Mail for reference as you configure the new install or use a text editor to open and print the pmail.ini file and any .pnd files to use for reference.  These files are located in the Home or New mailbox folders.

Old posting but still findable and relevant. Link has changed:

Setting up an Office 365 POP email account in Outlook 2010 or 2013:

http://btbusiness.custhelp.com/app/answers/detail/a_id/19539/c/5088/

Setting up an Office 365 POP email account in Outlook 2011-2016 Mac

http://btbusiness.custhelp.com/app/answers/detail/a_id/30981/c/5169/

also:

http://www.he.k-state.edu/support/instructions/pmailo365.html

At the moment this isn't working for me, but hopefully it's a matter of slogging away.

HTH

[quote user="breezes"]This got me thinking, though, about upgrading my own Pegasus.  I see on the download page that v4.63 will run under Windows 2000Pro.  My system is an older one, running W2K at about 1.5GHz.  Will that be sufficient? [/quote]

 It should be.  I have Pegasus Mail running on some minimal WinXP systems without a problem.

[quote user="breezes"]Do I simply install over the top of my current Pegasus (v4.41)?  Will the install program find the existing files to replace properly?  As it is right now, I have the program at C:\Program files\Pegasus mail.  The mail itself is at C:\PMail\Mail.  I think I recall that having Pegasus in Program files presents a problem in v4.64.  Is that correct?[/quote]

Actually, the problem with the \Program Files folder is related to Windows 7.  Win7 protects all files located in the \Pegasus Files folder preventing Pegasus Mail from writing to it's configuration files. 

As for the updater, you can select the folder of your current install and the updater will overwrite the old files with ones from v4.63 without affecting the configuration files. 

At some point you are going to need to get Pegasus Mail out of the \Program Files folder.  Consider doing a clean install then moving data from the existing mailbox(es) to the new install.  There are plenty of threads about how to do that.  Your existing install will remain functional during the transition.

[quote user="breezes"]Is there a step by step procedure set out anywhere for me to follow?  I have lots of mail that I don't want to lose.  Losing some of it would be disastrous.   I don't want to screw this up, so I want to be sure of the procedure before I start an upgrade.[/quote]

The installer takes care of an upgrade so no step by step procedure is needed.   Make a backup copy of both C:\Program files\Pegasus mail and C:\PMail\Mail before you begin.  One of the great things about doing an upgrade is that if something goes wrong you can replace the contents of C:\Program files\Pegasus mail and C:\PMail\Mail with the backup copies and be back to where you started.  I would make a backup even if you do a new install.  You can work from the backup as you transfer data to the new install.  Also, you can use a text editor to view files in the backup mailbox folders for reference as you configure the new install (pmail.ini and the .pnd files for instance).

Distribution lists are stored in the mailbox folder as .pml files.  They can be viewed with a text editor so try this.  Copy the .pml file you wish to work with to a temp location (so as not to mess up the original), open the copy with a text editor, copy all of the entries, paste them into a spreadsheet app, save as a .csv.

You can identify the .pml filename associated with each distribution list by looking at the settings options of the distribution list.

Search results folders that where created while the setting to delete them on exit was disabled must be deleted manually.

If you need to know where this setting is look in Tools | Options | Incoming mail | Folder behaviours.

[quote user="idw"]

[quote user="Euler GERMAN"]As I just said in , I think this is handled exclusively by Pmail's TER/HTS components.[/quote]

Mainly you're right, but the HTML is prepared for TER by LibTidy which access is provided to by BearHtml or IERenderer. But I'm pretty sure that this is in fact mainly a TER/HTS issue since they at least changed the DIV handling between latest versions (in former versions <DIV> was handled like <P>, i.e. created a paragraph, which isn't the proper handling compared to most (or all) browsers). I would like to get some sample HTML, though, if possible (it doesn't need to be a complete message, just the HTML would do).

[/quote]

I see, but the most relevant aspect is on those cases when a message has remote graphics. Also, most of paragraph styling is done using tables which makes HTML message forwarding a mess. I'm not fond of HTML for messaging but it's really a pain when you need to reply to some of them. For message forwarding the most reliable is to forward as attachment and leave it to recipient's email client.

[quote user="Joerg"]

Oh yes, life could be so easy without those weak links  :-)

Unfortunately judgment is always required. We are receiving so many different mails from different senders with more or less attachments. And those attachment have to be saved to different network locations at different servers. Therefore I would have to create too many filter rules.

Presently there is a verbal policy in force where the users are requested to remove attachments from emails directly after saving them on the server. This avoids an inflating of our mailbox drive. But in practice often they forget it or they are lazy, and at the end of the year I have to "clean" all user mail accounts by searching for the "big pieces" of attachments which are aready saved at the server but not removed from the mail account.

The best way for me would be a solution where the users are being automatically asked for an attachment deletion after they have saved an attachment.  ...  I know, it's a dream. ;-)

Hi Joerg!

I think you could try using one of those hot key managers like AutoHotKey, AutoIt3, TinyTask, WinParrot, and so to automate the process. The not so good part of the story is that you may turn your weak links yet weaker. Anyway, using a tool like AutoHotKey or AutoIt will let you control the working environment checking which window, child window, class, etc is active. TinyTask and WinParrot are just "dumb" macro executors, requiring more attention of end user.

 Within Pegasus Mail you could also try Quick Actions. One of the Quick Actions options is "Apply a set of filtering rules to the message". As long as the message is in NewMail folder (as .CNM) it could save and delete attachments. As an example, you could trigger rule by entire file name, only the name, and only the extension.

With the last information I posted fresh in my mind, I just tried running the same command from another work station running XP and it worked just fine.

That's a problem with the rights in NDS. Group BECOME should have full access to the mailboxes of the project accounts. As I remember, group BECOME must be in same context than the users. The users (or/via group) must be able to see the project accounts in NDS. And at least they have to enter loginnames of project accounts as full distiguished names, because they reside in another context now.

bye

Please copy to output of Help, About, Info button display and post so we can see how and where installed and where new mail is located.

Is there any Anti Virus or file checking program running on the system and how is it set up? Does it work as proxy and put itself between Pegasus Mail and connection to mail server and/or the SMTP server? Are you running in standalone mode or are you running winpm-32 from a server install? Pegasus Mail can not read or write data any faster than read/write from drive location so the speed of connection is a limiting factor. Also speed and availability to exchange data with printer driver is factor also and if that is slow to read/write it will slow down mail accordingly. Is defined default  printer local to your machine or across network? 

First install v4.63 by running the distribution archive exe on the new machine and using the default offered c:\pmail location as the destination. You may configure and test.

Then later copy only the desired data files or message or address book file pairs plus any *.cnm files (new mail messages) to the c:\pmail\mail\admin on the new machine install. Leave all other files behind or if using compressed archive from old machine extract only the files needed. Make sure any files copied or moved are not marked R (read only) attribute at OS level and if so remove that attribute on the new machine location,

http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html

is reference to files, names and locations. 

If you need old connection information best  plan is to print out the old .pmd file contents to use for reference in setting via the GUI on the new machine install.

Direct copy of pmail and below from old machine could only succeed *if* old machine install was in c:\pmail location and even that would only get you part way there. You would still need to run the v4.63 installer to set  proper registry entries and other things and mailto protocol etc.. on the new machine.

I'm not sure if this is the same problem but it seems that this explanation from Nick may shed some lights in. The text below is from PM-WIN@LISTSERV.UA.EDU archives.

[quote]Several "gurus" have looked at this several times.

The problem is obvious.

_Arguably_ RFC-correct multi-part messages with more than (from memory)
two levels of nesting and constructed in one of two (or more) legally
possible ways (that is where the arguments will start!  8-) ) are NOT
seen by PMail to have "closed" the "last level" of one of the MIME
level structures, when in fact, it has.  My _guess_ is that PMail then
scans through the rest of the digest looking for what it considers the
"missing" MIME part closure header.  It seems that the  parser is dead-
set that the next "MIME part header thing" it should see is this
"missing" part and thus it _ignores_ all the other MIME component part
start and end headers that exist from the point the PMail parser
errors, thus does not "see" any messages in the digest _after_ the
message in which this parsing error occurs.  As the digest summary
message -- the one that looks something like:

   There are 13 messages totaling 1058 lines in this issue.

   Topics of the day:

     1. smtp relay host
     ...
     6. PMAIL Digest - 4 Jan 2012 to 5 Jan 2012 (#2012-6)

-- is always the first message in the digest and (so far) always
produced in a format that cannot trigger this bug (it is a single-part,
text/plain-only Content-Type message) you can always see the correct
listing and count of the messages that the BAMA digester put into the
digest, but then may only see from 1-N (where N is the number from the
"There are 13 messages ..." sentence in the example above) messages
listed.  If you drop into "raw view" while reading the digest _and_ in
the message list viewer, you can see that all messages promised from
the digest summary are present, but as just described, PMail will not
actually list any of them (nor provide you any other way of seeing
them, other than "raw view") after the first message in the digest that
has this "imagined" MIME non-conformance issue.

In the last 4 or 5 years (maybe longer -- anyone keeping count?) this
has been noticed, replicated, analysed, and described on this list
multiple times, but never addressed in any updates.

It may well NOT be an easy fix, as the MIME component parser is
probably fairly crucial to a _lot_ of PMail internals and changing it
now may produce a whole lot of hurt (if nothing else, the beta testers
will presumably have to re-do a huge amount of message conformance
testing).



Regards,

Nick FitzGerald
[/quote]

Hope it helps. [:)]

Hi all ,

The problem has been fixed when i did an update to the last release of Bearhtml (4.6.9.0) and IERenderer (2.4.7.4.)

I wish to thank all of you for your help and patience... I don't know how could i fix  that problem without your help.

Happy  to be one of Pmail community.

[<:o)]

PS: from now i will also try to help other forum users if i can.

Thank you. Your suggestions - with some advice from a neightbour - have helped me out and I am OK again. But it does remind me that I should take these technical matters more seriously. Delay in reply due to need to get through Christmas and a big birthday before getting down to it again.

Charles

The PMIcal 1.11 opens now all (previously problematic) files.

Thank you.

I moved all the .pmm and .pmi files into the new installation.   Some of the folder names were garbled.  With those and all others I did a right click, index folder.  Then most of the emails showed as unknown so I deleted them.  The copyself.pmm didn't seem corrupted and it looks like all the emails were there after the reindex.  The ones I need for the court case were ok.

Thank you both for your suggestions. It's in the Inbox that she is having the

problem. What I've been having her do in the mean time is moving the

messages she wants to delete into a temporary folder - which she is then

able to delete.

I just discovered that the problem is in

the button on the toolbar. If she uses the delete key, the message

deletes. If she clicks on the delete button on the toolbar (which is her

habit) nothing happens. So it looks like the toolbar is somehow broken.

Is there any easy fix for that?

[quote user="bodhi926"]REALLY? gee maybe thats why i dont have outgoing mail, i have tried their settings and connected to a telnet server on port 25 also,  so i am a bit confused  apparently i am posting in the wrong section from what another user told me, didnt realize there was a difference between pmail and mercury.[/quote]

You've certainly confused me.

If you have a problem with Mercury transfer your post to that section.

• that did it..thanks to everyone....should I have discovered that on my own...?