Barrylev, I had the same problem - a setup which was working properly just stopped. I received a message from gmail saying that I tried to use an insecure app. I was quite ill at the time so just reverted to using the gmail webmail app.

I found the latest version of Pmail and loaded it and followed all the steps to make the link with gmail, but still no dice. I then received another message from gmail saying that someone had tried to login to my email account using an insecure non-google app. It also advised that I could allow this connection by altering the security setting in my google account to allow connection to less secure apps. I'm not sure if this is google being incredibly fastidious re security, but I have a sneaking suspicion they might be trying to squeeze out third parties - they even mention MS Outlook as a possible insecure app.

 Anyway, I enabled the less secure access and all seemed to fly. Hope this is OK for you and that the lowered security doesn't cause problems.

 I too would be keen to learn if there's any other way around google's block.

Since Thursday, attempts to log in to my AOL email account with Pegasus have timed out with the subject error. Same username and password have worked in the past, and the same username and password work fine when directly logging in on the AOL website. Is this a Pegasus issue or an AOL issue?

Jean 

Check the AOL-Webpages if they have changed anything on how to access their mailserver via POP3 / IMAP and SMTP. Many mailproviders in the near past disable older securityprotocols like SSL3/TLS1.0. May be you have to change protocol (StartTLS instead SSL) and/or the ports for accessing.

bye   Olaf

Thanks for the reply. It's  strange, but after checking the required settings, and finding all seemed to be fine, I finally decided to try the security settings, about which nothing is discussed in the information given other than to show a checked checkbox labelled "This server requires an encrypted connection (SSL)" under the directions for setting up Outlook. Under Pegasus' Security tab I had selected "Via direct SSL". For grins, I changed that to "Never." That gave me a different error message along the lines of "an error occurred when logging in." So I changed  back to "Via direct SSL", and Pegasus was able to log in! But then about 10 minutes later, the subject error message appeared again. I went into offline mode. Waited a while then exited offline mode. And Pegasus was again able to log in! Perhaps they are fiddling with their software. This behavior is baffling. 

How are you reading your mails? IMAP or POP3?

When does the erroro occure: on reading/getting mails or on sending?

In the options "Loading Windows internet Services (Winsock32.dll)" is set to always?

Bye    Olaf

POP3. I honestly think AOL was fiddling with their software. Since my last post Pegasus has been logging in just fine. I may be home free at this point. I will say though I am surprised no other AOL users reported the issue here. I can't be the only one who experienced this.

Jean 

Apparently AOL has recently changed their logon to require the full name, e.g., "username@verizon.net"; not just "username".   There is sometimes a glitch on the aliases, but I think that if the alias works on webmail, it should work on POP (or IMAP).  I think February-2018 is when I started seeing this.

I presume this is a requirement for SMTP, but I'm not in a hurry to fix it for those sub-accounts.   My most important account (okay, somewhere in the top 3) is the one that Spamgourmet points to.

Yeah. I had noticed that and changed it but still got the same error. Then mysteriously at some point I was able to log in. Lately the SMTP has shown some strange behavior too. First attempt to send email fails. But eventually it does get sent. Very strange,

Jean

While I use Gmail, the same thing described in this thread happenined to me. I've used Gmail and Pegasus together since 2008. I've never had a problem logging in. Last October I suffered an injury. Today, 3/14/18 is the first time since then I was able to use the computer with Pegasus on it. I tried to login to Gmail, with the same settings as before. I got the following message, tho I redacted my actual name.  To be precise, I the same message, changed my Gmail password, then updated my PMail settings, and then got the following.

[*] Connection established to 173.194.202.108
>> 0066 +OK Gpop ready for requests from 68.107.39.105 j15mb232151109ooa
<< 0021 USER -----.--------
>> 0015 +OK send PASS
<< 0015 PASS XXXXXXXX
>> 0049 -ERR [AUTH] Username and password not accepted.

While I'm trying to login to Gmail, this thread seems to be describing my problem as well.

Any answers yet? Thanks for your help.

Barry Levinsky

The "[AUTH] Username and password not accepted." entry is specifically an authentication failure (incorrect username and/or password).  Confirm that you can login via the Gmail web interface if you haven't since changing the password.