> Yesterday, that all changed. Now I can only receive (POP3) emails,
> but my sending is blocked no matter which of the three security
> protocol buttons I choose. I can ping the mail server; nothing
> wrong with the hardware link.
What we really need to see is a session log showing exactly what is happening between Pegasus Mail and the host. I suspect from your mail that you need to be using STARTTLS with your username and password and then also use SMTP authentication.
>
> Three different error messages, "Never" brings "must start TTLS
> first."
>
> Use STARTTLS brings "user not authenticated."
>
> Via direct SSL brings no explanation except "network error."
>
> I've spent three long calls to my ISP support, which is Bell
> Telephone in Canada, emails ending in @sympatico.ca
>
> As English isn't the first language of the overseas support people,
> it's a little hard to communicate, but as far as I can tell, their
> system made a "security change" and who knows what that was, but it
> does block Pegasus sending.
>
> Sad to report, Windows Mail, the Vista incarnation of what used to
> be called "Outlook," DOES work.
>
> It appears that there is some additional security protocol feature in
> Windows Mail that doesn't exist in Pegasus. (Sad sad day for the
> emailing world!)
Probably it because of something that outlook does not do, CRAM-MD5, and this has been causing all sorts of problems when it's advertised and then not implemented. You can use PB1 and tell the system to never use CRAM-MD5. From the PB1 help:
Do not use CRAM-MD5 authentication even if it is advertised This one's a bit technical, so please bear with us... The process of logging into the SMTP server to authenticate your identity can take a variety of forms: the server "advertises" the forms it understands, and Pegasus Mail looks through that list, choosing the most secure form it recognizes. Some forms are very "weak", in that they either transmit your credentials as clear text or in a form that can be easily broken, while other forms are "strong", in the sense that it is very difficult to work out your credentials simply by observing the exchange of data between the two programs. Unfortunately, one of the strongest forms of authentication, called CRAM-MD5, is commonly misconfigured on SMTP servers, even at quite reputable ISPs - the server will advertise that it supports it, but will actually fail any attempt to use it. Getting the ISP to realize that they are at fault is a lost cause in most cases - it's almost always easier simply to check this control, which tells Pegasus Mail never to use CRAM-MD5 for this server. You should be aware that you reduce the security of your connection by checking this control: CRAM-MD5 is the only commonly-used authentication form that offers reasonable security, and by disabling it, you force Pegasus Mail to use less secure methods... But sometimes you may decide that being able to send mail is more important than being able to do it securely. The choice is yours.
> Yesterday, that all changed.  Now I can only receive (POP3) emails,
> but my sending is blocked no matter which of the three security
> protocol buttons I choose.  I can ping the mail server; nothing
> wrong with the hardware link.
What we really need to see is a session log showing exactly what is happening between Pegasus Mail and the host.  I suspect from your mail that you need to be using STARTTLS with your username and password and then also use SMTP authentication.
>
> Three different error messages, "Never" brings "must start TTLS
> first."
>
> Use STARTTLS brings "user not authenticated."
>
> Via direct SSL brings no explanation except "network error."
>
> I've spent three long calls to my ISP support, which is Bell
> Telephone in Canada, emails ending in @sympatico.ca
>
> As English isn't the first language of the overseas support people,
> it's a little hard to communicate, but as far as I can tell, their
> system made a "security change" and who knows what that was, but it
> does block Pegasus sending.
>
> Sad to report, Windows Mail, the Vista incarnation of what used to
> be called "Outlook," DOES work.
>
> It appears that there is some additional security protocol feature in
> Windows Mail that doesn't exist in Pegasus.  (Sad sad day for the
> emailing world!)
Probably it because of something that outlook does not do, CRAM-MD5, and this has been causing all sorts of problems when it's advertised and then not implemented.  You can use PB1 and tell the system to never use CRAM-MD5.  From the PB1 help:
<i><b>Do not use CRAM-MD5 authentication even if it is advertised</b>&nbsp; This one's a bit technical, so please bear with us... The process of logging into the SMTP server to authenticate your identity can take a variety of forms: the server "advertises" the forms it understands, and Pegasus Mail looks through that list, choosing the most secure form it recognizes. Some forms are very "weak", in that they either transmit your credentials as clear text or in a form that can be easily broken, while other forms are "strong", in the sense that it is very difficult to work out your credentials simply by observing the exchange of data between the two programs. Unfortunately, one of the strongest forms of authentication, called CRAM-MD5, is commonly misconfigured on SMTP servers, even at quite reputable ISPs - the server will advertise that it supports it, but will actually fail any attempt to use it. Getting the ISP to realize that they are at fault is a lost cause in most cases - it's almost always easier simply to check this control, which tells Pegasus Mail never to use CRAM-MD5 for this server. You should be aware that you reduce the security of your connection by checking this control: CRAM-MD5 is the only commonly-used authentication form that offers reasonable security, and by disabling it, you force Pegasus Mail to use less secure methods... But sometimes you may decide that being able to send mail is more important than being able to do it securely. The choice is yours.</i>
