Forum Discussion

JFA8's avatar
JFA8
Joining in
12 months ago

Cant send emails

sending reported error (0x800CCC0F). The connection to the server was interrupted. Contact your ISP

Virgin webmail still works sending and receiving

Normally use Outlook to manage emails and can receive but get above error message when trying too send from Outlook

Spent ages on the phone to virgin and the technician guided me through a procedure for that seemed more  applicable to 'unlocking' my main account, which was not locked. He insisted I use a 4 word 22didget password.

I have recently swapped an old desktop for a new and I have noticed others doing this have had the same error

Can anyone please help as this account has connection to so many vital aspects of our normal lives

PS can anyone advise about the GADGET RESCUE TEAM? The technician I spoke to said he wasn't trained on Outlook but GRT staff were. Any idea of cost? I read it was £10 a month start and stop as you will is this correct?

Any guidance very gratefully received

 

 

 

 

 

 

 

  • JCmacc's avatar
    JCmacc
    Up to speed
    12 months ago

    Several here have had problems sending via Outlook while Virgin mail App worked fine. In my case, my home IP was blocked by Virgin so I couldn't send via the Hub although I could receive e-mail. They've since unblocked it and all is back to normal.

    I was incorrectly pushed to Gadget Support too and turned it down as it wasn't a problem on my kit.

    Sounds like your issue though could be Outlook sending an incorrect password when it talks to the server. As a quick fix you could try resetting the password for your mail account and then make sure Outlook is using the new reset password too.

     

  • coenoby's avatar
    coenoby
    Very Insightful Person
    12 months ago
    JFA8 wrote:

    sending reported error (0x800CCC0F).

    Normally use Outlook to manage emails and can receive but get above error message when trying too send from Outlook

    If you can receive emails ok but not send them that does not sound like a password issue.

    Sadly that Microsoft Outlook error is a particularly unhelpful error message. It just tells you that Outlook closed the connection to the VM SMTP server but gives no indication of why it did that.

    To know why that happened you need to get the exact error message that the VM email server reported to Outlook. There is a relatively simple way to get that by using the Curl command in Microsoft Windows 10 or 11

    Here are the simple steps to take to do that:

    1) Copy the following line of command text and then paste it into a MS Word document (or which ever text editor you prefer) so that you can edit it.

    curl -v smtps://smtp.virginmedia.com -u username:password

    2) Once you have pasted it into Word, replace "username" with your full Virgin Media / Ntlworld / Blueyonder email address,  and replace "password"  with your current password in Outlook (presumably that 4 word password you mentioned).

    So that part should now say something like     "youremailaddy@ntlworld.com:www-xxxxx-yyyy-zzzzz"      It is important to keep the colon  :  and the space before that piece of text exactly as per the original line of text in step 1).

    3) Type    cmd    into the Windows 10 or 11 search bar, press Enter and then open the Command Prompt app.
    4) Copy the full line of text that you just amended in step 2 from the Word document and then paste it where the cursor is blinking in the Command Prompt.

    Then press Enter.

    That will generate many lines of output but all you need to look for towards the end of the output will be a line such as:

    535 5.7.8 Authentication Credentials Invalid (VM300) 

    If you can post that line here then the VM3nn code will give the definitive reason why the connection to the VM server was blocked. On no account post the full text of the output. It will contain your email address and password in an encrypted by easily translated format.

    It is possible that your IP address has been blocked by VM because that issue seems to have started up again recently but the VM3nn error code should remove the need for guessing at what's going on.

    By the way, I would strongly suggest that you forget about using Gadget Rescue.

    Coenoby