SMTP problems??

[#1]

Seems I have the same problem, (see my Forum entry "Total failure of metronet email service") and it seems to have started at the same time as for others.

My Thunderbird config uses UN: myemail, Port 110 for mail.metronet.co.uk and UN: myemail, Port 25 for smtp.metronet.co.uk

Are these now incorrect? If so what should they be? Since they did work and now seems not to work why were we not notified of the change?

I tried to re-setup Thunderbird on my Samsung Mobile but disconnected Wi-Fi  and connected via the mobile data network therefore avoiding a potential fixed IP problem (ie not going via my router). I got the same error msg on smtp setup as before suggesting it's not an IP blacklisting problem indicated by the error msg.

[#2]

On my desktop Thunderbird setup I change UN to: myemail@metronet.co.uk for both mail.metronet.co.uk and smtp.metronet.co.uk and restarted Thunderbird.

Result: it now reads emails with other config settings unchanged and original PW supplied when requested. But will not send emails. Progress!

[#3]

Using webmail this morning I can log in, retrieve and send new emails using my username without the @metronet.co.uk extension and my password.

Using Outlook I can retrieve but not send any emails using my username with the @metronet.co.uk extension and password.

If I remove the @metronet.co.uk extension within the Outlook settings, using the same password as it was two days ago, I cannot retrieve or send emails.

Something has changed, presumably by PlusNet.

[#4]

Thanks again Townman however if I am reading the detail correctly, the only apparent reference to a server in the certificate indicates 'mail.enmail.co' ( 2.23.140.1.2.1?) The certificate is issued by R10 and is still valid within the dates shown.

Tracert to mail.enmail.co resolves to 91.204.208.195 after which the host is unreachable probably because it is set not to respond to ping requests.

2.23.140.1.2.1 is not resolvable

[#5]

This is most helpful. I’m discussing the issues in the SU space, I will add this onto that discussion.

[#6]

@Townman 

nslookup shows theses results for the  IP Addresses

nslookup mail.metronet.co.uk
Server:  UnKnown
Address:  192.168.10.1

Non-authoritative answer:
Name:    mail.plusnet.enmail.co
Address:  91.204.208.26
Aliases:  mail.metronet.co.uk

nslookup smtp.metronet.co.uk
Server:  UnKnown
Address:  192.168.10.1

Non-authoritative answer:
Name:    mail.plusnet.enmail.co
Address:  91.204.208.26
Aliases:  smtp.metronet.co.uk
          relay.metronet.co.uk

This issue is very much like the free-online email problem I had earlier in the week

[#7]

using nslookup for both mail.metronet.co.uk & smtp.metronet.co.uk I get similar to @Townman, ie

$ nslookup mail.metronet.co.uk

Non-authoritative answer:
mail.metronet.co.uk     canonical name = mail.plusnet.enmail.co.
Name:   mail.plusnet.enmail.co
Address: 91.204.208.26

$ nslookup smtp.metronet.co.uk

Non-authoritative answer:
smtp.metronet.co.uk     canonical name = relay.metronet.co.uk.
relay.metronet.co.uk    canonical name = mail.plusnet.enmail.co.
Name:   mail.plusnet.enmail.co
Address: 91.204.208.26

The differences maybe due to different versions of nslookup - but in general look the same.

I have now updated the config on my Samsung K9 email system to UN: myemail@metronet.co.uk and it to will now receive but not send.

On PN Webmail  under Identities/myemail/myemail.metronet.co.uk/email: myemail@metronet.co.uk

And this will both sent and receive emails. I might expect this since the code is running in a totally different environment and accesses to mail and smtp servers may "effectively" be local.

I don't want to use PN Webmail just to send emails!

[#8]

I have tried to login to metronet.co.uk using Telnet on port 587.
I am able to go through the authentication process but get 535 Authentication Error on submitting the B64 encoded account password. I will now try on port 25....

[#9]

UPDATE: SSL/TLS is NOT available for Metronet users.

Encryption should be set to NONE.  That will eliminate the certificate issues.

[#10]

Even with NONE - it doesn't fix the sending issue.

The disappointing thing with this is the TOTAL lack of response from PN staff.

They are active on other similar email community posts but not this one.  The active members asking for PM's when PN email issues are occurring fails to even acknowledge my PM.

My message highlighting the issue along with my open ticket about PORT 587 SMTP issues from last year also go unanswered.

Very disappointing when clearly the issue is of their causing!! 

[#11]

Thanks but despite reverting to the original port 25 and setting no SSL/TTS sending emails is still not possible.

Clearly the server is accepting authentication to successfully retrieve emails but not outgoing messages. The ball is still in PN's court and we are now 4 days into the issue with no real prospect of a resolution.
I dont mean to be ungrateful but PN have obviously changed something in the configuration which is now seriously impacting the service that I rely upon and they need to step up and get it resolved.

[#12]

Two different servers!

I have poked the issue again!

[#13]

thank you!

[#14]

Thanks Townman.

Sorry to be the squeaky wheel....

😞

[#15]

Just to clarify the current situation ....

Is everyone able to get mail via their client now leaving the issue sending even with SSL off on port 25 on outbound?