Since Monday morning I have been unable to submit e-mail to Namesco's SMTP server us2.smtp.mailhostbox.com (which my personal domains have aliases for). This problem affects all device connected via my Virgin Hub3 - I've tried 3 computers with wired ethernet connections and my iPad and phone which are both on Wifi.In the Windows command prompt I have determined I am unable to telnet to this server on any of its SMTP ports 25, 465 and 587, using any of its four IPv4 addresses returned by nslookup.I can send emails using the same account settings on my phone when I turn of the Wifi so it uses its 4G SIM rather than Virgin Media. I can also send emails via my Virgin Media Hub3 and an account setup to use its own server smtp.ntlworld.com and another server managed by a workplace.I assume either my Hub3's WAN IP address or Namesco's SMTP server is on some blacklist. I have contacted Namesco's support and they have said it's not at their end. I've rebooted my Hub3 twice but both times it has come back with the same IP address.

Hi detrain Welcome to the community forums Sorry to hear of your email concerns. Does your IP come up on as blacklisted at all when checked online? You can use checkers such as Spamhaus to see if it is the IP that might be causing the issue. Keep us posted with what you find out and we'll look to assist further if needed

My hub's IP address has been 80.5.192.32 since this problem first arose, overnight between Sunday 2nd and Monday 3rd June. I don't know if it was different before, but I can find no explanation other than IP blacklisting for this problem. IP address 80.5.192.32 is only on the Spamhaus PBL, which they say is normal for broadband ISP addresses. I know of no other reference to it online.The NamesCo SMTP server has 4 IP addresses: 208.91.198.143, 208.91.199.225, 208.91.199.223, 208.91.199.224. The Spamhaus website indicates no issues with any of these.My mail client (Thunderbird) reports an unhelpful generic error, but I have established using command-line tools - telnet, curl and 'openssl s_client' - that I cannot connect raw TCP sockets to the 4 server IPv4 addresses on any of TCP ports 25, 465 or 587 from a computer connected to the internet via my Virgin Media Hub3. All devices connected via either wired ethernet or wi-fi are similarly affected.I passed my Hub3 IP address 80.5.192.32 onto Namesco, but they have closed their support ticket, insisting that their server is not blocking me from connecting to it from that IP address and telling me to raise the issue with Virgin Media instead.

You've gone beyond my level of internet routing expertise, however I use Names/Namesco as my domain host - including use of their authenticated SMTP across my numerous devices.No such problems here, so I suspect the blacklisting idea doesn't hold complete water. But others on here know far better than I on that.

Cannot connect to Namesco SMTP server | Virgin Media Community

19 Replies

Carley_S
Forum Team
11 months ago
Hi detrain

Welcome to the community forums

Sorry to hear of your email concerns. Does your IP come up on as blacklisted at all when checked online? You can use checkers such as Spamhaus to see if it is the IP that might be causing the issue.

Keep us posted with what you find out and we'll look to assist further if needed
detrain
Joining in
11 months ago
My hub's IP address has been 80.5.192.32 since this problem first arose, overnight between Sunday 2nd and Monday 3rd June. I don't know if it was different before, but I can find no explanation other than IP blacklisting for this problem. IP address 80.5.192.32 is only on the Spamhaus PBL, which they say is normal for broadband ISP addresses. I know of no other reference to it online.
The NamesCo SMTP server has 4 IP addresses: 208.91.198.143, 208.91.199.225, 208.91.199.223, 208.91.199.224. The Spamhaus website indicates no issues with any of these.
My mail client (Thunderbird) reports an unhelpful generic error, but I have established using command-line tools - telnet, curl and 'openssl s_client' - that I cannot connect raw TCP sockets to the 4 server IPv4 addresses on any of TCP ports 25, 465 or 587 from a computer connected to the internet via my Virgin Media Hub3. All devices connected via either wired ethernet or wi-fi are similarly affected.
I passed my Hub3 IP address 80.5.192.32 onto Namesco, but they have closed their support ticket, insisting that their server is not blocking me from connecting to it from that IP address and telling me to raise the issue with Virgin Media instead.
japitts
Very Insightful Person
11 months ago
You've gone beyond my level of internet routing expertise, however I use Names/Namesco as my domain host - including use of their authenticated SMTP across my numerous devices.
No such problems here, so I suspect the blacklisting idea doesn't hold complete water. But others on here know far better than I on that.

Client62

Alessandro Volta

11 months ago

Do Ping and Tracert return results for us2.smtp.mailhostbox.com ?

We can ping us2.smtp.mailhostbox.com and get replies, it is a little slow but that may just be the distance.

C:\Users\Philip>ping us2.smtp.mailhostbox.com

Pinging us2.smtp.mailhostbox.com [208.91.199.225] with 32 bytes of data:
Reply from 208.91.199.225: bytes=32 time=195ms TTL=47
Reply from 208.91.199.225: bytes=32 time=191ms TTL=47
Reply from 208.91.199.225: bytes=32 time=193ms TTL=47
Reply from 208.91.199.225: bytes=32 time=197ms TTL=47

Ping statistics for 208.91.199.225:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 191ms, Maximum = 197ms, Average = 194ms

detrain

Joining in

11 months ago

Yes I can ping and tracert it. Only the TCP connect attempts appear to be blocked by a firewall and fail after 80 to 90 seconds. The delay before getting an error in Thunderbird is similar.

Microsoft Windows [Version 10.0.19045.4412]
(c) Microsoft Corporation. All rights reserved.

E:\>ping us2.smtp.mailhostbox.com

Pinging us2.smtp.mailhostbox.com [208.91.199.224] with 32 bytes of data:
Reply from 208.91.199.224: bytes=32 time=174ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=178ms TTL=49

Ping statistics for 208.91.199.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 178ms, Average = 175ms

E:\>tracert us2.smtp.mailhostbox.com

Tracing route to us2.smtp.mailhostbox.com [208.91.199.224]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router [192.168.0.1]
2 * * * Request timed out.
3 14 ms 12 ms 11 ms nrth-core-2b-ae43-650.network.virginmedia.net [6
2.253.128.121]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 16 ms 15 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.25
4.42.174]
8 * * * Request timed out.
9 18 ms 17 ms 15 ms ldn-bb1-link.ip.twelve99.net [62.115.122.188]
10 102 ms 102 ms 103 ms nyk-bb2-link.ip.twelve99.net [62.115.113.20]
11 185 ms 182 ms 191 ms chi-bb2-link.ip.twelve99.net [62.115.132.135]
12 129 ms 129 ms 130 ms omha-b3-link.ip.twelve99.net [62.115.143.183]
13 129 ms 128 ms 128 ms omha-b2-link.ip.twelve99.net [62.115.126.8]
14 183 ms 183 ms 183 ms kanc-bb2-link.ip.twelve99.net [62.115.134.6]
15 169 ms 176 ms 168 ms palo-b24-link.ip.twelve99.net [62.115.125.185]
16 183 ms 184 ms 182 ms salt-b4-link.ip.twelve99.net [62.115.140.53]
17 174 ms 174 ms 174 ms newfolddigital-ic-380138.ip.twelve99-cust.net [8
0.239.167.103]
18 174 ms 174 ms 172 ms 69-195-64-105.unifiedlayer.com [69.195.64.105]
19 174 ms 174 ms 175 ms 162-144-240-177.unifiedlayer.com [162.144.240.17
7]
20 174 ms 173 ms 177 ms 208-91-199-224.unifiedlayer.com [208.91.199.224]


Trace complete.

E:\>telnet us2.smtp.mailhostbox.com 587
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 587: Connect failed

E:\>telnet us2.smtp.mailhostbox.com 465
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 465: Connect failed

E:\>telnet us2.smtp.mailhostbox.com 25
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 25: Connect failed

E:\>

detrain

Joining in

11 months ago

Yes I can ping and tracert it. Only the TCP ports seem to be blocked by a firewall. The telnet commands time out and report the error after about 80-90s, and the delay before Thunderbird reports an error is similar.

Microsoft Windows [Version 10.0.19045.4412]
(c) Microsoft Corporation. All rights reserved.

E:\>ping us2.smtp.mailhostbox.com

Pinging us2.smtp.mailhostbox.com [208.91.199.224] with 32 bytes of data:
Reply from 208.91.199.224: bytes=32 time=174ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=178ms TTL=49

Ping statistics for 208.91.199.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 178ms, Average = 175ms

E:\>tracert us2.smtp.mailhostbox.com

Tracing route to us2.smtp.mailhostbox.com [208.91.199.224]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router [192.168.0.1]
2 * * * Request timed out.
3 14 ms 12 ms 11 ms nrth-core-2b-ae43-650.network.virginmedia.net [6
2.253.128.121]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 16 ms 15 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.25
4.42.174]
8 * * * Request timed out.
9 18 ms 17 ms 15 ms ldn-bb1-link.ip.twelve99.net [62.115.122.188]
10 102 ms 102 ms 103 ms nyk-bb2-link.ip.twelve99.net [62.115.113.20]
11 185 ms 182 ms 191 ms chi-bb2-link.ip.twelve99.net [62.115.132.135]
12 129 ms 129 ms 130 ms omha-b3-link.ip.twelve99.net [62.115.143.183]
13 129 ms 128 ms 128 ms omha-b2-link.ip.twelve99.net [62.115.126.8]
14 183 ms 183 ms 183 ms kanc-bb2-link.ip.twelve99.net [62.115.134.6]
15 169 ms 176 ms 168 ms palo-b24-link.ip.twelve99.net [62.115.125.185]
16 183 ms 184 ms 182 ms salt-b4-link.ip.twelve99.net [62.115.140.53]
17 174 ms 174 ms 174 ms newfolddigital-ic-380138.ip.twelve99-cust.net [8
0.239.167.103]
18 174 ms 174 ms 172 ms 69-195-64-105.unifiedlayer.com [69.195.64.105]
19 174 ms 174 ms 175 ms 162-144-240-177.unifiedlayer.com [162.144.240.17
7]
20 174 ms 173 ms 177 ms 208-91-199-224.unifiedlayer.com [208.91.199.224]


Trace complete.

E:\>telnet us2.smtp.mailhostbox.com 587
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 587: Connect failed

E:\>telnet us2.smtp.mailhostbox.com 465
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 465: Connect failed

E:\>telnet us2.smtp.mailhostbox.com 25
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 25: Connect failed

E:\>

detrain
Joining in
11 months ago
Yes I can ping and tracert it. Only the TCP ports seem to be blocked by a firewall. Connect attempts fail with an error, whether using SMTP client, telnet, etc.
Microsoft Windows [Version 10.0.19045.4412]
(c) Microsoft Corporation. All rights reserved.
E:\>ping us2.smtp.mailhostbox.com
Pinging us2.smtp.mailhostbox.com [208.91.199.224] with 32 bytes of data:
Reply from 208.91.199.224: bytes=32 time=174ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=175ms TTL=49
Reply from 208.91.199.224: bytes=32 time=178ms TTL=49
Ping statistics for 208.91.199.224:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 174ms, Maximum = 178ms, Average = 175ms
E:\>tracert us2.smtp.mailhostbox.com
Tracing route to us2.smtp.mailhostbox.com [208.91.199.224]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router [192.168.0.1]
2 * * * Request timed out.
3 14 ms 12 ms 11 ms nrth-core-2b-ae43-650.network.virginmedia.net [6
2.253.128.121]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 16 ms 15 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.25
4.42.174]
8 * * * Request timed out.
9 18 ms 17 ms 15 ms ldn-bb1-link.ip.twelve99.net [62.115.122.188]
10 102 ms 102 ms 103 ms nyk-bb2-link.ip.twelve99.net [62.115.113.20]
11 185 ms 182 ms 191 ms chi-bb2-link.ip.twelve99.net [62.115.132.135]
12 129 ms 129 ms 130 ms omha-b3-link.ip.twelve99.net [62.115.143.183]
13 129 ms 128 ms 128 ms omha-b2-link.ip.twelve99.net [62.115.126.8]
14 183 ms 183 ms 183 ms kanc-bb2-link.ip.twelve99.net [62.115.134.6]
15 169 ms 176 ms 168 ms palo-b24-link.ip.twelve99.net [62.115.125.185]
16 183 ms 184 ms 182 ms salt-b4-link.ip.twelve99.net [62.115.140.53]
17 174 ms 174 ms 174 ms newfolddigital-ic-380138.ip.twelve99-cust.net [8
0.239.167.103]
18 174 ms 174 ms 172 ms 69-195-64-105.unifiedlayer.com [69.195.64.105]
19 174 ms 174 ms 175 ms 162-144-240-177.unifiedlayer.com [162.144.240.17
7]
20 174 ms 173 ms 177 ms 208-91-199-224.unifiedlayer.com [208.91.199.224]

Trace complete.
E:\>telnet us2.smtp.mailhostbox.com 587
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 587: Connect failed
E:\>telnet us2.smtp.mailhostbox.com 465
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 465: Connect failed
E:\>telnet us2.smtp.mailhostbox.com 25
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 25: Connect failed
E:\>
detrain
Joining in
11 months ago
Yes, ping and tracert work - I've tried posting the command prompt output but the post isn't there when I reload the page. Only TCP connect attempts fail with an error after 80-90s whether using Thunderbird, telnet or any other tool.

detrain

Joining in

11 months ago

Trying again - tracert output;

E:\>tracert us2.smtp.mailhostbox.com

Tracing route to us2.smtp.mailhostbox.com [208.91.199.225]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router [192.168.0.1]
2 * * * Request timed out.
3 17 ms 12 ms 11 ms nrth-core-2b-ae43-650.network.virginmedia.net [6
2.253.128.121]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 26 ms 17 ms aor.uk-lon03a-ri1.network.virginmedia.net [62.25
4.42.174]
8 * * * Request timed out.
9 19 ms 17 ms 16 ms ldn-bb1-link.ip.twelve99.net [62.115.122.188]
10 197 ms 197 ms 196 ms prs-bb1-link.ip.twelve99.net [62.115.135.25]
11 195 ms 195 ms 194 ms ash-bb2-link.ip.twelve99.net [62.115.112.242]
12 127 ms 127 ms 133 ms nyk-bb2-link.ip.twelve99.net [62.115.136.200]
13 182 ms 181 ms 181 ms palo-b24-link.ip.twelve99.net [62.115.122.36]
14 197 ms 196 ms 196 ms salt-b4-link.ip.twelve99.net [62.115.140.53]
15 187 ms 187 ms 189 ms newfolddigital-ic-380138.ip.twelve99-cust.net [8
0.239.167.103]
16 188 ms 187 ms 186 ms 69-195-64-105.unifiedlayer.com [69.195.64.105]
17 187 ms 194 ms 186 ms 162-144-240-173.unifiedlayer.com [162.144.240.17
3]
18 188 ms 190 ms 187 ms 208-91-199-225.unifiedlayer.com [208.91.199.225]


Trace complete.

detrain

Joining in

11 months ago

ping output:

E:\>ping us2.smtp.mailhostbox.com

Pinging us2.smtp.mailhostbox.com [208.91.199.225] with 32 bytes of data:
Reply from 208.91.199.225: bytes=32 time=189ms TTL=49
Reply from 208.91.199.225: bytes=32 time=188ms TTL=49
Reply from 208.91.199.225: bytes=32 time=186ms TTL=49
Reply from 208.91.199.225: bytes=32 time=186ms TTL=49

Ping statistics for 208.91.199.225:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 186ms, Maximum = 189ms, Average = 187ms

detrain

Joining in

11 months ago

telnet output (similar for all of ports 587, 465 and 25 on all 4 IP addresses):

E:\>telnet us2.smtp.mailhostbox.com 587
Connecting To us2.smtp.mailhostbox.com...Could not open connection to the host,
on port 587: Connect failed

Forum Discussion

Cannot connect to Namesco SMTP server

19 Replies

Related Content

Cannot See/connect Home Network Connections

Connection keeps dropping

Ethernet connection

VM connect not connecting hub 4

Virgin connect app