I don't think Pegasus is responsible, but my mail provider refuses to go any further until I have discussed it with you. We have used Pegasus for many years, without problems. We are currently running Pegasus 4.80, on Win-10, and using a mail server from our local internet provider, eastlink.ca. In brief, Eastlink revised their security protocols, requiring us to update our password. The revised p/w works on Eastlink's webmail, but when we entered it into Pegasus, using the Pegasus Setup Wizard, followed by an attempted login to Eastlink, the trace shows things going smoothly up to the request, (from the mail server), for the p/w, at which point their server throws an error message: ERR AUTH, Authentication Failed. (Pegasus displays a message that either username or password are incorrect.)
Seems to me that it is not Pegasus which is complaining, but Eastlink, who are rejecting the transmission from Pegasus. Eastlink says it has nothing to do with them, but must have something to do with the transmission from Pegasus itself. (I don't have a very good feeling about this being easily resolved...) (And, underlying it is a distinct hostility on the part of Eastlink to our use of POP-3 in the first place.)
I don't think Pegasus is responsible, but my mail provider refuses to go any further until I have discussed it with you. We have used Pegasus for many years, without problems. We are currently running Pegasus 4.80, on Win-10, and using a mail server from our local internet provider, eastlink.ca. In brief, Eastlink revised their security protocols, requiring us to update our password. The revised p/w works on Eastlink's webmail, but when we entered it into Pegasus, using the Pegasus Setup Wizard, followed by an attempted login to Eastlink, the trace shows things going smoothly up to the request, (from the mail server), for the p/w, at which point their server throws an error message: ERR AUTH, Authentication Failed. (Pegasus displays a message that either username or password are incorrect.)
Seems to me that it is not Pegasus which is complaining, but Eastlink, who are rejecting the transmission from Pegasus. Eastlink says it has nothing to do with them, but must have something to do with the transmission from Pegasus itself. (I don't have a very good feeling about this being easily resolved...) (And, underlying it is a distinct hostility on the part of Eastlink to our use of POP-3 in the first place.)