Yes.

If they're in the new mail folder you would use a new mail filtering rule > rules applied when folder is opened.  All unread messages will be run through the filter each time the new mail folder is opened.   Note that only unread message are filtered so you may have to mark them as unread.  You can mark all as unread using Ctrl + A followed by Ctrl + U.

If they are in a folder you would use a general rule set and attach it to the folder as a folder-open or folder-close filter set.  The attach option is in the context menu when your right-click on a folder name. The read/unread status is irrelevant in this scenario.

If you haven't worked with filters before consider testing the filter using a "Set message colour" action.  This provide visual verification of the messages detected by the filter.  If all is well you can then change the action to Move or Delete.

Brian,

GOT IT WORKING! 

The "operator issue" was that after setting up the rule, not hitting the Save & Close buttons.

First pass got message to change color.. Second pass got the "sending address" to receive the "out on vacation" message.

Whewww... Case closed.

THANKS AGAIN for staying with me on this.

Steve

PS: Now to disable until we really leave town. 

Good Morning Brian:

Your simple and elegant solution works like a charm.

Thank you for the suggestion, it is appreciated.

All The Best

Tom G, Sr.

Apparently the Yahoo staff don't know about it though, as they literally said it's impossible without me giving them my phone number. :P 

Hi

I solved it. Problem was in file  PMAIL.INI

There was

Application window rectangle              = -32000 -32000 160 39

in old backuped file was

Application window rectangle              = -8 -8 1936 1056

But I do not know how it happened

Thank you

[quote user="Brian Fluet"]

I suspect the problem message is in the New Mail folder and is marked as unread.  

When you use 'on open' New Mail filtering rules every unread message gets processed through that rule set each time the New Mail folder is opened.  

[/quote]

Yup, that message is indeed in my New Mail folder and was unread, so I deleted it and I'll see if that fixes the problem.

THANKS!!!!!!

It still begs the question why they would refuse a message with ASCII content. I would be very interested to understand why they block this. The pessimist in me suspects it is a knee-jerk reaction.

I really appreciate all the time and attention you've given over the last 3 months (!!!) trying to drag me into a place to fix my screwed up mail. The reformat seems to have lost all the existing info or else it is hopelessly lost to me. Life is too short, I uninstalled the entire Pegasus program and hope this will remove all the fragments existing all over my HDD.

 Thanks again and I hate to be a quitter but my sanity seems more important. [:$]

There is a whitepaper in the downloads section of this sight called "Pegasus Mail files to copy to a new system guide".  This is the direct URL

 http://community.pmail.com/files/folders/whitepapers/entry41852.aspx

It was written specifically to provide to help copying data from an existing install to a clean install on a new PC.  Pegasus Mail v4.63 is the version on which it is based.  Versions 4.7x introduced some additional files but the guide remains relevant. 

There should not be any overwrites during the process.

There will likely be files from the old install that won't be in the new install, especially if the old install has been through a number of upgrades.  If in doubt, ask first before copying a file. 

You should recreate any configurations that can be easily recreated, like the POP3 and SMTP host files.

The PMAIL.INI file from the old install can be used as a reference when configuring the new install.  Don't copy it to the new install though.

Good luck.

What was 'copies'?

You need to give us more information:

What was the name of the old folder and how many messages were in it?
When you copied the contents of the old folder into the new folder, did the new folder then contain the same number of messages?

Did you try IDW's method before attempting to copy the messages into a new folder?

Just so you know, a Pegasus Mail folder comprises two files. The name is the same for each, but the extension is different. The file filename.pmm  contains the mail data. The file filename.pmi is an index of the contents of the .pmm file. When you open a .pmm file, it reads the index and displays the subject of each message. Opening/viewing a message is achieved by referring to the .pmi and know where the message is in the .pmm

When you right-click a folder and choose Properties, the filename (.pmm) is displayed.

Finally, did you create a backup as instructed? 

See Downloads section: http://community.pmail.com/files/folders/pegadd/entry50335.aspx  Only really needed for Windows 10 users who do NOT have Microsoft Office/Outlook installed.

[quote user="Reed_D"]E.g., if I see "su*Order" does the "su*" possibly signify the word being in the subject?[/quote]

Without knowing more details about Spamhalter I'm pretty sure that su* and fr* signify subject and from headers.

HI:

We have jst updated from 4.72 to 4.73 and started to find the same radom error message in almost all the PCs. it seem it happend in a idle time, when the program has been running but no in use during a while

Best regards

Angel

This is a new one to me so are a few thoughts... 

Has the PC been rebooted (cold boot) since the upgrade was done?

Are you able to browse directories with the system file explorer?

Might the attachment file browser be hanging due to an external drive or mapped drive that is not accessible?

Open a copy of the PMAIL.INI and do a search for all instances of "Favourite directory" to see if the path associated with each one is valid.

Hi Brian,

       I have done several re-boots, it makes no difference.  I am running Windows 10.0.17134.  I running off a solid state hard drive with a conventional hard drice (d:0 for my data etc.

DT-C.

I thought it would be best for me to note that the latest IERenderer versions ( now v2.6.1 )  have been handling the emails properly.

Thank you Michael and Martin.

I see this occasionally on Windows 7 as well. The same error message is shown, and the settings are hosed. It used to regularly happen to one account, but I have seen it on several. Completely random and have never been able to determine the cause.

[quote user="Euler GERMAN"]

My filetype.pm control file has two PDF related entries in the following order:

Adobe-PDF,0,X,0,.PDF
Adobe-PDF,S,0,\037PDF\045
 

It seems to me it uses preferentially the "Attachment type" rather than extension to choose which application to call.[/quote]

Thank you. I've added these two to my filetype.pm 

[quote user="Euler GERMAN"]

Strangely, my mime-map.pm file has only a single line "Text/HTML = HTML-text" (no quotes). I'm assuming it has little or no-effect on how Pmail handles attachments. BTW, this is the same file I have under my \Programs\RESOURCE directory.

Anyway, I remember of recipients complaining about attachments sent by me were found corrupt after being processed by Pmail. This happened a long time ago and I don't remember which measures taken corrected the problem. My guess is that telling Pmail to behave by the "Attachment type" instead of file extension is a good guess. As an example, I remember plain-text attachments being added to the message body instead of attached as a file. I used a trick (can't remember who whispered it to me) to make Pmail treat plain-text as binary by adding the line below to filetype.pm:

[code];Text,0,X,0,.TXT
binary,0,R,0,\\032,R,0,\\013\\010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,0,o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L,R,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
[/code]

Notice that the original "Text" is commented.

Lastly, anyone can get a copy of my current filtype.pm control file for the next 7 days. I'm not saying it is perfect, but it plays well here without hiccups AFAIK.

[/quote]

I've added this too.

I'll start sending PDFs again by right clicking the file to send to Pegasus and see if I get any more complaints of not being able to read PDF attachments.

So far it looks good. Pegasus is now saying that my attachment is a PDF, unlike before. However it still wants to use encoding. I'll let Pegasus do that for now.

NICE! 

Thank you Martin!