Because Yahoo recently decided that POP3 clients would have to be SSL enabled, I finally got round to upgrading from Pegasus 4.01 (I believe) to 4.63. This upgrade (not a new install) was successful except I had to reconfigure the Network configuration for each identity. Three of these do not utilise SSL security, three identities do.
After reconfiguration, all seemed well, though there was one incident of the BSOD when testing one of the SSL-enabled IDs, which did not reoccur - at first. I checked each ID for receiving and sending.
However, soon afterwards, I found that checking any ID with SSL security for incoming mail, I get the BSOD.
I deleted all the IDs and reset them. Those without SSL are ok, but the first one I tested that did, BSOD crashed on checking for incoming mail.
I've attached the reports generated by XP (manifest.txt, Mini100313-04.dmp & sysdata.xml) as a zip file. They mean 0 to me...
Any ideas would be most welcome.
Thanks !
<p>Because Yahoo recently decided that POP3 clients would have to be SSL enabled, I finally got round to upgrading from Pegasus 4.01 (I believe) to 4.63.&nbsp; This upgrade (not a new install) was successful except I had to reconfigure the Network configuration for each identity.&nbsp; Three of these do not utilise SSL security, three identities do.</p><p>After reconfiguration, all seemed well, though there was one incident of the BSOD when testing one of the SSL-enabled IDs, which did not reoccur - at first.&nbsp; I checked each ID for receiving and sending.</p><p>However, soon afterwards, I found that checking any ID with SSL security for incoming mail, I get the BSOD.</p><p>I deleted all the IDs and reset them.&nbsp; Those without SSL are ok, but the first one I tested that did, BSOD crashed on checking for incoming mail. </p><p>I've attached the reports generated by XP (manifest.txt, Mini100313-04.dmp &amp; sysdata.xml) as a zip file.&nbsp; They mean 0 to me...</p><p>Any ideas would be most welcome.</p><p>&nbsp;Thanks !
</p>
