[quote user="jpiquette"]

Brian,

I am running v. 4,72572. It may be that the later version includes the updated DLL's. And actually, verizon no longer offers email service. But when they dropped it, they transferred all the accounts to AOL, allowing those who moved over to retain their verizon addresses. It is quite possible AOL changed something, but they made no announcement.

 Jean

[/quote]

I supposed it would be 4.71 or 4.72. Version 4.73 introduce the most stable OpenSSL libraries, those I sent you. Maybe you should consider update to 4.73 that have many other improvements and a security fix.

For the past 24 hours I have been seeing the subject error message upon attempts to check the host for new mail. Any help with this would be appreciated.

Jean 

A web search for "malloc" produces numerous references to it as a C library function having to do with memory allocation.  I don't know if that is relevant here but a cold boot of the PC is worth a try if you haven't done one.

Thanks for the reply. Unfortunately, I have done a reboot with no difference resulting.

It doesn't look like a Pegasus Mail error message. Methinks it could be an OpenSSL error probably due to a wrong setting in the POP (or IMAP) Internet options. I'd start looking if the right port and/or proper SSL/TLS settings complies with server's.

I have checked the port setting and the SSL settings. According to the provider, they are correct. Also, this has worked fine for years, and only started having the problem yesterday. I guess it's possible the provider changed things but has not updated their user information. It is hard getting through to them now with what is going on with the covid situation though.

 I will try to find to if they made any changes.

 Jean 

Maybe a session log can shed lights on the matter.

How do I produce a session log?

[quote user="jpiquette"]How do I produce a session log?[/quote]

Session logs are activated when you check Create Internet session logs (advanced diagnostic use only), bottommost of Tools > Internet options... General of your desired/running Identity. Once checked, all traffic between Pegasus Mail and your mail server will be registered in a session log.

These logs will be saved into the TCPLogs folder under that of your mailbox. Logs will be named TCP-######-####-#.pop, or TCP-######-####-#.imap, or TCP-######-####-#.smtp depending of the protocol used.

Please take care to obfuscate parts of the session logs that contains your login and password before you publish them. Pay attention to these lines below:

[quote]12:31:33.878: << USER @@@@@@@@@@@@@<cr><lf>
12:31:34.104: >> +OK send PASS<cr><lf>
12:31:34.104: << PASS @@@@@@@@@@@@@@@@@@@@<cr><lf>[/quote]

where the "@" char replaces those of login and password. Note that despite either of them may be encoded (Base64 mostly) it is very easily decoded to the actual text string.

The logs all seem to only include the error message that is the subject of this thread. But I may be looking at the wrong log(s). None of the TCP logs I examined included any information about my login.Only the time and date and an error report are given. Error report is essentially the subject of the thread. Here is a copy of what is included in one of these logs (all of which appear to be identical):

 11:18:19.532: --- 1 May 2020, 11:18:19.532 ---

11:18:19.532: Connect to 'pop.verizon.net', timeout 180 seconds.

11:18:20.737: [!] OpenSSL reported errors during handshake - error queue follows:

11:18:20.737: [!] -------------------------------------------------------------------------

11:18:20.737: [!] error:1411B041:SSL routines:SSL3_GET_NEW_SESSION_TICKET:malloc failure

11:18:20.737: [!] -------------------------------------------------------------------------

[quote user="jpiquette"]

The logs all seem to only include the error message that is the subject of this thread. But I may be looking at the wrong log(s). None of the TCP logs I examined included any information about my login.Only the time and date and an error report are given. Error report is essentially the subject of the thread. Here is a copy of what is included in one of these logs (all of which appear to be identical):

 11:18:19.532: --- 1 May 2020, 11:18:19.532 ---

11:18:19.532: Connect to 'pop.verizon.net', timeout 180 seconds.

11:18:20.737: [!] OpenSSL reported errors during handshake - error queue follows:

11:18:20.737: [!] -------------------------------------------------------------------------

11:18:20.737: [!] error:1411B041:SSL routines:SSL3_GET_NEW_SESSION_TICKET:malloc failure

11:18:20.737: [!] -------------------------------------------------------------------------

[/quote]

Yes indeed. But as I supect it is an OpenSSL error. I'm using OpenSSL version 1.0.2.14 and it works fine. You can check their two files (DLL) in the \Programs directory. Look for libeay32.dll and ssleay32.dll. I remember these files were updated because that in the installation package was producing errors under certain circumstances. I can send you my files if they are not available for download download from the Community site.

Those DLL's both have 2015 dates on  them, so it is likely they are out of date. Could not find a download for them in the community. And although I did find downloads online, I am not confident in the reliability of the sites. I would appreciate if you would make your updated versions available.

Get the file PmailSSL.zip from the link below. It'll last for the next 5 days. Drop its contents into \Pmail\Programs directory. Hope it doesn't get quarantined by the moderation.

http://www.fileconvoy.com/dfl.php?id=g1e64e1a5f806545710002474576c3f77a9444cd27f

Hope it works for you. I won't be available until tomorrow night. HTH.

That fixed it. Thank you so much! I have marked your post as the answer. Is there some other way I can credit you? 

 Also, do you have any idea why this worked for years, then just suddenly had this problem 2 days ago?

Jean,

What version of Pegasus Mail are you running?  I ask because I have these SLL files in my v4.73 and don't remember manually updating them.  I am now curious whether they are included in v4.73 or whether I have forgotten that I updated them.

As for why the problem just started, I suspect Verizon made a change that required a more recent version of SSL.

Brian,

I am running v. 4,72572. It may be that the later version includes the updated DLL's. And actually, verizon no longer offers email service. But when they dropped it, they transferred all the accounts to AOL, allowing those who moved over to retain their verizon addresses. It is quite possible AOL changed something, but they made no announcement.

 Jean

[quote user="jpiquette"]

That fixed it. Thank you so much! I have marked your post as the answer. Is there some other way I can credit you? 

 Also, do you have any idea why this worked for years, then just suddenly had this problem 2 days ago?

[/quote]

Glad it sorted out fine. HTH.