At the moment, I can (i) use PMail in combination with Zonealarm, but then WinApps do not update, or (ii) use Windows Firewall, which allows WinApps update, but Pmail can't get through (this is the apps in Win 8.1 desktop, not Windows update itself, which is fine)

In Windows Firewall, I've added Pegasus Mail to Allowed Applications. Is there something else I need to alter/add? 

Thanks for the support .The solution was found on the other thread.

I have not received a copy of a bad message yet.  Have you given up?

Martin

Thanks for the reply caisson. 

No it's a POP server.  Most email gets classified correctly and Pegasus hadn't been touched for about a year. The problem has only been noticed in the last few weeks.

I have updated to 4.7  but the behaviour is the same.

Spanhalter has been (still is as this is just an irritation) amazing for me - accurate and easy to use. 

PDF viewing broke for me fairly recently with the type unknown error.

I checked the Content Viewer and PDF wasn't listed. So I added it and even though Pegasus still says type unknown, clicking on open now works as it used to.

Cheers. 

[quote user="Zagra2350"]Are you suggesting 4.70 cannot be installed in

E:\PMAIL? Because that is where I have been running 4.70 (via upgrades)

since 4.70 arrived. Drive 'C' on my machines is only used for the OS.

Other logical drives are for APPS, DATA, Downloads, Office, Utilities,

Photos, etc. This has been my practice whenever I build a new PC[/quote]

Not at all. An installation to E:\PMAIL is perfectly fine.  What is important to understand is that if you want to move any mailbox directory from one machine to another it must be moved to the exact same path with the understanding that on a Win7 or newer OS it can not reside anywhere inside of \PROGRAM FILES.

[quote user="Zagra2350"]At

the moment 4.70 is working OK in the directory E:\PMAIL except that it

cannot 'see' the saved mail folders that were copied back from the saved

location. PMAIL.INI has the correct paths to E:\PMAIL\MAIL.[/quote]

There are other files that contain paths.  Also, there is a file named PMAIL.CFG located in the excutable directory that tells Pegasus Mail where to look for the mailbox directory(ies).  You can view its content with a text editor but it is one of the few files that you can not manually edit.  It gets modified using PCONFIG.EXE.

[quote user="Zagra2350"]I have never previously had any problems of this nature when transferring PM (with data) to a new build PC.[/quote]

It still can be problem free provided the conditions are as described above (exact same path and not in \PROGRAM FILES).  Here are the steps I suggest following if both the mailbox directories

and the executables are inside of E:\PMAIL and you wish to move them to

E:\PMAIL on a new machine.  1) Duplicate E:\PMAIL on the new machine; 

2) Run winpm-32.exe once including specifying a user if needed (get it

fully started up with a mailbox opened);  3) Shut it down;  4) Run the

installer over top (upgrade) in order to create registry entries and

shortcuts.  It should now be ready to go.

Note 1: The purpose for

running winpm-32.exe once is that it creates registry entries that will

tell the installer the path to the last run winpm-32.exe and its

mailboxes.  You may remember the days when Pegasus Mail did not make

registry entries.  Those days are gone. 

Pegasus Mail on the new machine can work fine without running the

installer but some functionality will be lost (specifying it as default

mail program to the OS for example).

[quote user="Zagra2350"]NOTE: The saved ADMIN files have not yet been copied over. The ADMIN folder contains only the new install files.[/quote]

I am confused by this statement.  Your first statement says that the saved mail folders were copied back from the saved location.   If you did a new install then copied back other mailbox directories, the new install may have no knowledge that those other mailboxes (Pegasus Mail users) exist.  That information is stored in the \MAIL\PMAIL.USR file which you would also have needed to copy over provided your old installation contained an /ADMIN mailbox.  Even if you did, I am not sure this will work if the new install is a single user install.  You might need to convert it to multi-user.

Caisson, I think I understand your concern better now; I'm sorry if I misinterpreted your intent.  Please note that I reported a fairly minimal, if not the minimal, set of steps to reproduce the problem, rather than what I was actually doing when the problem first occurred.  It would indeed be more logical for the user to first create the POP3 settings for a new identity, then use those setting when specifying the username and password for the SMTP settings.  I believe that the problem would still occur in that scenario.  (I've uninstalled the software, so I can't test it right now, but it should be easy for other people to do, now that the bug has been confirmed.)  However, in reporting the bug, I wanted to use the fewest possible steps, in order to make it easier to locate the problem in the code.

Go to Tools | Internet Options | Sending (SMTP) | Edit | Security

That's the Security tab.  At the bottom of that box you'll see the  "Do not use CRAM-MD5 authentication even if it is advertised." Check that box.  

Yes, this was solved last week -- no thanks to Verizon. (See http://community.pmail.com/forums/thread/41822.aspx). But Brian has it right.

that did it...thanks a bunch

[quote user="lafiete"]I am totally lost. Do I need to know all the file extensions.

All I want to do is have the new Pegasus use the old Pegasus database.

Is there no way to do something like a copy of the old location data and 

paste it into the new default mailbox location.[/quote]

Unfortunately not.  Pegasus Mail stores configuration files in the same directory  as the mail data.  These configuration files are not useful to different instances of Pegasus Mail except under very limited circumstances.  They will cause problems otherwise. 

As mentioned previously, the white paper located at http://community.pmail.com/forums/thread/41693.aspx is a guide for accomplishing exactly what you need.

[quote user="caisson"]Peg Folders might help:

 http://www.lexacorp.com.pg/lexacorp_utilities.html

[/quote]Thanks, PegFolders is a handy utility. I put it in my ...\Mail\Admin\ folder and also added MsgCount.

"caisson,"

 That did do the trick and removed those pesky permanently saved queued message with nothing entered on any line.  Do not know how that could have occurred, the date stamp was from yesterday, 8/9/2014.

Thank you very muchly . . .

Indeed it does!

Common causes for socket timeout errors are inadequate timeout settings and packet fragmentation.  A search of this forum for "socket timeout" will produce numerous discussions on the subject.

For a place to start check out this post from the developer of Pegasus Mail:  http://community.pmail.com/forums/post/926.aspx

Since PM 4.7 and with preview-mode I sometimes have a mailentry in the folder, which is greyed and has a dashed line. Those entries are always entries of mails, I have moved before to another folder. Meanwhile I have selected another folder and the entry appears, if I select again that folder formerly holding the mail. Sometimes the dashed entry disappears, if I choose another folder and then reselect that folder - but not always:

Just clicking the mailfolder for updating it never lets disappear the dashed mail. Up to now this only happended with IMAP-folders - but my use of local folders is very low.

bye    Olaf

[quote user="Carpediem"]I did a side-by-side comparison on this and determined that up to about 100 messages your method above is much much quicker.[/quote]

OK ... your test tells us, that the difference is not that folders are on IMAP or local -  there are obviously different routines for copy/move involved with drag&drop and using the icon. May be David could use the same, quicker routine for both (perhaps saving program-code :-).

[quote]I said you were a genius for a reason Olaf, you're a genius! :)[/quote]

Thanks ... but I'm for shure not! [:$]

I'm simply a very long time Pegasus user and IT admin with meanwhile thousands of university employees passing by. One offered service for users in my faculty is to migrate mailboxes on or to the central mailservices of the university. Doing that one time after a nice party till sunrise I had ... hmmm ... small problems on a high-resolution pc/monitor to hit the intended target folder with drag&drop. [H] So I simply used CTRL+A, hit the move-icon and navigated to the target folder with cursorkeys. OK - I wasn't that tired to not recognize the difference in speed moving the mails. That's all - no genius far and wide - only a Pegasus user in luck. [:D]

cheers *hicks*      Olaf

Thanks, Stan. I looked: it's a little beyond me and I don't think it addresses the issue I'm having. I've got the fonts looking good, it's only the size of the fonts in the address book that are stuck.

 BTW: if anyone is seeing blurry fonts on a high-res screen: right-click on the Pegasus icon - open properties - open compatibility - check "disable display scaling on high DPI settings. Makes the text crips.

 Mark 

Thanks for the reference to the other thread with the solution.

I see he posted about 2 hours after I did.  I decided to give the forum some time before checking back and missed the immediate answer.

Hi there,

  Firstly to point out that the filename reported by Pegasus Mail (the Dot) is not done when you double click the attachment entry. PMIcal does not get involved until the user causes the attachment to be associated with an application, and then the application can be invoked with the extracted file.  This is identical to the Mail filter rules where an application can get triggered by a rule firing, and the *.CNM file path details are passed as a parameter (%s).  

   The problem is that a user on the Pegasus Mail Attachments list page will select a part they are interested in and then click Open. It is silent (failed Open). If they click Save they get a Save dialog and can Save As anything they want. But how do they determine what the content of the file is?  Well they can do a  Raw View, and wade through all the Mime parts and then do a selective copy of the vCalendar content, invoke Notpad and save it. Then in Windows Explorer, find the just-created file and double-click it (if the file association with PMIcal is present) and wake up PMIcal.  Way too much.

So I am doing a review of the various processes involved in PMIcal and may well re-design the workflow 

I hope this starts to clarify the problems, generated by Microsoft mainly, are causing me.   P.S The same problems, to a lesser extent, occur with vCard streams from exporting Microsoft and Apple Contacts. 

 Martin