Email not working since 15/04/24
Seems that there a lot of problems being reported since yesterday, 15/04/24, mainly concerned with the SMTP server for outgoing mail.
For me, I get:
16/04/24, 23:04:47: SEND - sending mail message(s) - 1 message(s) in queue
16/04/24, 23:04:47: SEND - Connecting to SMTP server smtp.virginmedia.com on port 465
16/04/24, 23:04:47: SEND - Initiating TLS handshake
!16/04/24, 23:04:47: SEND - Server reports TLS error: Handshake failure.
I've tried protocol logging, but as the initial handshake fails there is nothing to log.
As requested in a couple of the other threads, here's a curl report:
C:\xxx>curl -v smtps://smtp.virginmedia.com
* Trying 84.116.6.19:465...
* Connected to smtp.virginmedia.com (84.116.6.19) port 465 (#0)
* schannel: disabled automatic use of client certificate
< 220 csmtp6-prd-nl1-vmo.edge.unified.services csmtp6-prd-nl1-vmo.edge.unified.services ESMTP server ready
> EHLO xxx
< 250-csmtp6-prd-nl1-vmo.edge.unified.services hello [MOD EDIT: Personal information], pleased to meet you
< 250-HELP
< 250-AUTH LOGIN PLAIN
< 250-SIZE 52000000
< 250-ENHANCEDSTATUSCODES
< 250-PIPELINING
< 250-8BITMIME
< 250 OK
> HELP
< 214-2.0.0 This is csmtp6-prd-nl1-vmo.edge.unified.services ESMTP service help
214-2.0.0 This is csmtp6-prd-nl1-vmo.edge.unified.services ESMTP service help
< 214-2.0.0 To contact postmaster send email to postmaster@virginmedia.com.
214-2.0.0 To contact postmaster send email to postmaster@virginmedia.com.
< 214-2.0.0 For local information send email to Postmaster at your site.
214-2.0.0 For local information send email to Postmaster at your site.
< 214 2.0.0 end of HELP info
214 2.0.0 end of HELP info
* Connection #0 to host smtp.virginmedia.com left intact
I haven't made any changes to my mail client settings for years, as appears to be the case with others. I did try a couple of changes, but nothing worked. I would be wary of what appears to be very poor advice being offered via the helpline regarding changing passwords etc as this appears to be an un-notified change in the server.
So, if you have started having problems, please contribute to this thread and we can hopefully get someone at VM to take a look, rather than wait for the customary 2 weeks before the problem mysteriously fixes itself 🙂