al67
Superfast
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: Email not working since 15/04/24
Well, it's mysteriously and/or magically working again with no changes to my settings. Congratulations to VM in fixing this in just 10 days, instead of the customary 2 weeks, and for keeping us updated. LOL! 🤣 Seriously, I think VM seriously need to look at the purpose of this forum, given the total lack of useful input from the staff. Oh, couple of things, you may need to turn off "require secure authentication" or you get a "Server reports error. The response is: 5.1.0 Authentication Required (VM401)" which is either a server problem, or my email client has got it's settings flipped. Weird. Also, the ntlworld server on port 25 still woks, but delivery is very slow Until next time, adios, it's been fun. Not as much fun as the great gmail fustercluck back in the day though 🙂506Views0likes0CommentsRe: Email not working since 15/04/24
A quick heads-up for anyone still still struggling with an ntlworld email address ... Incoming mail can be retrieved from pop.ntlworld.com using your user name (exclude the @ntlworld.com) on port 110 Outgoing mail can be sent via smtp.ntlworld.com using no encryption on port 25 This might work with blueyonder with obvious changes. It's like we've gone back 10 years 🙂 Quite why VM have provided no updates after more than a week is unbelievable and unacceptable. Guys, get a grip, let us know what the hell is going on 😞731Views1like0CommentsEmail 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 🙂5.8KViews0likes35CommentsRe: IP Address apparently blocked and according to second line technical help only three options to resolve
@Graham_A What I was suggesting was that as there is an ongoing issue with SMTP that it wasn't worth chasing down rabbit holes in that regard 🙂 My IP address is blocked by SORBS for some reason, but I haven't noticed any problems. Just wondering if repeated refused connections by the VM SMTP server caused it to be blacklisted? My older (ancient!) email client supports TLS 1.2 and works fine with another SMTP server that mandates 1.2, though it does appear that VM no longer supports older versions, and I have no idea how long that has been the case, so may not be recent.Seems that VM should be accepting 1.2 though. Whatever, would be good to know if whatever happened on the 15th was a deliberate change or if someone unplugged the server to plug their phone charger in 😉 Anyway, I think I'm out. I don't use VM email at all, just use the SMTP server as it's convenient and I'm paying for it already 🙂1.1KViews0likes0CommentsRe: Email not working since 15/04/24
@Ashleigh_C, my settings are fine.Read all of the other threads. Your SMTP server is refusing connections. A lot of investiagtion has been done by those of us suffering, so the ops team have plenty to get started with. I understand that 'the relevant departments' were notified of the issue on Tuesday. Any updates from them?1.5KViews0likes3CommentsRe: IP Address apparently blocked and according to second line technical help only three options to resolve
A lot of people have the same SMTP ptoblem, just look at the number of threads on the same subject! VM are apparently aware, but the only official replies here are garbage as they haven't read all of the details. Help line is spewing garbage too,don't go there! Only option seems to be to wait the customary two weeks until it suddenly mysteriously fixes itself 😉1.1KViews0likes2CommentsRe: Outlook e-mail error (0x800CCC1A) :
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 [REMOVED], 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 intact1.2KViews0likes1CommentRe: Email not working since 15/04/24
I'm wondering if the SMTP server is now requiring TLS 1.3 - Older clients like mine only support 1.2 .If this is the case, some notice and impact assessment would have been useful. Oh, POP still works on ntlworld port 110 with no fancy tricks required, so I don't think SMTP/POP have been dropped in favour of IMAP. Whatever, the number of threads continues to grow. Might be nice if a superuser/mod could flag this issue 🙂1.9KViews0likes7CommentsRe: Outlook SMTP SSL Error
Similar issue (with a different mail client) started yesterday 16/04/24, 10:06:15: SEND - sending mail message(s) - 1 message(s) in queue 16/04/24, 10:06:15: SEND - Connecting to SMTP server smtp.virginmedia.com on port 465 16/04/24, 10:06:15: SEND - Initiating TLS handshake !16/04/24, 10:06:15: SEND - Server reports TLS error: Handshake failure. Doesn't get far enough for the protocol log to record anything.: Haven't changed anything, been working for years. Will investigate more later and perhaps start a new thread as I suspect this is a change in server configuration rather than an individual client issue.692Views1like4Comments