Interesting.  I have certificate tracking enabled on the smtp side but am pretty certain that I do not have it enable on the pop3 side since I was looking at it last night when I posted my settings.  I plan to look at it again when I get home though.  Glad you got it figured it out.

FWIW, when the certificate changes there is a prompt by Pegasus Mail that calls the change to your attention.  You can then choose whether to accept the new certificate fingerprint.  Luckily, it doesn't happen often enough to be a significant inconvenience.

Greetings All,  I have been experiencing a problem with the Filtering rules for quite a period.  I set up rules, but then they get ignored and I manually have to move messages.  Is there a limit to the number of rules that PM can handle?

 Also, I have noticed recently that I have to initiate a POP3 connection twice to get the OpenSSL to shake hands ( I use Gmail as my ISP).  Is there a fix for this down the road or a patch I am not aware of? Running 4.70 on XP SP3

Thank You - Ralph B.

[quote user="Ralph B."]Greetings All,  I have been experiencing a problem with the Filtering rules for quite a period.  I set up rules, but then they get ignored and I manually have to move messages.  Is there a limit to the number of rules that PM can handle?[/quote]

There is no limit that I am aware of.   What you are describing is a failure of the message to trigger a rule.  There is a technique that I use to troubleshoot rules that involves adding a color.  This helps determine whether the rule is being trigger or the rule action is failing.  If the rule is failing to trigger then you look for a problem with the rule or a problem with the logic in the rule list.  To troubleshoot, identify a rule that is not triggering as expected.  Change its action to a "GoTo Label" action.  Add the label and within it place a change color rule followed by the action you want.  Example is below.  Be sure to include an Always Exit rule before the label and at the end of every label (if you do multiple) to insure processing is stopped appropriately.

rule1
rule2
rule3
rule4 GoTo Label1
rule5
.
.
.
.
Always Exit
:Label1
Always set color
Always perform desired action
Always Exit

[quote user="Ralph B."] Also, I have noticed recently that I have to initiate a POP3 connection twice to get the OpenSSL to shake hands ( I use Gmail as my ISP).  Is there a fix for this down the road or a patch I am not aware of? Running 4.70 on XP SP3[/quote]

Unfortunately I can't help you with this one.

Brian,  Thank you - but that really does not tell me anything that I understand at all.  All I ever had was back in the mid 70's with COBOL.

Perhaps I misunderstand your need.  You indicated that filtering wasn't working and asked whether there is a limit to the number of rules.  This indicated to me that you are doing extensive filtering which you now claim to not understand.  Perhaps it is just the GoTo Label part that you don't understand?  If so, I don't know of another way to troubleshoot rules.  All you can do is to identify the rules that don't work and then figure out why.  It can be either a problem with the rule itself or with the rule sequence logic causing the message to never get processed by the rule.

As for your Gmail problem.  There was a post made to the the Pegasus Mail FAQs section of this site about Gmail and SMTP.  Your problem is with POP3 so this may not pertain to you but it might if you have the "Send mail before receiving mail via POP3" option enabled.  Here is the path to that post:

 http://community.pmail.com/forums/thread/44795.aspx

Greetings All,

I just upgraded to PM 4.71 - I NEVER saw any announcement of the new release!  But the problem of the OpenSSL handshake failure is still continuing with Gmail in POP3 - I have to go in via Selective POP3, and when I get the failure error message

go in through the normal POP3 button/tab.  Then it connects and downloads from the INBOX.  Thank you.

I have just tried TWICE to access my Gmail account - I got TWO sets of handshake errors from PM 4.71 regarding OpenSSL using POP3;  I do not have a problem sending emails just accessing and downloading.  0321UTC February 21 2016.  What is the problem?

Have you turned on internet session logging then review the log after one of these errors?

If the time stamps in the log show a delay between the handshake and the final disconnect then assume a connection problem or a transient error on the Gmail end.  The delay is an indication of Pegasus Mail timing out as a result of no response. 

FWIW, my Gmail POP3 is pretty solid, not perfect but the failures are rare and usually resolved by the next download attempt.

My settings are:

Host : pop.gmail.com
Port : 995
Timeout : 90
Security: Via direct SSL connect
no other options are enabled in the Security tab

Hello Brian,

Thanks for the input - I figured out to turn on the log function. I have a cable modem/Wifi system - so I do not think 90 seconds is necessary.  The log showed that the connection to gmail failed, but the connection to yahoo was a clear success.

When I tried to do my two step method - it worked.  But no log report to tell me what happened or why.

What was the content of the log for the failed connection.

Take care not to post the section containing your username and password. These might be Base64 encoded and therefore easily decoded.

The connection did NOT even get that far.  Would you like the contents via regular email or available to the group?

You can post the log contents here but be sure to remove the username and password credentials content from it first as caisson mentioned.  In a .pop log file they are in clear text (at least mine are which surprises me) but in a .smtp log they are the four entries following the "Auth login" entry.

Brian et al;

Here are both gmail attempts from last night - as you can see they never got even close to connecting with the Google server.

 22:04:50.500: --- 21 Feb 2016, 22:04:50.500 ---
22:04:50.500: Connect to 'pop.gmail.com', timeout 90 seconds.
22:06:22.562: [!] OpenSSL timed out during handshake.

 22:06:26.593: --- 21 Feb 2016, 22:06:26.593 ---
22:06:26.593: Connect to 'pop.gmail.com', timeout 90 seconds.
22:07:29.468: [!] OpenSSL reported errors during handshake - error queue follows:
22:07:29.468: [!] -------------------------------------------------------------------------
22:07:29.468: [!] -------------------------------------------------------------------------

  Thanks for any clues as to the problem.

The first attempt appears to be a connection problem preventing contact with the Gmail server

The second attempt contains "OpenSSL reported errors during handshake - error queue follows:" which is known to be associated with incompatible versions of SSL between Pegasus Mail and the server it is contacting. 

If your smtp is working but pop3 is not then I suspect there is something different between the two configurations.  On the General tab the host name and port should be different but look at the SSL/TLS settings in the Security tab to see if anything is different there.

You might also try this:  Go to the Security tab of the POP3 host configuration for your

Gmail and location the setting called "Only use SSLv3...".  If it is

enabled, disable it then test.  If it is disabled, enable it then test. 

Check the log of each test for any additional clues.

Hello Brian and everyone;

I figured out the glitch - gmail wants the fingerprint certificate turned on.  I checked that control and then the systems shook hands immediately and the .pop file was 320k plus.

Is there a way that the fingerprint certificate can be configured to be updated "automatically" as connections are made?

PS. The control for SSLv3 was not a factor - but thanks for the thought.  

In the Gmail configuration material for OTHER clients they do not mention the certificate - but let me check one or more of the other configs.

 THANK YOU VERY MUCH!!!   Ralph B.