Email problem

In reply to a post by Andrew_W:

Suggestions please!!

Edited by GonePostal (Sat 11-Jun-22 13:03:38)

In reply to a post by Andrew_W:

Error code (0x800CCC67) appears saying the server was found but no response from the server. So I contact by phone my ISP Idnet who says that is an MS error code!! “Try change changing the SMTP port to 587 from 25”. That works for a couple of tries then fails.

I have another Windows 10 PC with Office 2003 and that throws up the same error. I have even tried another router.

In reply to a post by Andrew_W:

An error occurred while sending mail: The mail server sent an incorrect greeting: Cannot connect to SMTP server 212.69.40.22 (212.69.40.22:25), connect error 10060.

In reply to a post by Andrew_W:

Oliver I have no idea! How can you tell?

In reply to a post by Andrew_W:

Thanks all for replies.

First, my email is tied to my ISP . I tried temporally disabling my firewall no improvement.

Sending via Thunderbird worked first time but another attempt with Tbird produced this:

An error occurred while sending mail: The mail server sent an incorrect greeting: Cannot connect to SMTP server 212.69.40.22 (212.69.40.22:25), connect error 10060.

How would I know if my ISP have upgraded their email security and no longer support older versions of TLS?

In reply to a post by Oliver341:

Upgrade Microsoft Office.

Edited by jchamier (Sat 11-Jun-22 16:42:22)

First, my email is tied to my ISP .

In reply to a post by jchamier:

TLS 1.2 is recommended.

Looks as if they still support SMTP over TCP port 25 without encryption, or over port 587 with encryption. TLS 1.2 is recommended.

Some very old info:
https://answers.microsoft.com/en-us/outlook_com/foru...

In reply to a post by Pheasant:

Does the OP's version of Outlook actually support the newer version of TLS 1.2?

In reply to a post by Pheasant:

Andrew - come out of the darkened room, its lovely and sunny out

Is your version of Thunderbird v27 or older?

In reply to a post by Oliver341:

In reply to a post by Pheasant:

Does the OP's version of Outlook actually support the newer version of TLS 1.2?

Outlook 2003 predates TLS 1.2 by several years, and it was not backported to Outlook 2003 as far as I know.

In reply to a post by Oliver341:

In reply to a post by Pheasant:

Does the OP's version of Outlook actually support the newer version of TLS 1.2?

Outlook 2003 predates TLS 1.2 by several years, and it was not backported to Outlook 2003 as far as I know.

Edited by Pheasant (Sat 11-Jun-22 18:31:57)

In reply to a post by Andrew_W:

So how is it that it stopped working three days ago?!!

In reply to a post by bowdon:

If you use Avast anti-virus program there is some bug in the most recent version.

I think someone suggested disabling the mail shield to see if it works.

In reply to a post by Pheasant:

Ah shame about the weather, quite balmy here.

Other than the port number for SMTP - are you using the current server names in the mail client settings, as per the guide here?

In Thunderbird have you enabled STARTTLS in connection security for the outgoing server?

In reply to a post by Pheasant:

If you ping the mail server, do you get any timeouts?

In reply to a post by Pheasant:

Possibly some sort of DNS issue on your Netgear router. Can you ping successfully 212.69.40.22 from your machines?

ipconfig /all produced a quick flash on the screen of something too fast to read!

In reply to a post by Pheasant:

ipconfig /all produced a quick flash on the screen of something too fast to read!

You need to open a a command prompt first, by typing cmd
Then from within the command shell there type ipconfig /all

You can then scroll back through the output of the ipconfig /all command at your leisure

In reply to a post by Pheasant:

ipconfig /all produced a quick flash on the screen of something too fast to read!

You need to open a a command prompt first, by typing cmd
Then from within the command shell there type ipconfig /all

You can then scroll back through the output of the ipconfig /all command at your leisure

In reply to a post by Pheasant:

Reboot the PC and retest by pinging the various servers to make sure there are no timeouts and then check outlook etc again.

Edited by Andrew_W (Mon 13-Jun-22 12:07:59)

In reply to a post by Andrew_W:

A response from everything except 212.69.40.22 and
smtp.idnet.com


All PCs

when I ping smtp.idnet.com I am getting a response from an IPV6 address

In reply to a post by Pheasant:

when I ping smtp.idnet.com I am getting a response from an IPV6 address

Possibly just an OS protocol precedence/preference for ipv6 over ipv4.

Using ping smtp.idnet.com -4 should force it to return an IPv4 addressed response

In reply to a post by Pheasant:

No worries.

When Andrew returns, I think it’s traceroute time to see what’s going on there!

[SMTP server looks healthy from here and I can telnet etc. into it ]

In reply to a post by Andrew_W:

OK Andrew is back!.

Just for fun, I tried tracert smtp.idnet.com whatever that is and got three responses, one from my router, and two more. One from telehouse-gw10-10G.idnet.net and another from telehouse-gw7-10G.idnet.net. Thereafter it timed out repeatedly.

I must confess I do not know what I am talking about!!!!!!!!!!

Edited by Andrue (Mon 13-Jun-22 19:10:07)

In reply to a post by Pheasant:

Have you any thoughts as to what to try next?

In reply to a post by jchamier:

Some very old info:
https://answers.microsoft.com/en-us/outlook_com/foru...

In reply to a post by bsdnazz:

If the users ISP only offers TLS on their email server then I'd expect Outlook to fail to make a secure connection to it and you'd get an error.

In reply to a post by Andrew_W:

Everything else works as it should.

Email was working first thing this morning but now it does not! This fails of course.

ping smtp.idnet.com

1
23
4

Trying 212.69.40.22...
Connected to smtp.idnet.com.Escape character is '^]'.
220 smtp.idnet.com ESMTP Postfix (Debian/GNU)

1
23
45
67
89
1011
12

250-smtp.idnet.com
250-PIPELINING250-SIZE 50000000
250-VRFY250-ETRN
250-STARTTLS250-AUTH PLAIN LOGIN
250-ENHANCEDSTATUSCODES250-8BITMIME
250-DSN250-SMTPUTF8
250 CHUNKING

1

334 VXNlcm5hbWU6

1

334 UGFzc3dvcmQ6

1

235 2.7.0 SMTP350 Authentication successful for user xxx etc, etc.

1

250 2.1.0 <your email address> sender ok

1

250 2.1.5 <<an email address you want to test sending to> recipient ok

1

354 OK

1

250 2.0.0 13MsoX9T0Dbx513OCoWgSm mail accepted for delivery

1

221 2.0.0 smtp.idnet.com closing connection

In reply to a post by billford:

In reply to a post by bsdnazz:

If the users ISP only offers TLS on their email server then I'd expect Outlook to fail to make a secure connection to it and you'd get an error.

The problem is that it accepts a few, then stops... that's why I suggested a nearly full mailbox: when those few have been sent on (or some new incoming ones read) there's a bit more room again.

Although I'm not at all sure that's what the behaviour would be

Edited by Pheasant (Wed 15-Jun-22 09:15:19)

Edited by ashdown (Wed 15-Jun-22 20:51:56)

In reply to a post by ashdown:

One possibility that's not been mentioned so far is a firewall that responds to what it thinks is abuse by blocking inbound connections from a particular IP address for a while. Such rate-limiting and blackhole techniques are often used to protect networks. There's little evidence to suggest this is the cause (although I think it's consistent with the reported symptoms) but it's a possibility to consider.

In reply to a post by Andrew_W:

Well, this problem is driving me mad!!! I just do not know enough about the workings of my PCs to come to a conclusion. IDnet Support we no help as all they said was that there is "a corruption"; of what, I know not. I even tried a borrowed laptop with Office 2016 on it, set it up appropriately and that failed too. Two different routers also.

This morning for example I could send several emails without problem over a period of two hours and then for no reason, failed again.

I am so grateful for all the help offered on this forum, particularly 'Pheasant' who has gone out of their way to solve this. I am going to have to find an expert who can sit at my end of this phone line and sort it all out!!!

In reply to a post by Pheasant:

In reply to a post by ian72:

Do you have data on a mobile phone that you could use to tether one of the devices to? This would allow you to test sending emails via a different connection in case it is related to your IDNet connection. You may also be able to do so if you know someone else who would let you connect to their ISP network to test (or possibly your local library might offer the facility although it may be they would block SMTP as a security measure).

In reply to a post by Pheasant:

Best bet is to reset the passwords for each of you email accounts - just in case one or more has been leaked/compromised and then update the the email client on each device. After that all should be well again.

In reply to a post by Andrew_W:

I have been a customer of IDNet for 16 years so you would think that by now they would know what my invalid credentials are and ignore them 😇

Edited by Andrue (Fri 17-Jun-22 17:21:49)

Edited by APTMAN (Fri 17-Jun-22 17:46:01)

In reply to a post by mking90031:

@Andrew_W,

Here's my 2 cents worth. I would recomend getting yourself a domain and then you can have as many email addresses as you want. I would recommend either 123-Reg or Ionos as they both provide excellent email servers that I have NEVER had an issue with in over 30 years! If you would like a hand getting your own domain then please drop me a message and we can disucuss this further.

Yours,

In reply to a post by Andrue:

In reply to a post by jchamier:

I prefer Microsoft's look and way of working to Google or Yahoo.

In reply to a post by Andrew_W:

OK Changed ISP and all is well. SFSG!

Edited by Oliver341 (Thu 14-Jul-22 09:37:19)

In reply to a post by Oliver341:

In reply to a post by Andrew_W:

OK Changed ISP and all is well. SFSG!

If I am understanding correctly:

- Connecting to smtp.idnet.com using an IDNet connection = bad
- Connecting to smtp.idnet.com using a different connection = good

Is that right?

Edited by Andrew_W (Thu 14-Jul-22 12:13:38)

In reply to a post by ian72:

I googled SFSG and it came up with "Special Forces Support Group". I was about to google again when I realised I assume it is "so far so good" - never seen that used before.

In reply to a post by Andrew_W:

OK Changed ISP and all is well. SFSG!

In reply to a post by Andrew_W:

It did but at the expense of connection speeds. I will blame it on the heat for now, everyone else is. Must be the copper wire between me and the exchange expanding so I am now further away!!!

Amazing how many email contacts I now have to notify.

Again, thanks so much for all your advice 👍 👍

In reply to a post by Andrew_W:

IDNet Webmail still works but can't find an option to divert. Good thought though, thanks.

In reply to a post by Andrew_W:

Could someone please explain why. The BT website is hard work!

In reply to a post by Andrew_W:

With my previous ISP, I regularly achieved over 1meg upload speeds on my 3.4km copper wire connection to the exchange. BT I am told cap upload at 448K?

In reply to a post by Andrew_W:

This, https://broadbandtest.which.co.uk/ however, offers me 1.4Mbps upload??

In reply to a post by jchamier:

You can check your router web pages to see the actual "sync speed" that you are connected at over the wires.

In reply to a post by Andrew_W:

8096Meg 448K

In reply to a post by Andrew_W:

In reply to a post by jchamier:

You can check your router web pages to see the actual "sync speed" that you are connected at over the wires.

8096Meg 448K

In reply to a post by MHC:

Are you sure? an 8Gbps connection is rather fast!