Try unchecking the option to preserve deleted emails - Tools | Options | Basic settings.

[quote user="Bill@VT"]I have work-arounds, but wondered if all of you are interested in this potential problem and would want me to forward the e-mails (redirect them) for you to look at?[/quote]

 Sure, please do as advised in my previous replies.

Oh dear.  Please send me a copy of the entire email, so it can be reviewed for structure and syntax. The easiest way to do this is to open the message then click the Forward button, and enter my email address (irelam@telus.net). In the Forwarding method,  click the button that states "Forward the message without editing".  Then click the Forward button at the bottom of the screen.

Martin 

[quote user="KSQR"]

When I activated SpamHalter I ran into a major problem, namely a 250KB file attached to a message got trimmed to under 10KB  Got the file by having the sender resend it and using web mail to retrieve it.  Also noticed that my mail filter to move files with ***SPAM*** prepended to Subject to a separate folder also moved some messages without the ***SPAM*** prefix.

    POP3 serverside filtering rules (if any)
    Global whitelist (if any)

[/quote]

After rerunning the PM install file (v4,70), the problem went away.  :-)

After many years of using PM, I finally edited my global whitelist file, white.pm.  To make editing easier. started by sorting.  The file went from over 500 entries to 383.

KSQR

The only additional suggestion I have is to play around with deletion settings in your Gmail profile in Pmail, i.e. delete immediately etc, to see if that solves the problem.

Thanks Michael ... but the problem is resolved.

The guy with our central IT who installed the new  certificates on central mailhost went to a conference ... and forgot to enable a nightly reboot of our mailhost. His colleague didn't know about and said, there are no problems at all. I tested with Outlook and Thunderbird and they didn't have any problems. Than I wrote this message to the forum thinking Pegasus was the problem.

The problem was not Pegasus ... it was the not rebootet mailhost. It holds around 40.000 IMAP-Sessions and some of them (which haven't died in iterim) did have the old certificate, the others the new one. So depending on the IMAP-prozess answering on Pegasus requsts, Pegasus got the old or the new certificate. Because we enabled fingerprint tracking, everytime when certificate changed randomly Pegasus asked if it should refresh. Didn't recognize this.

Pegasus handles SHA-2 certificates correctly.

Sorry for hastily writing the message!

    Olaf

Brian,

Many thanks for your advice. Your third suggestion did the trick. There was a rogue (very large) .CNM causing the freeze.

I'm using Pmail 4.7 under Windows-XP.

Ron Hulme. 

Bingo!

Thank you again! 

You may also wish to consider running Pegasus Mail from the server hosting the mail data. That way you have just one installation of Pegasus Mail to administer. After the installation has been configured and tested you simply create a shortcut to \\servername\share\winpm-32.exe on each person's desktop.

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.