[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.

Just to say that I have precisely the same setup, and the same minor annoyance applies here too.

David

[quote user="John Whitehead"]

 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.

KSQR

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).

I can't get headers.dll to work since upgrading either; it shows in Extensions Manager but there's no headers in the emails.

Another workaround is to create your custom headers in the Special tab when sending emails.

These will be retained  in the recently-used list, so you have to enter them only once, then just recall them.

You could enter the headers directly into \Pmail\MAIL\<username>\WINPMFUH.PM,

and you could also backup this file - very useful if the custom headers get lost.

There's one major weakness - its not a sticky setting so you have to remember to invoke the Special tab each time.

However I suppose you have to remember to run 4.63 for your newsletters anyway; using stored custom headers seems better.

Gmail messages sent from PMail to an address where the mail host uses Apache Spam Assassin, a grade is included in the message header for:

MALFORMED_FREEMAIL     Bad headers on message from free email service

Anyone else having this experience?

KSQR

[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.

I finally got it working by not using the authenticate with pop3 credentials (which I know work) but putting in the username and password directly.

Thanks for your help.  I really appreciate it.

Thank you for the tip...it IS appreciated

[quote user="KSQR"]

[quote user="caisson"]http://www.vandenbogaerde.net/pegasusmail/p300_idmcodes.html[/quote]

Thanks for the info.

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 

Martin 

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.

If you cannot sort out the SMTP you could try using DavMail if your company has Exchange Web Services running.

Well just doing a new install does work fine.

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. 

Thanks Brian.

[quote user="jonm"]As I said at 5906 characters the line becomes invisible so I find your statement of 16kb doesn't match my reality.[/quote]

Becoming invisible doesn't necessarily mean you can't enter more. I just pasted in more than 6000 characters which made Pegasus Mail throw a (software) exception which didn't crash it, though. And if copying all of it back to my text editor it still contains all of them while I even can type in more (without the line end getting blank) ... But I can duplicate the error message when trying to send a message with such a long line. This might be an internal processing error (truncation for not exceeding buffer size), though, since the editor field seems to accept more characters.

Restarting did not solve the problem. I did a restore point from a from last week which seems to have solved the problem. Reinstalling the software updates which included one of the Visual C++ packs did not seem to break the Message Editor. Perhaps I had some malware keystroke monitor or something that slipped by the firewall and virus scanners. A full virus scan hasn't turned up anything.

Thank you very much...now it works...I used all of the suggestions except disable cram-md5 which I already knew needed to be enabled...thank you so very much

Tools | Internet options | Sending. Select your Verizon definition, then Edit.

Compare whats there with the settings provided to you by Verizon and take into account the info already provided to you through this forum.