Menu
Reply
  • 23
  • 0
  • 0
priesto
On our wavelength
606 Views
Message 31 of 74
Flag for a moderator

Re: Problems sending email using a mail client

@ravenstar68

Is this right?

2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] AUTH LOGIN
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 334 VXNlcm5hbWU6
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] ????????????????????????????????
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 334 UGFzc3dvcmQ6
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] *****
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 235 2.7.0 ... authentication succeeded
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): Authorized to host
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): Connected to host
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] MAIL FROM: <*****>
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 250 2.1.0 <*****> sender ok
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] RCPT TO: <*****>
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 250 2.1.5 <*****> recipient ok
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] DATA
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 354 OK
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx]

0 Kudos
Reply
  • 9.56K
  • 1.06K
  • 4.5K
Superuser
Superuser
595 Views
Message 32 of 74
Flag for a moderator

Re: Problems sending email using a mail client

I'm going to try this one, or I'll never learn.

None of the VM codes in this log are error codes (AFAICS). It looks like the SMTP authentication was successful and remained so. But @ravenstar68 will confirm.


-----------------------

Superuser 18/19.
Use Kudos to say thanks
Tick an answer as "helpful" only when the problem is solved
Please don't send me private messages unless I ask you to.
I do not work for VM. The advice I give is based on my best understanding of VM policy and practice. You rely on it at your own risk.
0 Kudos
Reply
  • 23
  • 0
  • 0
priesto
On our wavelength
592 Views
Message 33 of 74
Flag for a moderator

Re: Problems sending email using a mail client

@HowardML

 

Thanks, miraculously, both my problem email accounts (virginmedia.com and ntlworld.com) are now working so that might account for the fact that there are no longer any error codes!

0 Kudos
Reply
  • 17.24K
  • 949
  • 6.95K
Superuser
Superuser
584 Views
Message 34 of 74
Flag for a moderator

Re: Problems sending email using a mail client

With the exception that we're missing the last part of the send that one actually appears to indicate the mail was sent successfully.

2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] AUTH LOGIN
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 334 VXNlcm5hbWU6
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] ????????????????????????????????
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 334 UGFzc3dvcmQ6
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] *****
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 235 2.7.0 ... authentication succeeded
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): Authorized to host
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): Connected to host
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] MAIL FROM: <*****>
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 250 2.1.0 <*****> sender ok
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] RCPT TO: <*****>
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 250 2.1.5 <*****> recipient ok
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx] DATA
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): <rx> 354 OK
2019.06.18 17:17:20 SMTP (smtp.virginmedia.com): [tx]

The line in green shows your password was accepted.

The following lines show the Mail client sending the sender and recipient addresses.  Both of which were accepted.  Then the client sends the DATA command - this it where is sends the mail itself.

Here's a full send:

2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Begin execution
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Port: 465, Secure: SSL, SPA: no
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Finding host
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Connecting to host
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Securing connection
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Connected to host
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 220 know-smtprelay-10-imp cmsmtp ESMTP server ready
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): [tx] EHLO TIMSDESKTOP
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-know-smtprelay-10-imp hello [80.195.90.23], pleased to meet you
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-HELP
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-AUTH LOGIN PLAIN
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-SIZE 52000000
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-ENHANCEDSTATUSCODES
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-PIPELINING
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250-8BITMIME
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 250 OK
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): Authorizing to server
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): [tx] AUTH LOGIN
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 334 VXNlcm5hbWU6
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): [tx] ??????????????????????????????????
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): <rx> 334 UGFzc3dvcmQ6
2019.06.18 17:38:39 SMTP (smtp.virginmedia.com): [tx] *****
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 235 2.7.0 ... authentication succeeded
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): Authorized to host
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): Connected to host
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): [tx] MAIL FROM: <*****>
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 250 2.1.0 <*****> sender ok
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): [tx] RCPT TO: <*****>
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 250 2.1.5 <*****> recipient ok
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): [tx] DATA
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 354 OK
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): [tx] 
.
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 250 2.0.0 dH83h49Ain5AFdH84hs7zx mail accepted for delivery
2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): End execution
2019.06.18 17:38:40 ???????????@blueyonder.co.uk: ReportStatus: RSF_COMPLETED, hr = 0x00000000

While it doesn't show the actual mail in the log this part:

2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): [tx] 
.

Is where Outlook (or any other mail client) sends a line with a . (and newline) to indicate that the email has been sent.

After that we get the message from the server:

2019.06.18 17:38:40 SMTP (smtp.virginmedia.com): <rx> 250 2.0.0 dH83h49Ain5AFdH84hs7zx mail accepted for delivery

The client normally follows up with a quit command to close the connection gracefully - I suspect Microsoft intentionally omitted that though.

Again the line we were interested in is the line in green - In yours and my cases there is nothing wrong with the outgoing username and password.

Tim

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 17.24K
  • 949
  • 6.95K
Superuser
Superuser
582 Views
Message 35 of 74
Flag for a moderator

Re: Problems sending email using a mail client


@priesto wrote:

@HowardML

 

Thanks, miraculously, both my problem email accounts (virginmedia.com and ntlworld.com) are now working so that might account for the fact that there are no longer any error codes!


Not really a miracle - Despite the fact that they've been silent about it - Virgin Media have been looking into the problem - even last week.

Glad it's working for you though.

Tim

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 9.56K
  • 1.06K
  • 4.5K
Superuser
Superuser
580 Views
Message 36 of 74
Flag for a moderator

Re: Problems sending email using a mail client

OK I wasn't that sophisticated, but I wasn't wrong - at least in principle.

-----------------------

Superuser 18/19.
Use Kudos to say thanks
Tick an answer as "helpful" only when the problem is solved
Please don't send me private messages unless I ask you to.
I do not work for VM. The advice I give is based on my best understanding of VM policy and practice. You rely on it at your own risk.
0 Kudos
Reply
  • 17.24K
  • 949
  • 6.95K
Superuser
Superuser
577 Views
Message 37 of 74
Flag for a moderator

Re: Problems sending email using a mail client


@HowardML wrote:
OK I wasn't that sophisticated, but I wasn't wrong - at least in principle.

You were right in practice as well. Smiley Tongue glad to see what I post hasn't gone to waste - lol

Tim

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 68
  • 0
  • 27
NickyBB
Dialled in
545 Views
Message 38 of 74
Flag for a moderator

Re: Problems sending email using a mail client

Posting here as Rachel asked. I still can't access my email. I can't send or recieve. HELP!!! SOS.
0 Kudos
Reply
  • 10
  • 0
  • 8
mattyboy22
Tuning in
543 Views
Message 39 of 74
Flag for a moderator

Re: Problems sending email using a mail client

I'm with you. VM call centre has said they have reset my password. But now IMAP on iphone says wrong username and/or password and still cant log in via a web browser either. HELLLLPPP!

 

  • 9.56K
  • 1.06K
  • 4.5K
Superuser
Superuser
513 Views
Message 40 of 74
Flag for a moderator

Re: Problems sending email using a mail client

@mattyboy22

It would help if you kept your information to your own thread (posted at the weekend) that I have already answered with a request for more information. We might get somewhere then?

-----------------------

Superuser 18/19.
Use Kudos to say thanks
Tick an answer as "helpful" only when the problem is solved
Please don't send me private messages unless I ask you to.
I do not work for VM. The advice I give is based on my best understanding of VM policy and practice. You rely on it at your own risk.
0 Kudos
Reply