• Suddenly cannot send email but can receive

    From Joshua Reichek@21:1/5 to All on Wed Feb 23 14:35:11 2022
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send emails.
    I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is
    working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0] BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis Lee Bieber@21:1/5 to I called dslextreme technical suppo on Wed Feb 23 19:32:48 2022
    On Wed, 23 Feb 2022 14:35:11 -0800 (PST), Joshua Reichek <reichek@dslextreme.com> declaimed the following:

    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send emails.
    I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    Per https://secure.dslextreme.com/support/kb/email-and-newsgroups/generic-mail-settings-for-email-programs
    """
    Outgoing Mail Server: smtp.dslextreme.com
    Outgoing Mail Server port is 465.
    Outgoing Mail Server requires SSL.

    The Outgoing Mail Server does require authentication. The E-mail address
    and associated password are the username and password
    """

    Note that, if you have not installed an updated SSL, with new root certificates, Eudora will likely fail to connect on SSL. https://sourceforge.net/projects/hermesmail/files/ grab the HermSSL package
    and follow the instructions.


    --
    Wulfraed Dennis Lee Bieber AF6VN
    wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Thu Feb 24 04:50:40 2022
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send emails. I
    can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is working fine
    and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Thu Feb 24 10:42:34 2022
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send emails.
    I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is working
    fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0] BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port". Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them. Thank
    for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Thu Feb 24 10:55:31 2022
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send
    emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is
    working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0] I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0] BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port". Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them. Thank for
    your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing password, and put
    in the new one when prompted.
    Good luck!
    Cheers,
    Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Fri Feb 25 17:15:11 2022
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send
    emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is
    working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port". Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them. Thank
    for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving. The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing password, and
    put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis Lee Bieber@21:1/5 to All on Fri Feb 25 22:13:03 2022
    On Fri, 25 Feb 2022 17:15:11 -0800 (PST), Joshua Reichek <reichek@dslextreme.com> declaimed the following:


    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    "I still cannot send emails" is about as useful as "Doctor, it hurts when I do this".

    Install, if you haven't already, the esoteric plugin.

    Tools/Options/Logging
    Enable everything except maybe Search... and Playlists.

    Attempt to send some message.

    Shut-down Eudora.

    Open the Eudora log file, scroll down to the start of that session and
    start examining it for the server handshakes. If you cut&paste to a post
    here, be careful -- Eudora uses simple UUEncode for masking passwords;
    anyone with any skill can decode the sent password.


    --
    Wulfraed Dennis Lee Bieber AF6VN
    wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sat Feb 26 04:35:27 2022
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send
    emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is
    working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them. Thank
    for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving. The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing password, and
    put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sat Feb 26 08:20:48 2022
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to send
    emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server is
    working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them.
    Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course! Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing password,
    and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending"
    be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application
    specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser
    based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora
    to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to Joshua Reichek on Sat Feb 26 08:29:52 2022
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to
    send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server
    is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them.
    Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course! Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing password,
    and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my computer,
    a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be set to "
    Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific password
    for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser based
    mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to
    remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This forum
    does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do? Best,
    Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sat Feb 26 09:39:10 2022
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not to
    send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail server
    is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them.
    Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send. Any
    further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be
    set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser
    based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora
    to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This forum
    does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do? Best,
    Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If so, the
    Hermes files are doing what they should do.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sat Feb 26 09:57:08 2022
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not
    to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail
    server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them.
    Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send.
    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be
    set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser
    based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in
    Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do? Best,
    Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If so,
    the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you
    started Eudora" Best, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sat Feb 26 09:53:02 2022
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not
    to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail
    server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for them.
    Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send.
    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be
    set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser
    based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in
    Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do? Best,
    Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If so,
    the Hermes files are doing what they should do.
    Dear Dave, Under the Incoming Mail I do not have a "Last ssl info" Would it be better to correspond using screen shots ... my direct email is reichek@dslextreme.com ... Do you take paypal? Perhaps we could agree on a fee for getting me back
    sending emails? I would like to be able to pay you for your help. Regards, Joshua
    my Incoming Mail window has:
    server configuration set to POP (not IMAP)
    and authentication style set to Password (not kerberos, not APOP, not RPA)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sat Feb 26 14:48:55 2022
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided not
    to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail
    server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for
    them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not send.
    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be
    set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's, browser
    based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in
    Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do? Best,
    Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If so,
    the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you started
    Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sat Feb 26 15:09:59 2022
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided
    not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail
    server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out for
    them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not
    send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted my
    computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending" be
    set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's,
    browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in
    Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do?
    Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If
    so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you
    started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window. Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to Joshua Reichek on Sat Feb 26 15:24:18 2022
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly decided
    not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said their mail
    server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out
    for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your existing
    password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not
    send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted
    my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending"
    be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's,
    browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in
    Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful - This
    forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do?
    Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2? If
    so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you
    started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window. Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dennis Lee Bieber@21:1/5 to All on Sat Feb 26 19:12:18 2022
    On Sat, 26 Feb 2022 14:48:55 -0800 (PST), DaveH2 <dave-h@sky.com> declaimed
    the following:


    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.

    I believe the OP has stated that INBOUND email runs with SSL: NEVER -- so it will never have a "last SSL info" which can be checked.

    That would leave trying to SEND a message, and then checking the OUTBOUND "last SSL info" for messages.


    --
    Wulfraed Dennis Lee Bieber AF6VN
    wlfraed@ix.netcom.com http://wlfraed.microdiversity.freeddns.org/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sun Feb 27 04:44:08 2022
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly
    decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said
    their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way out
    for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your
    existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But not
    send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I rebooted
    my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when Sending"
    be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application specific
    password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's,
    browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords
    in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was unsuccessful -
    This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I do?
    Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2?
    If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you
    started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window. Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "Use relay
    personality" is unchecked, and "Use submission port" is checked on the sending side.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sun Feb 27 08:16:30 2022
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly
    decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said
    their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way
    out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your
    existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But
    not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.2"
    .
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I
    rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when
    Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application
    specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme 's,
    browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget
    Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I
    do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.2?
    If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time you
    started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window. Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "Use relay
    personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sun Feb 27 10:03:42 2022
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly
    decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said
    their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy way
    out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your
    existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine. But
    not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do. If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "TLSv1.
    2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I
    rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when
    Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application
    specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme '
    s, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget
    Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting I
    do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say TLSv1.
    2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time
    you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "Use
    relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay Personality be
    set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem. Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dave-h@sky.com> to see if it
    works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sun Feb 27 12:08:59 2022
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it suddenly
    decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They said
    their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy
    way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove your
    existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine.
    But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "
    TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I
    rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when
    Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application
    specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider - dslextreme
    's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget
    Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are suggesting
    I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say
    TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last time
    you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "Use
    relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay Personality
    be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem. Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to see if it
    works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to Joshua Reichek on Sun Feb 27 12:18:09 2022
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it
    suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They
    said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the easy
    way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove
    your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them fine.
    But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "
    TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it. I
    rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets when
    Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an application
    specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget
    Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are
    suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say
    TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last
    time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it says "
    Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards,
    Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "Use
    relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay Personality
    be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem. Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to see if it
    works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua

    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards and respects, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to Joshua Reichek on Sun Feb 27 13:36:24 2022
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it
    suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They
    said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked: allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the
    easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/ These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove
    your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them
    fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should say "
    TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it.
    I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets
    when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an
    application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>Forget
    Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are
    suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it say
    TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the last
    time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it
    says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards,
    Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "
    Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to see if
    it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua

    Dear Dave, Greetings and good afternoon. I have sent an email to support@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and that
    a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sun Feb 27 14:09:42 2022
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it
    suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They
    said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked: allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the
    easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/ These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to remove
    your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them
    fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should
    say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched it.
    I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure Sockets
    when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require an
    application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>
    Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are
    suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it
    say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the
    last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it
    says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards,
    Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked, "
    Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam! If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to see
    if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and that a
    ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Sun Feb 27 14:57:15 2022
    On Sunday, February 27, 2022 at 2:09:43 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when it
    suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem – They
    said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com
    smtp relay personality: None
    All the following options are checked: allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is the
    easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/ These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to
    remove your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive them
    fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it should
    say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and relaunched
    it. I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "Secure
    Sockets when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now require
    an application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>
    Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are
    suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does it
    say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the
    last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field it
    says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative regards,
    Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is checked,
    "Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to see
    if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and that
    a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.

    Dear Dave, Greetings and good afternoon. I tried to resend the messages that went through earlier - one to myself - to my email address and an other to a good friend. They now will not send and I get the same error message trying to send them to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look] I tried to resend to you at the dave-h<at>sky.com where the less than greater than is actually a @ -- it still does not send and I get the same error message to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Your further consideration is most appreciated. With best regards and respects, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Sun Feb 27 16:38:05 2022
    On Sunday, 27 February 2022 at 22:57:16 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 2:09:43 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when
    it suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem –
    They said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is
    the easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities.
    One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to
    remove your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive
    them fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it
    should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and
    relaunched it. I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "
    Secure Sockets when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now
    require an application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>
    Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you are
    suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there? Does
    it say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since the
    last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status field
    it says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative
    regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is
    checked, "Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to
    see if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support at
    dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and
    that a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.
    Dear Dave, Greetings and good afternoon. I tried to resend the messages that went through earlier - one to myself - to my email address and an other to a good friend. They now will not send and I get the same error message trying to send them to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look] I tried to resend to you at the dave-h<at>sky.com where the less than greater than is actually a @ -- it still does not send and I get the same error message to wit: Error
    talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Your further consideration is most appreciated. With best regards and respects, Joshua

    OK. Well there's nothing else either of us can do about this.
    Your outgoing messages are being blocked and only your service provider can address that.
    They need to identify which blacklist you are on, and get the block removed.
    If you have security software installed, i would do a full scan anyway, just in case you do have an infection on your system which is sending out spam messages! I hope not, but you never know!
    I don't think this problem is now anything to do with your Eudora setup.
    Good luck. Cheers, Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to dav...@sky.com on Tue Mar 1 13:54:36 2022
    On Sunday, February 27, 2022 at 4:38:06 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 22:57:16 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 2:09:43 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend when
    it suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem –
    They said their mail server is working fine and has been without any issues.

    My Eudora email settings are:
    smtp server: smtp.dslextreme.com smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that is
    the easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities. One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora to
    remove your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can receive
    them fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it
    should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and
    relaunched it. I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "
    Secure Sockets when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now
    require an application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service provider -
    dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option Special>
    Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here but was
    unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you
    are suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there?
    Does it say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since
    the last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status
    field it says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative
    regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is
    checked, "Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com> to
    see if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support
    at dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and
    that a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.
    Dear Dave, Greetings and good afternoon. I tried to resend the messages that went through earlier - one to myself - to my email address and an other to a good friend. They now will not send and I get the same error message trying to send them to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look] I tried to resend to you at the dave-h<at>sky.com where the less than greater than is actually a @ -- it still does not send and I get the same error message to wit: Error
    talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Your further consideration is most appreciated. With best regards and respects, Joshua

    OK. Well there's nothing else either of us can do about this.
    Your outgoing messages are being blocked and only your service provider can address that.
    They need to identify which blacklist you are on, and get the block removed. If you have security software installed, i would do a full scan anyway, just in case you do have an infection on your system which is sending out spam messages! I hope not, but you never know!
    I don't think this problem is now anything to do with your Eudora setup. Good luck. Cheers, Dave.
    Dear Dave and fellow forum members, Greetings. Things "magically" started working fine this morning. I am now able to send emails without issue. I wanted to finish the loop on the experience with this issue (at least for the time being) Tech support
    at dslextreme said they had several recent security and mail server updates. That it can take up to 3 days for the servers to fully update particularly as regards the older lesser used email clients served by these mail servers - but hopefully it is
    now all working correctly even for a user such as myself using an antiquated email client. They suggested I give consideration to using webmail, something more recent. That I stop using Eudora to avoid this kind of issue in the future. They indicated
    there is a good chance at some point Eudora will just stop working and not be able to serve as an email client anymore. Best regards and respects, Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Wed Mar 2 04:30:27 2022
    On Tuesday, 1 March 2022 at 21:54:37 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:38:06 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 22:57:16 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 2:09:43 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend
    when it suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem â€
    “ They said their mail server is working fine and has been without any issues.

    My Eudora email settings are: smtp server: smtp.dslextreme.com smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that
    is the easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities. One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora
    to remove your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can
    receive them fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it
    should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and
    relaunched it. I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "
    Secure Sockets when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now
    require an application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service
    provider - dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option
    Special>Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here
    but was unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you
    are suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there?
    Does it say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since
    the last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status
    field it says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative
    regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is
    checked, "Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com>
    to see if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support
    at dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and
    that a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.
    Dear Dave, Greetings and good afternoon. I tried to resend the messages that went through earlier - one to myself - to my email address and an other to a good friend. They now will not send and I get the same error message trying to send them to
    wit: Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look] I tried to resend to you at the dave-h<at>sky.com where the less than greater than is actually a @ -- it still does not send and I get the same error message to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Your further consideration is most appreciated. With best regards and respects, Joshua

    OK. Well there's nothing else either of us can do about this.
    Your outgoing messages are being blocked and only your service provider can address that.
    They need to identify which blacklist you are on, and get the block removed.
    If you have security software installed, i would do a full scan anyway, just in case you do have an infection on your system which is sending out spam messages! I hope not, but you never know!
    I don't think this problem is now anything to do with your Eudora setup. Good luck. Cheers, Dave.
    Dear Dave and fellow forum members, Greetings. Things "magically" started working fine this morning. I am now able to send emails without issue. I wanted to finish the loop on the experience with this issue (at least for the time being) Tech support at
    dslextreme said they had several recent security and mail server updates. That it can take up to 3 days for the servers to fully update particularly as regards the older lesser used email clients served by these mail servers - but hopefully it is now all
    working correctly even for a user such as myself using an antiquated email client. They suggested I give consideration to using webmail, something more recent. That I stop using Eudora to avoid this kind of issue in the future. They indicated there is a
    good chance at some point Eudora will just stop working and not be able to serve as an email client anymore. Best regards and respects, Joshua

    Glad to hear that it's working again now Joshua!
    DSLExtreme had obviously been changing things, but at least now your copy of Eudora has been patched with the Hermes update it should keep working for a bit longer than it probably would have done otherwise.
    Of course all mail providers would rather that you used webmail nowadays as that's easier for them to maintain and support, but many people still want to use mail client programs and store their messages locally, so it will be a long time before they
    will be able to get away with withdrawing that service.
    Although Eudora is struggling a bit now due to it's age, it's still the best mail client ever made in many people's opinion, so I hope there's plenty more years in it yet, especially thanks to the guys at the Hermes project!
    Glad to have been able to help.
    Cheers, Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From DaveH2@21:1/5 to rei...@dslextreme.com on Wed Mar 2 04:28:14 2022
    On Tuesday, 1 March 2022 at 21:54:37 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:38:06 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 22:57:16 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 2:09:43 PM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 21:36:25 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 12:18:10 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 12:09:00 PM UTC-8, Joshua Reichek wrote:
    On Sunday, February 27, 2022 at 10:03:43 AM UTC-8, dav...@sky.com wrote:
    On Sunday, 27 February 2022 at 16:16:31 UTC, rei...@dslextreme.com wrote:
    On Sunday, February 27, 2022 at 4:44:09 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 23:24:19 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 3:10:00 PM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 2:48:56 PM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 17:57:09 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 9:39:12 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 16:29:53 UTC, rei...@dslextreme.com wrote:
    On Saturday, February 26, 2022 at 8:20:50 AM UTC-8, Joshua Reichek wrote:
    On Saturday, February 26, 2022 at 4:35:28 AM UTC-8, dav...@sky.com wrote:
    On Saturday, 26 February 2022 at 01:15:12 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 10:55:33 AM UTC-8, dav...@sky.com wrote:
    On Thursday, 24 February 2022 at 18:42:36 UTC, rei...@dslextreme.com wrote:
    On Thursday, February 24, 2022 at 4:50:42 AM UTC-8, dav...@sky.com wrote:
    On Wednesday, 23 February 2022 at 22:35:13 UTC, rei...@dslextreme.com wrote:
    Greetings all. I have been using Eudora 7.1.0.9 in windows as my email client for nearly 20 years. Currently it is running with the latest version of windows 10. It was running fine until this past weekend
    when it suddenly decided not to send emails. I can receive emails no problem. None of my settings in Eudora have changed. These setting were working fine for years. I called dslextreme technical support for email and they of course said not our problem â€
    “ They said their mail server is working fine and has been without any issues.

    My Eudora email settings are: smtp server: smtp.dslextreme.com smtp relay personality: None
    All the following options are checked:
    allow authentication
    immediate send
    send on check
    use submission port (587)
    Secure sockets when sending: Never

    The issue I have with not being able to send emails is: upon and attempt to send an email, I get the following error message:
    <Dominant> , Connecting to the Mail Server…., EHLO MBMaster1.dslextreme.com {04:22:50 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    I also get:
    <Dominant> , Connecting to the Mail Server…., HELO MBMaster1.dslextreme.com {05:14:16 PM}
    Error reading from network Cause: connection closed by foreign host. [0]
    BTW .. MBMaster1 is the name of my computer. Any ideas? Anything would be appreciated.
    With appreciative regards, Joshua
    Try setting "Secure Sockets when Sending" to "Required, Alternate Port".
    Your provider has probably updated their security requirements, and you will probably have to do the same for receiving soon as well.
    Dav...sky - Thank you for responding. My provider's tech support said there had been no changes to the server and it was working fine - no other customers calling in with similar technical issues. Of course that
    is the easy way out for them. Thank for your suggestion -- I have tried all the options for setting "Secure Sockets when Sending" and none of them permit me to send emails again. There are four options to choose from for "Secure Sockets when Sending" :
    Never
    if available, STARTTLS
    Required, Alternate port
    Required, STARTTLS

    Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Well they must have changed something, or it wouldn't have suddenly stopped working!
    There are two immediate possibilities. One is that they have stopped supporting TLSv1.0 encryption, which is the only version that Eudora can natively use.
    That is fixable using an update to some Eudora program files. It's called Hermes (nothing to do with the courier company!)
    https://sourceforge.net/projects/hermesmail/
    These new files give TLSv1.2 support to Eudora for sending and receiving.
    The other possibility is that they now require an application specific password for mail clients that they deem to be insecure.
    Eudora is one of them due to its age since its last update of course!
    Have a look at the webmail interface, and check the settings page to see if there's anything that refers to that.
    If so, you will have to get the webmail system to generate an application specific password, which you will have to use in Eudora in place of your usual password. Use the option Special>Forget Passwords in Eudora
    to remove your existing password, and put in the new one when prompted.
    Good luck!
    Cheers,
    Dave.
    Dear Dave and fellow forum members, Thank you for the thoughts and suggestions. I have downloaded Hermes and copied the files, per the readme.txt file, to my Eudora directory. I still cannot send emails. I can
    receive them fine. But not send. Any further thoughts or suggestions would be most welcomed and appreciated . Best regards, Joshua

    Installing the Hermes files is always a good thing to do.
    If you don't need them now, you almost certainly will at some point in the future when the servers stop supporting TLSv1.0.
    You can check that the Hermes update is working by going to the properties of your Eudora persona, selecting the "Incoming Mail" tab, and clicking on "Last SSL Info" after doing a mail check. In the "SSL Info" box it
    should say "TLSv1.2".
    As for the sending problem, did you look at the settings on the webmail interface to see if you can generate an application specific password?
    Cheers, Dave.
    Dear Dave. Thank you so much for your assistance with this. I copied the hermes files over to the Eudora directory and verified that the modified date was yesterday when I copied the files over. I closed Eudora and
    relaunched it. I rebooted my computer, a Microsoft Book 2. The last ssl info gives: You have never done any ssl negotiations with any personality since the last time you started Eudora or a negotiation is in progress with that personality. Should the "
    Secure Sockets when Sending" be set to "Required, Alternate Por" or to "Never" I tried both but neither seems to make an difference. . I still cannot send emails. I am not sure what you are referring to when you say: "The other possibility is they now
    require an application specific password for mail clients they deem to be insecure.
    Have a look at the webmail interface, and check the settings page" -- Where do I find the "webmail interface" (a search for webmail in settings for windows 10 gave no results and I went to Zimbra my email service
    provider - dslextreme 's, browser based mail client and, perhaps in my ignorance, found nothing under preferences which would seem to effect sending mail from an email client?
    "If so, you will have to get the webmail system to generate an application specific password, " How would I go about doing that? "which you will have to use in Eudora in place of your usual password. Use the option
    Special>Forget Passwords in Eudora to remove your existing password, and put in the new one when prompted." Should I remove the existing password and put in a new one anyway? I so appreciate your assistance and knowledge. I tried to send screenshots here
    but was unsuccessful - This forum does not seem to permit including pictures/attachments. With my appreciation and gratitude for your assistance. Best regards, Joshua
    Dear Dave, Greetings again. I occurs to me you may be indicating that I should make sure my password for access to Dslextreme's browser based Zimbra email program is the same as my password for my Eudora. Is that what you
    are suggesting I do? Best, Joshua

    Hi again Joshua, we really need to know that the Hermes files are working. Checking on the sending side won't be any good as you can't send at the moment anyway, so it will always say that you haven't made an SSL connection!
    Do a mail check (it doesn't matter if it doesn't find anything) and then look at the persona properties again, this time looking under the "Incoming Mail" tab. What do you see if you click the "Last SSL Info" button there?
    Does it say TLSv1.2? If so, the Hermes files are doing what they should do.
    Dear Dave, Greetings again. I noticed I have a Last SSL info under Checking Mail the Secure Sockets when receiving is set to Never and the Last SSL Info gives "You have never done any ssl negotiation with any personality since
    the last time you started Eudora" Best, Joshua

    Are you sure you're looking in the right place?
    Do a mail check, and then go to Tools>Personalities, and select your <Dominant> personality, which I assume is the only one you have.
    Right click on it and select "Properties".
    Select the "Incoming Mail" tab.
    There should be a "Last SSL Info" button at the bottom of that window.
    Select it and see what it says. It should say "TLSv1.2" in the "SSL Version" field.
    If you can still receive messages (ignore the sending problem for the moment) that should work and should confirm that the Hermes files are doing their job.
    Dear Dave, Got it. In the Eudora SSL connection information Manager - per your instructions - I got there. in the ssl Version field of the Security Parameters, it says " TLSv1.2 " ..In the security Parameters Negotiation Status
    field it says " Succeeded " In the notes field of the Eudora SSL Connection Manager it says " Certificate bad: Destination Host name does not match host name in certificate
    But ignoring this error because Certificate is trusted " What next?
    Dear Dave, Greetings again. I just wanted to express my appreciation. With your guidance, patience with me, and instructions I feel like there is progress and light in the tunnel. Thank you so much, With friendly and appreciative
    regards, Joshua

    Hi again Joshua. That's very good news that the Hermes files are working and you are making a TLSv1.2 connection.
    That is one big possible cause of the problem eliminated, and hopefully it will enable things to continue working if TLSv1.0 support is removed on the servers, which it almost certainly will be at some point!
    You usually have to have "Required, Alternate Port" selected on most systems nowadays for Eudora to communicate with mail servers, have you tried setting that on sending and receiving? Also make sure that "Authentication Allowed" is
    checked, "Use relay personality" is unchecked, and "Use submission port" is checked on the sending side.
    Dear Dave, Greetings and good day. I have verified the settings and they are now as you requested. There is now a different error message. It seems to be from changing from "Never" to "Required, Alternate Port" -- What should SMTP Relay
    Personality be set to in the Sending Mail popup. None or <Dominant>? The new error message is:

    <Dominant>, Connecting to the Mail Server [7:38:36AM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]

    Best regards, Joshua

    "SMTP Relay Personality" in Tools>Options>Sending Mail" should be set to "None" if you only have one personality.
    Your error message now looks much more like the root cause of the problem.
    Basically your ISP has been blacklisted as a possible source of spam!
    If you Google "RBL Restriction" you will find out plenty about it, such as here -
    https://mailchannels.zendesk.com/hc/en-us/articles/202191674-Fixing-the-550-5-7-1-RBL-Sender-blocked-IP-or-domain-error
    Usually I would have thought the problem would only happen sending some messages, not all, because it would depend on whether the receiving server blocked the message or not. You could try sending a test message to me at <dav...@sky.com>
    to see if it works.
    Whether it does or not, it's something that you need to sort out with your service provider, because they need to get themselves removed from the blacklist!
    Cheers, Dave.
    Dear Dave, Greetings and good day. I really appreciate your working through this with me. Sending emails just suddenly started working. I did not change anything and it just started sending emails. If it stops again I will call Tech Support
    at dslextreme.com again and tell them of the error and your link to the zendesk article. Perhaps they cleared the blockage. I will send an email to the address you provided. I hope you get it. Thank you so much for all your support and all your so
    knowledgeable and helpful assistance. With friendly regards and respects, Joshua
    Dear Dave, Greetings again. It just started not sending emails again. The email I tried to send you at <dav...@sky.com> did not send. I have made no changes in any settings in Eudora.

    The error again:
    <Dominant>, Connecting to the Mail Server [12:10:36PM]
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Best regards and respects, Joshua
    Dear Dave, Greetings and good afternoon. I have sent an email to sup...@dslextreme.com regarding the " [550 5.7.1 [C16] RBL Restriction " message when trying to send emails from my Eudora email client. I got a response acknowledging receipt and
    that a ticket has been created for my issue. and saying I would be contacted. Is there anything we can do at our end? Or is this entirely in the hands of dslextreme? Best regards, Joshua

    No there's nothing you can do, they need to find out why your messages are being blocked.
    I would be very surprised if other people on their system aren't having the same problem although as I said it depends on who the messages are being sent to, as some servers will honour the block and some won't.
    I trust you sent the test message to me using the full address, not the truncated version which is shown here!
    It's dave-h<at>sky.com
    You said that you managed to send some messages OK. Can you try sending them again (with suitable apologies to the recipients!) to see if they still send now?
    If they do, that bears out what I thought, that some messages will be delivered and some won't, depending on the server they're being sent to.
    I think your Eudora setttings are now correct.
    Dear Dave, Greetings and good afternoon. I tried to resend the messages that went through earlier - one to myself - to my email address and an other to a good friend. They now will not send and I get the same error message trying to send them to
    wit: Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look] I tried to resend to you at the dave-h<at>sky.com where the less than greater than is actually a @ -- it still does not send and I get the same error message to wit:
    Error talking to SMTP server [550 5.7.1 [C16] RBL Restriction: See https://look]
    Your further consideration is most appreciated. With best regards and respects, Joshua

    OK. Well there's nothing else either of us can do about this.
    Your outgoing messages are being blocked and only your service provider can address that.
    They need to identify which blacklist you are on, and get the block removed.
    If you have security software installed, i would do a full scan anyway, just in case you do have an infection on your system which is sending out spam messages! I hope not, but you never know!
    I don't think this problem is now anything to do with your Eudora setup. Good luck. Cheers, Dave.
    Dear Dave and fellow forum members, Greetings. Things "magically" started working fine this morning. I am now able to send emails without issue. I wanted to finish the loop on the experience with this issue (at least for the time being) Tech support at
    dslextreme said they had several recent security and mail server updates. That it can take up to 3 days for the servers to fully update particularly as regards the older lesser used email clients served by these mail servers - but hopefully it is now all
    working correctly even for a user such as myself using an antiquated email client. They suggested I give consideration to using webmail, something more recent. That I stop using Eudora to avoid this kind of issue in the future. They indicated there is a
    good chance at some point Eudora will just stop working and not be able to serve as an email client anymore. Best regards and respects, Joshua

    Glad to hear that it's working again now Joshua!
    DSLExtreme had obviously been changing things, but at least now your copy of Eudora has been patched with the Hermes update it should keep working for a bit longer that it probably would have done otherwise.
    Of course all mail providers would rather that you used webmail nowadays as that's easier for them to maintain and support, but many people still want to use mail client programs and store their messages locally, so it will be a long time before they
    will be able to get away with withdrawing that service.
    Although Eudora is struggling a bit now due to it's age, it's still the best mail client ever made in many people's opinion, so I hope there's plenty more years in it yet, especially thanks to the guys at the Hermes project!
    Glad to have been able to help.
    Cheers, Dave.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Pamela@21:1/5 to All on Fri Mar 4 10:46:02 2022
    On 12:30 2 Mar 2022, DaveH2 said:

    On Tuesday, 1 March 2022 at 21:54:37 UTC, rei...@dslextreme.com
    wrote:

    [...]

    Dear Dave and fellow forum members, Greetings. Things "magically"
    started working fine this morning. I am now able to send emails
    without issue. I wanted to finish the loop on the experience with
    this issue (at least for the time being) Tech support at dslextreme
    said they had several recent security and mail server updates. That
    it can take up to 3 days for the servers to fully update
    particularly as regards the older lesser used email clients served
    by these mail servers - but hopefully it is now all working
    correctly even for a user such as myself using an antiquated email
    client. They suggested I give consideration to using webmail,
    something more recent. That I stop using Eudora to avoid this kind
    of issue in the future. They indicated there is a good chance at
    some point Eudora will just stop working and not be able to serve as
    an email client anymore. Best regards and respects, Joshua

    Glad to hear that it's working again now Joshua! DSLExtreme had
    obviously been changing things, but at least now your copy of Eudora
    has been patched with the Hermes update it should keep working for a
    bit longer than it probably would have done otherwise. Of course all
    mail providers would rather that you used webmail nowadays as that's
    easier for them to maintain and support, but many people still want
    to use mail client programs and store their messages locally, so it
    will be a long time before they will be able to get away with
    withdrawing that service. Although Eudora is struggling a bit now due
    to it's age, it's still the best mail client ever made in many
    people's opinion, so I hope there's plenty more years in it yet,
    especially thanks to the guys at the Hermes project! Glad to have
    been able to help. Cheers, Dave.

    Nice to see a successful outcome after some patient work. Well done!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joshua Reichek@21:1/5 to Pamela on Sat Mar 5 07:54:24 2022
    On Friday, March 4, 2022 at 2:46:26 AM UTC-8, Pamela wrote:
    On 12:30 2 Mar 2022, DaveH2 said:

    On Tuesday, 1 March 2022 at 21:54:37 UTC, rei...@dslextreme.com
    wrote:

    [...]

    Dear Dave and fellow forum members, Greetings. Things "magically"
    started working fine this morning. I am now able to send emails
    without issue. I wanted to finish the loop on the experience with
    this issue (at least for the time being) Tech support at dslextreme
    said they had several recent security and mail server updates. That
    it can take up to 3 days for the servers to fully update
    particularly as regards the older lesser used email clients served
    by these mail servers - but hopefully it is now all working
    correctly even for a user such as myself using an antiquated email
    client. They suggested I give consideration to using webmail,
    something more recent. That I stop using Eudora to avoid this kind
    of issue in the future. They indicated there is a good chance at
    some point Eudora will just stop working and not be able to serve as
    an email client anymore. Best regards and respects, Joshua

    Glad to hear that it's working again now Joshua! DSLExtreme had
    obviously been changing things, but at least now your copy of Eudora
    has been patched with the Hermes update it should keep working for a
    bit longer than it probably would have done otherwise. Of course all
    mail providers would rather that you used webmail nowadays as that's
    easier for them to maintain and support, but many people still want
    to use mail client programs and store their messages locally, so it
    will be a long time before they will be able to get away with
    withdrawing that service. Although Eudora is struggling a bit now due
    to it's age, it's still the best mail client ever made in many
    people's opinion, so I hope there's plenty more years in it yet,
    especially thanks to the guys at the Hermes project! Glad to have
    been able to help. Cheers, Dave.
    Nice to see a successful outcome after some patient work. Well done!
    Dear Pamela, Your supportive and positive note is appreciated and well received. Thank you for the thought. Our best good wishes to you Joshua

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)