I guess it's possible that at some point I did a bulk unread of the folder and only noticed the discrepancy when looking for recent posts as they now appeared at the end of the folder
Thank you very much, Martin! I do not know where they all hid themselves, but using the Tiles feature unhid them. Now all is right with the world again . [8-|] [Y] .
[quote user="caisson"]You would (should) have been asked to specify a location during the reinstall[/quote]The reinstall did ask for a relocation of the program, but did not ask me to re-specify a location for /MAIL/[Users]. It continued to use all my user files on the C: drive. Perhaps I failed to delete those and do a registry clean-up. My bad.
[quote user="caisson"]Also there is a command line switch (-ROAM) that can be used for removable drives that tells Pmail to ignore the drive letter. Useful if the drive does not always show up with the same drive letter.[/quote]This is good info to know. However, my external drive is always the same letter. I just believe that Pegasus should have an encrypted password system - it's just too easy to "crack", should someone get hold of your external drive.
However, my wife now has a macular sight problem and needs larger (and clear) print. The address book is quite impossible, together with using folders.
We realise that in the main window we can choose the font and have done so but this doesn't seem to apply to Address Book etc.
[/quote]
Also have macular problems. Have found that I can do most PMail activities easily when I changed to a 27" monitor set to 1280 x 720 pixels. When needed I use the Virtual Magnifying Glass: http://magnifier.sourceforge.net/ So far it is the easiest one to use that I have found.
I should have written something back in Oct 2014...
Pegasus Mail with the distributed OpenSSL binaries is vulnerable to the POODLE attack -- in theory, in practice no.
While other protocols (e.g., HTTPS) are more likely to be exploited by an active man-in-the-middle to downgrade connections to SSLv3, that is a near impossibility with email protocols (i.e., POP3S, SMTPS, IMAPS). In a web setting, the SSLv3 weakness can be exploited by a MITM attacker who repeatedly re-crafts client requests to the server. On average this effort requires 256 requests per byte of data.
One may "drop-in" updated OpenSSL binaries in-place of those distributed with Pegasus Mail. However since Pegasus does not employ the TLS_FALLBACK_SCSV mechanism, an attacker can still force a protocol "downgrade dance".
If one has a need to absolutely disable the SSLv3 protocol, I've compiled "openssl-1.0.2d-no-ssl23-win32-static-x86" which has no SSLv2 or SSLv3 support.
(The file "openssl-1.0.2d-no-ssl23-win32-static-x86-tests.txt" shows SSLv2 and SSLv3 as unsupported, TLSv1, TLSv1.1, and TLSv1.2 as supported cipher-suites).
[quote user="DigiDog"]Or maybe this Windows weirdness will forever remain a mystery. In any event, many thanks for your help IDW. You've just made my day better.[/quote]
You're welcome. I'm sure it's an issue with the Registry entries for browsers. Since updates continuously mess with the Registry (worst of all IMO Acrobat which always set's it's reader as default without asking for permission) it could be caused by any browser update.
In the following portion of the page, 3: did not work for me. Others?
"When you create a toolbar.pm file there are some additional codes you can use: 0: A standard 22x20 pixel bitmapped button 1: An 8-pixel separator gap 2: A combobox control 3: A separator line"
[/quote]
It works if done correctly. The following is an example line using the Train Spam ID:
0,10263,0,1831,"Train Spam"
1831 is an icon taken at random from the PNG folder in Pmail.
Note that you have to add 10000 to the control id (263)
Further to my previous posting, the latest version of Virscan has a separate option in Virscan.ini, called Enczip= which can have two values Deny (which is default) or Skip
As caisson says, messages only get moved out of the new mail folder by some sort of filtering rule. Those can exist in autofiltering, Spamhalter, Content Control, and rules created via Tools | Mail filtering rules. These rules are stored in the winrules.pmc file mentioned by caisson. The contents of this file can be viewed with a text editor. As for Content Control, make sure its Basic Spam Detection set is disabled.
Both the server and the client machines installs of Pegasus Mail should be accessing the same home mailbox directory when signing in as the same user so both should display the lock warning. The fact that the client doesn't is of concern. Trust us when we recommend not accessing the same mailbox directory simultaneously. If you do, keep backups handy.
I get the impression that when you began this endeavor you where trying to figure out your options and understand how things worked. That is commendable but now that you have played with it I recommend the same as has SaliesBuzz. In instances where there is a server and a client(s), the best option is to run the server install of Pegasus Mail from the client.