My mail host (Comcast) sent a notice that they will implement SSL for POP in a few weeks and depricate port 110, replacing it with 995.
I downloaded the HermesSSL update for Eudora7.,1 today. Following directions, I replaced 4 files in my program folder (libeay32.dll, QCSSL.dll, rootcerts.p7b, ssleay32.dll).
Here are the relevant lines in the INI file:
UseSubmissionPort=1
SmtpAuthAllowed=1
SMTPServer=smtp.comcast.net
PopServer=mail.comcast.net
POPPort=995
UsesPOP=1
UsesIMAP=0
SSLSendUse=3
SSLReceiveUse=3
I get a timeout when trying to check for mail - with a message saying "Error reading from Network, closed by foriegn host".
I do not want to switch to another email client, especially with the pending release of Hermes... Any suggestions on how to make Eudora 7.1 (paid version) work with SSL on port 995?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Michael, Our updated SSL code for Eudora allows use of SSL/TLS in many contexts where the original code did not. It is not a cure-all however and we are still working to enhance it to work in more cases. We know, for example, that it does not work with Zimbra. Comcast may be another. I do not have a Comcast account so will not be able to test it there. Do you happen to know what POP server Comcast uses? Would you be ready to do some testing for us?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will see if I can find out what Comcast uses for mail servers, they did use Zimbra for webmail - but that may have changed. I will be happy to help with testing. I worked in the computer support field (now retired) - but I have no coding experience.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did a packet capture using Wireshark of an attempt to connect Eudora via port 995 using SSH/TLS. I don't see any data being transfered, just handshakes. I can send you the capture files if you have a CAP file viewer. Do you have a secure way to send the files (other than public postings here?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Eudora works with the new Comcast settings. In addition to changing the port to 995, you need to change [under 'checking mail'] SS to "required, alternate port".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried that setting as well with the same result. Making that change in the options menu changes the eudora.ini fields to:
SSLSendUse=2
SSLReceiveUse=2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Remember to eMail me the compiled file so that I may package it and put it
online. :-) Alternatively, you can do it yourself; you have
administrative permissions both on SF and BitBucket.
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
WOW, Pete....thanks.
It's really too bad that all this software "stuff" is such a moving target.
Comcast is my internet provider, but I've never cared about using Eudora to check any of my webmail accounts....maybe because Eudora never worked with them? Nah, that's not the case.
However, judging from the volumes of email I get from that Eudora list, I'm clearly in the minority and the work you're doing on QCSSL is welcome/appreciated. :-)
Last edit: Walt Stagner 2018-10-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Comcast has finally closed port 110 today. Since I've been unable to get my copy of Eudora to connect to port 995 - that offically ends my use of Eudora (at least for now). Anyone have a suggestion on what client to migrate to, with the expectation I will move to Hermes when it is released ? (BTW, I officially toss my hat into the ALPHA testing pool... :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using our latest QCSSL release? We have tested that successfully with Comcast POP to port 995. If it is not working for you then I would like to try to determine why.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I confirm that the latest QCSSL (10/29/18) works fine with Comcast email.
If Eudora is connecting to port 110 instead of port 995, I believe you need to configure incoming mail to "Required, Alternate Port"instead of "Required, STARTTLS".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mike, if you'd like to be added to the Alpha testing pool, could you privately send me your e-Mail address? Or post it on here? I'd like to send you an invite to our BitBucket project (the Web site will eventually be hosted there, and our source code already is).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am using davmail, which converts an exchange EWS url to imap/smtp. It works with chandler and thunderbird, but not with Eudora. I set the smtp server to 127.0.0.1:1025 and the imap server to 127.0.0.1:1143, but I get auth errors. I am not encrypting traffic to the davmail local proxy, since davmail encrypts from the local machine to the exchange server. I have attached the davmail log below.
Hi, Justin. I recommend you join the Eudora-Win email list, and ask your question there. Note that the list doesn't support attachments, but you could excerpt a short relevant part of your log file in your message.
My mail host (Comcast) sent a notice that they will implement SSL for POP in a few weeks and depricate port 110, replacing it with 995.
I downloaded the HermesSSL update for Eudora7.,1 today. Following directions, I replaced 4 files in my program folder (libeay32.dll, QCSSL.dll, rootcerts.p7b, ssleay32.dll).
I also edited the eudora.ini file to change the pop port to match the directions at Xfinity (from 110 to 995 - directions here: https://www.xfinity.com/support/articles/update-pop3-110-995?rid=19349415&mid=20181010_AdHoc_CM_POP_Rewrite
Here are the relevant lines in the INI file:
UseSubmissionPort=1
SmtpAuthAllowed=1
SMTPServer=smtp.comcast.net
PopServer=mail.comcast.net
POPPort=995
UsesPOP=1
UsesIMAP=0
SSLSendUse=3
SSLReceiveUse=3
I get a timeout when trying to check for mail - with a message saying "Error reading from Network, closed by foriegn host".
I do not want to switch to another email client, especially with the pending release of Hermes... Any suggestions on how to make Eudora 7.1 (paid version) work with SSL on port 995?
Hello Michael, Our updated SSL code for Eudora allows use of SSL/TLS in many contexts where the original code did not. It is not a cure-all however and we are still working to enhance it to work in more cases. We know, for example, that it does not work with Zimbra. Comcast may be another. I do not have a Comcast account so will not be able to test it there. Do you happen to know what POP server Comcast uses? Would you be ready to do some testing for us?
I will see if I can find out what Comcast uses for mail servers, they did use Zimbra for webmail - but that may have changed. I will be happy to help with testing. I worked in the computer support field (now retired) - but I have no coding experience.
I did a packet capture using Wireshark of an attempt to connect Eudora via port 995 using SSH/TLS. I don't see any data being transfered, just handshakes. I can send you the capture files if you have a CAP file viewer. Do you have a secure way to send the files (other than public postings here?)
I use Wireshark and am curious to see your capture. I am not sure of how best to send them to me though.
Eudora works with the new Comcast settings. In addition to changing the port to 995, you need to change [under 'checking mail'] SS to "required, alternate port".
I tried that setting as well with the same result. Making that change in the options menu changes the eudora.ini fields to:
SSLSendUse=2
SSLReceiveUse=2
Pete....current Comcast mail server settings are here: https://www.xfinity.com/support/articles/email-client-programs-with-xfinity-email, just in case you ever need them.
Last edit: Walt Stagner 2018-10-22
Walt, Thank you. I have completed a new update to QCSSL that works with Comcast. It should be available soon.
On Mon, 29 Oct 2018 at 19:23, Pete Maclean petemaclean@users.sourceforge.net wrote:
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
WOW, Pete....thanks.
It's really too bad that all this software "stuff" is such a moving target.
Comcast is my internet provider, but I've never cared about using Eudora to check any of my webmail accounts....maybe because Eudora never worked with them? Nah, that's not the case.
However, judging from the volumes of email I get from that Eudora list, I'm clearly in the minority and the work you're doing on QCSSL is welcome/appreciated. :-)
Last edit: Walt Stagner 2018-10-30
Comcast has finally closed port 110 today. Since I've been unable to get my copy of Eudora to connect to port 995 - that offically ends my use of Eudora (at least for now). Anyone have a suggestion on what client to migrate to, with the expectation I will move to Hermes when it is released ? (BTW, I officially toss my hat into the ALPHA testing pool... :)
Are you using our latest QCSSL release? We have tested that successfully with Comcast POP to port 995. If it is not working for you then I would like to try to determine why.
I confirm that the latest QCSSL (10/29/18) works fine with Comcast email.
If Eudora is connecting to port 110 instead of port 995, I believe you need to configure incoming mail to "Required, Alternate Port"instead of "Required, STARTTLS".
Mike, if you'd like to be added to the Alpha testing pool, could you privately send me your e-Mail address? Or post it on here? I'd like to send you an invite to our BitBucket project (the Web site will eventually be hosted there, and our source code already is).
sorry
Last edit: Betty Twiselton 2019-01-29
I am using davmail, which converts an exchange EWS url to imap/smtp. It works with chandler and thunderbird, but not with Eudora. I set the smtp server to 127.0.0.1:1025 and the imap server to 127.0.0.1:1143, but I get auth errors. I am not encrypting traffic to the davmail local proxy, since davmail encrypts from the local machine to the exchange server. I have attached the davmail log below.
Last edit: Justin Goldberg 2019-10-12
Hi, Justin. I recommend you join the Eudora-Win email list, and ask your question there. Note that the list doesn't support attachments, but you could excerpt a short relevant part of your log file in your message.
Subscription info is at the top of http://listmoms.net/eudora-win/index.html