I have noticed this behaviour too: select more messages, command to move or delete them, click anywhere else on a message ... HEY!! That other message was moved/deleted instead and the operation stopped! [:S]

This was not a problem in previous versions. Seems to me such operations were strictly sequential and Pegasus did not respond before it was completed. It might take ages to retrieve a big message over a slow line, but at least it did what it should. Maybe now this comes as a result of paralelizing; perhaps the operation does not get a list of messages at its launch time but instead every time one message is processed it asks "give me more"? Doesn't matter, this is way too much annoying, and it happens even on a gigabit line next to the server when you are too fast!

My advice is to move back to <4.7 and wait until this gets resolved despite any good new features 4.7 has (e.g. that significant speedup). I'm using Pegasus since maybe 1994 and I like it, yet I cannot use this new version.

When I select a message to move or delete it in the inbox, press move/delete/whatever, and then proceed to select another message too quickly, Pegasus accidentally performs the required operation on the newly selected message. Using 4.7.

Verson 4.7 is slower in some actions than were previous versions.  This is especially apparent during sending and POP3 checks for new mail.  It is worse for some folks than for others.  The issue is known and being worked on.  My advise is to give v4.7 a chance to complete each operation before attempting to do anything else.