Ravenstar's Email FAQ's

SMTP ERROR 530 What it means

SMTP error 530 is defined as meaning Access Denied.  When this is sent by a server the server sends additional information as to why it's been denied.  Two common reasons are blacklisting and authentication issues.

Blacklisting should not be a problem for home users, I've only included that here for completeness.

The message itself explains the reason  in this case.

Authentication Denied (VM401)

Unfortunately mail client error messages can somtimes confuse the issue,  Take a look at this one from Outlook

The message could not be sent because the server rejected the sender's e-mail address. The sender's e-mail address was someaddress@ntlworld.com'.

Subject 'hhh'
Server Error: 530
Server Response: 530 Authentication Required (VM401)
Server: 'smtp.ntlworld.com'
Windows Live Mail Error ID: 0x800CCC78
Protocol: SMTP
Port: 25
Secure(SSL): No

At first glance it looks as if the problem was with the senders email address.  However looking further down we see Authentication Required.  In other words - it's not the email address that's causing the issue.  It's the fact that the mail client has not authenticated beforehand.

What do I mean?  Lets talk to an email server in this case smtp.virginmedia.com

220 know-smtprelay-10-imp bizsmtp ESMTP server ready
ehlo desktop
250-know-smtprelay-10-imp hello [77.100.xxx.xxx], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 52000000
250-8BITMIME
250-STARTTLS
250 OK
mail from: <myaddress@blueyonder.co.uk>
530 Authentication Required (VM401)

 Lines in blue are messages from the server back to me.  The mail from: line is me sending out the address that the mail is coming from.  The server refuses it because I failed to authenticate first.  So lets try again.

220 know-smtprelay-10-imp bizsmtp ESMTP server ready
ehlo desktop
250-know-smtprelay-10-imp hello [77.100.xxx.xxx], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 52000000
250-8BITMIME
250-STARTTLS
250 OK
auth login
334 VXNlcm5hbWU6
bXlhZGRyZXNzQGJsdWV5b25kZXIuY28udWs=
334 UGFzc3dvcmQ6
bXlwYXNzd29yZA==
235 ... authentication succeeded
mail from: myaddress@blueyonder.co.uk
250 <myaddress@blueyonder.co.uk> sender ok

 This time I send an auth login command and the server asks for my username and password the request and response are sent in base64 encoding - note that encoding is not the same as encryption, the text can be read by going to a base64 decoder.

Note to mods - My username and password have been removed.  The encoded text simply reads myaddress@blueyonder.co.uk and mypassword.

Now when I send the mail from: command the address is accepted and I can go on and complete the exchange and send my mail should I wish to.

I've included the above as a background.  The long and the short is that by turning on email authentication in your client you should be able to send your mails.

But I could send mails before - what's changed?

Technically nothings changed smtp.blueyonder.co.uk, smtp.ntlworld.co.uk and smtp.virgin.net have had authentication switched on since at least 2011.

However in the interests of making things easier for the customer the old settings were also left in place.  This means that if you connect from a Virgin address and you were using the above servers then authentication is not needed.

However if you try to send from outside the Virgin network you still need to authenticate.

Whit the changeover of ADSL users from Virgin to TalkTalk Virgin appear to have removed some IP blocks from the lists of addresses allowed to send without authenticating.  Unfortunately some of the IP ranges were in use by blueyonder and ntlworld customers as well.  I say some, because despite the threads complaining of this.  I was able to connect and send mail unauthenticated to smtp.blueyonder.co.uk - although I should add this was just for testing.  I normally use SMTP authentication in ALL my clients.

Virgin have since restored the functionality so ntlworld and blueyonder users should now be able to connect.

So I can leave my settings as they are?

If you are using outdated settings it's really advisable to update them to the recommended settings for two reasons:

1. Should the problem that's caused this issue recur, then you shouldn't be affected as you are already authenticating (the smtp server won't complain if you authenticate when you don't need to).
2. Outdated settings pose a security risk.

As already stated the settings have been on Virgin's website since at least 2011 so a quick Google search will bring them up.  However here the recommended outgoing settings:

Server

• smtp.blueyonder.co.uk, smtp.ntlworld.com, smtp.virgin.net - to match the end of your email address - OR
• smtp.virginmedia.com - can currently be used for all four VM domains.

Port: 465

Security: SSL (Outlook) or SSL/TLS (Thunderbird) Other clients should show one format or another.

Authentication: Enabled This is found in more settings in Outlook.  On Macs and Ipads/Iphones this should be set to password.

Username and Password: same as incoming

Note that if you use POP3 with recent: before you username to collect mail, then you need to configure the smtp settings to login using your email without the recent: as the username.

Ravenstar68