Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

"It's not just a computer -- it's your ass." -- Cal Keegan


computers / comp.mail.eudora.ms-windows / Re: Suddenly cannot send email but can receive

SubjectAuthor
* Suddenly cannot send email but can receiveJoshua Reichek
`* Re: Suddenly cannot send email but can receiveDaveH2
 `* Re: Suddenly cannot send email but can receiveJoshua Reichek
  `* Re: Suddenly cannot send email but can receiveDaveH2
   `* Re: Suddenly cannot send email but can receiveJoshua Reichek
    `* Re: Suddenly cannot send email but can receiveDaveH2
     `* Re: Suddenly cannot send email but can receiveJoshua Reichek
      `* Re: Suddenly cannot send email but can receiveJoshua Reichek
       `* Re: Suddenly cannot send email but can receiveDaveH2
        +- Re: Suddenly cannot send email but can receiveJoshua Reichek
        `* Re: Suddenly cannot send email but can receiveJoshua Reichek
         `* Re: Suddenly cannot send email but can receiveDaveH2
          `* Re: Suddenly cannot send email but can receiveJoshua Reichek
           `* Re: Suddenly cannot send email but can receiveJoshua Reichek
            `* Re: Suddenly cannot send email but can receiveDaveH2
             `* Re: Suddenly cannot send email but can receiveJoshua Reichek
              `* Re: Suddenly cannot send email but can receiveDaveH2
               `* Re: Suddenly cannot send email but can receiveJoshua Reichek
                +* Re: Suddenly cannot send email but can receiveJoshua Reichek
                |+- Re: Suddenly cannot send email but can receiveDaveH2
                |+- Re: Suddenly cannot send email but can receiveDaveH2
                |+- Re: Suddenly cannot send email but can receiveDaveH2
                |`* Re: Suddenly cannot send email but can receiveDaveH2
                | `* Re: Suddenly cannot send email but can receivePamela
                |  `- Re: Suddenly cannot send email but can receiveJoshua Reichek
                +- Re: Suddenly cannot send email but can receiveJoshua Reichek
                +- Re: Suddenly cannot send email but can receiveJoshua Reichek
                `- Re: Suddenly cannot send email but can receiveJoshua Reichek

Pages:12
Suddenly cannot send email but can receive

<9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=315&group=comp.mail.eudora.ms-windows#315

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a5d:45d0:0:b0:1e3:39ed:530c with SMTP id b16-20020a5d45d0000000b001e339ed530cmr1204499wrs.687.1645655712666;
Wed, 23 Feb 2022 14:35:12 -0800 (PST)
X-Received: by 2002:a05:622a:4289:b0:2d4:69a4:18bd with SMTP id
cr9-20020a05622a428900b002d469a418bdmr1925379qtb.278.1645655712064; Wed, 23
Feb 2022 14:35:12 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Wed, 23 Feb 2022 14:35:11 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
Subject: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Wed, 23 Feb 2022 22:35:12 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Joshua Reichek - Wed, 23 Feb 2022 22:35 UTC

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

Re: Suddenly cannot send email but can receive

<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=316&group=comp.mail.eudora.ms-windows#316

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:adf:c3cc:0:b0:1ed:b641:6ee2 with SMTP id d12-20020adfc3cc000000b001edb6416ee2mr2131144wrg.529.1645707041660;
Thu, 24 Feb 2022 04:50:41 -0800 (PST)
X-Received: by 2002:a37:6110:0:b0:60d:ed9f:18da with SMTP id
v16-20020a376110000000b0060ded9f18damr1468699qkb.610.1645707041007; Thu, 24
Feb 2022 04:50:41 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Thu, 24 Feb 2022 04:50:40 -0800 (PST)
In-Reply-To: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:a54b:91c2:ffd3:23f5;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:a54b:91c2:ffd3:23f5
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Thu, 24 Feb 2022 12:50:41 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: DaveH2 - Thu, 24 Feb 2022 12:50 UTC

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.

Re: Suddenly cannot send email but can receive

<fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=317&group=comp.mail.eudora.ms-windows#317

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a5d:6205:0:b0:1e4:b3fd:9ba8 with SMTP id y5-20020a5d6205000000b001e4b3fd9ba8mr3228176wru.426.1645728155462;
Thu, 24 Feb 2022 10:42:35 -0800 (PST)
X-Received: by 2002:ac8:5850:0:b0:2dd:9260:c4f9 with SMTP id
h16-20020ac85850000000b002dd9260c4f9mr3722363qth.446.1645728155124; Thu, 24
Feb 2022 10:42:35 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.87.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Thu, 24 Feb 2022 10:42:34 -0800 (PST)
In-Reply-To: <33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com> <33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Thu, 24 Feb 2022 18:42:35 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Joshua Reichek - Thu, 24 Feb 2022 18:42 UTC

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

Re: Suddenly cannot send email but can receive

<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=318&group=comp.mail.eudora.ms-windows#318

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a1c:acc6:0:b0:380:e35f:ff1f with SMTP id v189-20020a1cacc6000000b00380e35fff1fmr10560408wme.52.1645728931871;
Thu, 24 Feb 2022 10:55:31 -0800 (PST)
X-Received: by 2002:a05:622a:1301:b0:2de:82c5:8409 with SMTP id
v1-20020a05622a130100b002de82c58409mr3597604qtk.403.1645728931567; Thu, 24
Feb 2022 10:55:31 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.128.88.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Thu, 24 Feb 2022 10:55:31 -0800 (PST)
In-Reply-To: <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:b113:5c2f:1fef:bb8b;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:b113:5c2f:1fef:bb8b
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Thu, 24 Feb 2022 18:55:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: DaveH2 - Thu, 24 Feb 2022 18:55 UTC

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.

Re: Suddenly cannot send email but can receive

<0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=319&group=comp.mail.eudora.ms-windows#319

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:6214:1d01:b0:432:563a:6c93 with SMTP id e1-20020a0562141d0100b00432563a6c93mr8014102qvd.78.1645838111880;
Fri, 25 Feb 2022 17:15:11 -0800 (PST)
X-Received: by 2002:a05:6214:f2d:b0:432:dc5f:ea15 with SMTP id
iw13-20020a0562140f2d00b00432dc5fea15mr2965104qvb.81.1645838111750; Fri, 25
Feb 2022 17:15:11 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Fri, 25 Feb 2022 17:15:11 -0800 (PST)
In-Reply-To: <cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 01:15:11 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 85
 by: Joshua Reichek - Sat, 26 Feb 2022 01:15 UTC

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

Re: Suddenly cannot send email but can receive

<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=320&group=comp.mail.eudora.ms-windows#320

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:6214:240c:b0:42c:728e:8a55 with SMTP id fv12-20020a056214240c00b0042c728e8a55mr9027493qvb.126.1645878927846;
Sat, 26 Feb 2022 04:35:27 -0800 (PST)
X-Received: by 2002:ac8:5f06:0:b0:2d4:3b47:1bb1 with SMTP id
x6-20020ac85f06000000b002d43b471bb1mr10707589qta.107.1645878927683; Sat, 26
Feb 2022 04:35:27 -0800 (PST)
Path: i2pn2.org!i2pn.org!aioe.org!feeder1.feed.usenet.farm!feed.usenet.farm!2.eu.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 04:35:27 -0800 (PST)
In-Reply-To: <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:75f9:ee2d:235e:80cb;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:75f9:ee2d:235e:80cb
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sat, 26 Feb 2022 12:35:27 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 99
 by: DaveH2 - Sat, 26 Feb 2022 12:35 UTC

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.

Re: Suddenly cannot send email but can receive

<5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=321&group=comp.mail.eudora.ms-windows#321

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ac8:714b:0:b0:2d7:fbb2:eb05 with SMTP id h11-20020ac8714b000000b002d7fbb2eb05mr10887542qtp.380.1645892449405;
Sat, 26 Feb 2022 08:20:49 -0800 (PST)
X-Received: by 2002:a05:620a:2a04:b0:648:d0c4:23a7 with SMTP id
o4-20020a05620a2a0400b00648d0c423a7mr7539665qkp.399.1645892449152; Sat, 26
Feb 2022 08:20:49 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 08:20:48 -0800 (PST)
In-Reply-To: <c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 16:20:49 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 127
 by: Joshua Reichek - Sat, 26 Feb 2022 16:20 UTC

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

Re: Suddenly cannot send email but can receive

<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=322&group=comp.mail.eudora.ms-windows#322

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a37:e303:0:b0:47d:7548:23fa with SMTP id y3-20020a37e303000000b0047d754823famr7844687qki.152.1645892992619;
Sat, 26 Feb 2022 08:29:52 -0800 (PST)
X-Received: by 2002:ac8:4e8c:0:b0:2de:a2f9:15cb with SMTP id
12-20020ac84e8c000000b002dea2f915cbmr10194883qtp.385.1645892992458; Sat, 26
Feb 2022 08:29:52 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!2.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 08:29:52 -0800 (PST)
In-Reply-To: <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 16:29:52 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 133
 by: Joshua Reichek - Sat, 26 Feb 2022 16:29 UTC

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

Re: Suddenly cannot send email but can receive

<d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=323&group=comp.mail.eudora.ms-windows#323

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:620a:24c1:b0:662:e76f:4e4d with SMTP id m1-20020a05620a24c100b00662e76f4e4dmr186326qkn.771.1645897151514;
Sat, 26 Feb 2022 09:39:11 -0800 (PST)
X-Received: by 2002:ad4:4ea4:0:b0:42b:f8f2:6ba4 with SMTP id
ed4-20020ad44ea4000000b0042bf8f26ba4mr9705753qvb.4.1645897151230; Sat, 26 Feb
2022 09:39:11 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 09:39:10 -0800 (PST)
In-Reply-To: <06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:75bc:53c1:32df:f517;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:75bc:53c1:32df:f517
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sat, 26 Feb 2022 17:39:11 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 144
 by: DaveH2 - Sat, 26 Feb 2022 17:39 UTC

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.

Re: Suddenly cannot send email but can receive

<d49b798b-c45b-4c7d-a14e-3eb7bf77ab3en@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=324&group=comp.mail.eudora.ms-windows#324

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ac8:5ace:0:b0:2c9:f9d2:146 with SMTP id d14-20020ac85ace000000b002c9f9d20146mr11688821qtd.216.1645897983073;
Sat, 26 Feb 2022 09:53:03 -0800 (PST)
X-Received: by 2002:a37:ac07:0:b0:649:63d5:6154 with SMTP id
e7-20020a37ac07000000b0064963d56154mr7439045qkm.274.1645897982900; Sat, 26
Feb 2022 09:53:02 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 09:53:02 -0800 (PST)
In-Reply-To: <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d49b798b-c45b-4c7d-a14e-3eb7bf77ab3en@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 17:53:03 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 157
 by: Joshua Reichek - Sat, 26 Feb 2022 17:53 UTC

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)


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=325&group=comp.mail.eudora.ms-windows#325

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:6214:1c8e:b0:432:4f21:aedb with SMTP id ib14-20020a0562141c8e00b004324f21aedbmr9492157qvb.74.1645898228896;
Sat, 26 Feb 2022 09:57:08 -0800 (PST)
X-Received: by 2002:a37:87c7:0:b0:5e9:562c:3cfa with SMTP id
j190-20020a3787c7000000b005e9562c3cfamr7665755qkd.440.1645898228721; Sat, 26
Feb 2022 09:57:08 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 09:57:08 -0800 (PST)
In-Reply-To: <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 17:57:08 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 152
 by: Joshua Reichek - Sat, 26 Feb 2022 17:57 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=326&group=comp.mail.eudora.ms-windows#326

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:620a:1729:b0:648:a992:cd47 with SMTP id az41-20020a05620a172900b00648a992cd47mr8418851qkb.53.1645915735753;
Sat, 26 Feb 2022 14:48:55 -0800 (PST)
X-Received: by 2002:a05:620a:280f:b0:60c:971c:a596 with SMTP id
f15-20020a05620a280f00b0060c971ca596mr8046202qkp.518.1645915735561; Sat, 26
Feb 2022 14:48:55 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 14:48:55 -0800 (PST)
In-Reply-To: <29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:ed48:73bb:2cdf:f684;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:ed48:73bb:2cdf:f684
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sat, 26 Feb 2022 22:48:55 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 168
 by: DaveH2 - Sat, 26 Feb 2022 22:48 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=327&group=comp.mail.eudora.ms-windows#327

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ad4:5041:0:b0:432:360a:887d with SMTP id m1-20020ad45041000000b00432360a887dmr9907011qvq.0.1645916999740;
Sat, 26 Feb 2022 15:09:59 -0800 (PST)
X-Received: by 2002:a0c:d80a:0:b0:42c:37de:466d with SMTP id
h10-20020a0cd80a000000b0042c37de466dmr9891360qvj.56.1645916999594; Sat, 26
Feb 2022 15:09:59 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!3.eu.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 15:09:59 -0800 (PST)
In-Reply-To: <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 23:09:59 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 177
 by: Joshua Reichek - Sat, 26 Feb 2022 23:09 UTC

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?


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=328&group=comp.mail.eudora.ms-windows#328

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:620a:258e:b0:5f1:8799:7e with SMTP id x14-20020a05620a258e00b005f18799007emr8278615qko.333.1645917859285;
Sat, 26 Feb 2022 15:24:19 -0800 (PST)
X-Received: by 2002:a05:6214:2b07:b0:432:f7e6:e443 with SMTP id
jx7-20020a0562142b0700b00432f7e6e443mr1864281qvb.125.1645917859130; Sat, 26
Feb 2022 15:24:19 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sat, 26 Feb 2022 15:24:18 -0800 (PST)
In-Reply-To: <2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sat, 26 Feb 2022 23:24:19 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 185
 by: Joshua Reichek - Sat, 26 Feb 2022 23:24 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=329&group=comp.mail.eudora.ms-windows#329

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a0c:e6c5:0:b0:42c:d5f:7e4c with SMTP id l5-20020a0ce6c5000000b0042c0d5f7e4cmr11268712qvn.93.1645965848608;
Sun, 27 Feb 2022 04:44:08 -0800 (PST)
X-Received: by 2002:a37:785:0:b0:54e:39dc:2c28 with SMTP id
127-20020a370785000000b0054e39dc2c28mr9028998qkh.109.1645965848355; Sun, 27
Feb 2022 04:44:08 -0800 (PST)
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 04:44:08 -0800 (PST)
In-Reply-To: <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:f57b:a7c3:d56d:245b;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:f57b:a7c3:d56d:245b
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sun, 27 Feb 2022 12:44:08 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 199
 by: DaveH2 - Sun, 27 Feb 2022 12:44 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=330&group=comp.mail.eudora.ms-windows#330

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ac8:5c43:0:b0:2de:4ac9:6c62 with SMTP id j3-20020ac85c43000000b002de4ac96c62mr13629041qtj.465.1645978590856;
Sun, 27 Feb 2022 08:16:30 -0800 (PST)
X-Received: by 2002:ad4:554e:0:b0:433:24ca:13db with SMTP id
v14-20020ad4554e000000b0043324ca13dbmr962706qvy.29.1645978590696; Sun, 27 Feb
2022 08:16:30 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 08:16:30 -0800 (PST)
In-Reply-To: <bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sun, 27 Feb 2022 16:16:30 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Joshua Reichek - Sun, 27 Feb 2022 16:16 UTC

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:


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=331&group=comp.mail.eudora.ms-windows#331

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:622a:514:b0:2de:7415:8086 with SMTP id l20-20020a05622a051400b002de74158086mr14097548qtx.464.1645985022931;
Sun, 27 Feb 2022 10:03:42 -0800 (PST)
X-Received: by 2002:ac8:4e8c:0:b0:2de:a2f9:15cb with SMTP id
12-20020ac84e8c000000b002dea2f915cbmr13144158qtp.385.1645985022753; Sun, 27
Feb 2022 10:03:42 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 10:03:42 -0800 (PST)
In-Reply-To: <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:a4f0:16af:228c:fbd5;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:a4f0:16af:228c:fbd5
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sun, 27 Feb 2022 18:03:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 233
 by: DaveH2 - Sun, 27 Feb 2022 18:03 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=332&group=comp.mail.eudora.ms-windows#332

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a37:311:0:b0:648:c4dc:f9f2 with SMTP id 17-20020a370311000000b00648c4dcf9f2mr9619798qkd.500.1645992539827;
Sun, 27 Feb 2022 12:08:59 -0800 (PST)
X-Received: by 2002:ad4:554e:0:b0:433:24ca:13db with SMTP id
v14-20020ad4554e000000b0043324ca13dbmr1379560qvy.29.1645992539632; Sun, 27
Feb 2022 12:08:59 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 12:08:59 -0800 (PST)
In-Reply-To: <4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sun, 27 Feb 2022 20:08:59 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 245
 by: Joshua Reichek - Sun, 27 Feb 2022 20:08 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=333&group=comp.mail.eudora.ms-windows#333

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:620a:1472:b0:62c:e3fb:337c with SMTP id j18-20020a05620a147200b0062ce3fb337cmr9774437qkl.495.1645993090092;
Sun, 27 Feb 2022 12:18:10 -0800 (PST)
X-Received: by 2002:a0c:fdc2:0:b0:432:590c:b3e5 with SMTP id
g2-20020a0cfdc2000000b00432590cb3e5mr11984543qvs.123.1645993089915; Sun, 27
Feb 2022 12:18:09 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 12:18:09 -0800 (PST)
In-Reply-To: <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sun, 27 Feb 2022 20:18:10 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 260
 by: Joshua Reichek - Sun, 27 Feb 2022 20:18 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=334&group=comp.mail.eudora.ms-windows#334

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ac8:714b:0:b0:2d7:fbb2:eb05 with SMTP id h11-20020ac8714b000000b002d7fbb2eb05mr14249017qtp.380.1645997784935;
Sun, 27 Feb 2022 13:36:24 -0800 (PST)
X-Received: by 2002:ac8:5850:0:b0:2dd:9260:c4f9 with SMTP id
h16-20020ac85850000000b002dd9260c4f9mr14589470qth.446.1645997784758; Sun, 27
Feb 2022 13:36:24 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 13:36:24 -0800 (PST)
In-Reply-To: <58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sun, 27 Feb 2022 21:36:24 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 271
 by: Joshua Reichek - Sun, 27 Feb 2022 21:36 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=335&group=comp.mail.eudora.ms-windows#335

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:6214:27ca:b0:432:c4cd:4e90 with SMTP id ge10-20020a05621427ca00b00432c4cd4e90mr8337969qvb.116.1645999783486;
Sun, 27 Feb 2022 14:09:43 -0800 (PST)
X-Received: by 2002:ac8:4e8c:0:b0:2de:a2f9:15cb with SMTP id
12-20020ac84e8c000000b002dea2f915cbmr13670007qtp.385.1645999783284; Sun, 27
Feb 2022 14:09:43 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 14:09:42 -0800 (PST)
In-Reply-To: <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=90.199.32.180; posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 90.199.32.180
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com> <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Sun, 27 Feb 2022 22:09:43 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: DaveH2 - Sun, 27 Feb 2022 22:09 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=336&group=comp.mail.eudora.ms-windows#336

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a37:a597:0:b0:4e0:e232:1d12 with SMTP id o145-20020a37a597000000b004e0e2321d12mr10103972qke.542.1646002635630;
Sun, 27 Feb 2022 14:57:15 -0800 (PST)
X-Received: by 2002:a05:622a:4289:b0:2d4:69a4:18bd with SMTP id
cr9-20020a05622a428900b002d469a418bdmr14285016qtb.278.1646002635444; Sun, 27
Feb 2022 14:57:15 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 14:57:15 -0800 (PST)
In-Reply-To: <e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=75.101.37.162; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 75.101.37.162
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com> <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
<e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Sun, 27 Feb 2022 22:57:15 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 303
 by: Joshua Reichek - Sun, 27 Feb 2022 22:57 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<edbeaf98-130d-4997-b72a-53091636fb97n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=340&group=comp.mail.eudora.ms-windows#340

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:622a:58f:b0:2de:92c7:8859 with SMTP id c15-20020a05622a058f00b002de92c78859mr14688830qtb.191.1646008686341;
Sun, 27 Feb 2022 16:38:06 -0800 (PST)
X-Received: by 2002:a05:620a:1a87:b0:648:e544:3a82 with SMTP id
bl7-20020a05620a1a8700b00648e5443a82mr10078134qkb.619.1646008686118; Sun, 27
Feb 2022 16:38:06 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Sun, 27 Feb 2022 16:38:05 -0800 (PST)
In-Reply-To: <4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:9562:5ef6:30c:c663;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:9562:5ef6:30c:c663
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com> <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
<e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com> <4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <edbeaf98-130d-4997-b72a-53091636fb97n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Mon, 28 Feb 2022 00:38:06 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: DaveH2 - Mon, 28 Feb 2022 00:38 UTC

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.


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<b9588046-3674-4082-a30d-88efcfb4f49en@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=341&group=comp.mail.eudora.ms-windows#341

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:a05:6214:5188:b0:433:3463:709f with SMTP id kl8-20020a056214518800b004333463709fmr5914762qvb.59.1646171676633;
Tue, 01 Mar 2022 13:54:36 -0800 (PST)
X-Received: by 2002:a05:6214:2684:b0:435:1ab6:eac8 with SMTP id
gm4-20020a056214268400b004351ab6eac8mr753758qvb.4.1646171676422; Tue, 01 Mar
2022 13:54:36 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Tue, 1 Mar 2022 13:54:36 -0800 (PST)
In-Reply-To: <edbeaf98-130d-4997-b72a-53091636fb97n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=206.121.7.90; posting-account=MxGjFgoAAAC_Zo5GKbutiTIUl0FcKoTN
NNTP-Posting-Host: 206.121.7.90
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com> <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
<e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com> <4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>
<edbeaf98-130d-4997-b72a-53091636fb97n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b9588046-3674-4082-a30d-88efcfb4f49en@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: reic...@dslextreme.com (Joshua Reichek)
Injection-Date: Tue, 01 Mar 2022 21:54:36 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 339
 by: Joshua Reichek - Tue, 1 Mar 2022 21:54 UTC

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


Click here to read the complete article
Re: Suddenly cannot send email but can receive

<c3d134c5-e5ec-4fca-a76e-33e0e3fe6c03n@googlegroups.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=342&group=comp.mail.eudora.ms-windows#342

  copy link   Newsgroups: comp.mail.eudora.ms-windows
X-Received: by 2002:ae9:e114:0:b0:609:b256:ee5 with SMTP id g20-20020ae9e114000000b00609b2560ee5mr16248839qkm.93.1646224094815;
Wed, 02 Mar 2022 04:28:14 -0800 (PST)
X-Received: by 2002:a05:6214:f2d:b0:432:dc5f:ea15 with SMTP id
iw13-20020a0562140f2d00b00432dc5fea15mr15337259qvb.81.1646224094644; Wed, 02
Mar 2022 04:28:14 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.mail.eudora.ms-windows
Date: Wed, 2 Mar 2022 04:28:14 -0800 (PST)
In-Reply-To: <b9588046-3674-4082-a30d-88efcfb4f49en@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2a02:c7f:dd74:3c00:d4df:faf3:c869:568c;
posting-account=NmsmigoAAAD9jGIPiCwbttyA37RxNlkL
NNTP-Posting-Host: 2a02:c7f:dd74:3c00:d4df:faf3:c869:568c
References: <9e445947-bcf5-4d4d-a24e-075dd0169f9dn@googlegroups.com>
<33dfe5ee-1eca-458b-8a8a-b018ee6c186an@googlegroups.com> <fbd92196-078a-4464-88cf-c13888c28e26n@googlegroups.com>
<cdaff819-e568-45d8-9039-96f9ddac77edn@googlegroups.com> <0f61c6df-621a-40ad-82e7-44ef60894ad3n@googlegroups.com>
<c74d0100-0d35-4e1f-aa49-3fb5bce0c657n@googlegroups.com> <5c0cfc77-deef-47e5-99ac-1d03cef2f9een@googlegroups.com>
<06b783c7-b1c2-453f-ba26-15ca8bb15e59n@googlegroups.com> <d5ffb8a5-8087-4cc3-b90e-10ae453f4f33n@googlegroups.com>
<29bd1345-d1b2-4873-b928-10add2736c83n@googlegroups.com> <f5d72fa6-fc58-4024-b15e-dd64e277198an@googlegroups.com>
<2cbbaad8-8abe-4bd4-a5aa-c57b182f76fdn@googlegroups.com> <b66dfe73-1799-488b-a2ba-ec0fb5100c0dn@googlegroups.com>
<bbd0d75c-e165-4859-82c8-dec0ebb12933n@googlegroups.com> <b8cb56dd-5e9a-458b-b421-14972a0ae937n@googlegroups.com>
<4d38e465-1a9b-4611-a511-f314ee85dbc4n@googlegroups.com> <57f2589d-b155-477b-850b-de23c97f4c70n@googlegroups.com>
<58b6aa4b-3915-4a1e-9a62-c01fb8b52b8fn@googlegroups.com> <99bd61ee-e064-4ac7-b7c7-3d5d958e00dfn@googlegroups.com>
<e61afa33-cc46-4475-b3bc-be3607debc2fn@googlegroups.com> <4f08c126-cb83-423e-bce3-512a0d6b68dfn@googlegroups.com>
<edbeaf98-130d-4997-b72a-53091636fb97n@googlegroups.com> <b9588046-3674-4082-a30d-88efcfb4f49en@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c3d134c5-e5ec-4fca-a76e-33e0e3fe6c03n@googlegroups.com>
Subject: Re: Suddenly cannot send email but can receive
From: dav...@sky.com (DaveH2)
Injection-Date: Wed, 02 Mar 2022 12:28:14 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 358
 by: DaveH2 - Wed, 2 Mar 2022 12:28 UTC

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.


Click here to read the complete article
Pages:12
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor