Right,
I have part of this problem sussed. That Wormly test won't work on the mail servers precisely because they don't allow relaying.
Quote:
smtp.ntlworld.com:
Resolving hostname...
Connecting...
SMTP -> FROM SERVER:
421 aamtaout01-winn.ispmail.ntl.com connection refused from [66.228.123.50]
SMTP -> FROM SERVER:
SMTP -> ERROR: EHLO not accepted from server:
SMTP -> FROM SERVER:
SMTP -> ERROR: HELO not accepted from server:
Message sending failed.
The IP address resolves to:
$ host 66.228.123.50
50.123.228.66.in-addr.arpa domain name pointer clover.wormly.com.
smtp.blueyonder.co.uk:
Resolving hostname...
Connecting...
SMTP -> FROM SERVER:
220 asmtp-out3.blueyonder.co.uk ESMTP Sun, 26 Jul 2009 09:18:33 +0100
SMTP -> FROM SERVER:
250-asmtp-out3.blueyonder.co.uk Hello www.wormly.com [66.228.123.50]
250-SIZE 31457280
250-PIPELINING
250-AUTH LOGIN PLAIN
250 HELP
MAIL FROM: ******@ntlworld.com
SMTP -> FROM SERVER:
250 OK
RCPT TO: ******@ntlworld.com
SMTP -> FROM SERVER:
550 Administrative prohibition - relaying not allowed
SMTP -> ERROR: RCPT not accepted from server: 550 Administrative prohibition - relaying not allowed
Message sending failed
|
Those tests only go to prove the servers are up and running, it is down to the configuration of the mail server you have entered as to whether the test will work.
In both cases I have tried smtp.ntlworld.com & smtp.blueyonder.co.uk, and in both attempts it has said that relaying has failed which it is supposed to as a spam avoidance measure. You aren't able to specify that the server allows smtp authentication because that is not what the simple test does. SMTP Authentication only works on the blueyonder platform, as per this line:
So for the moment can you provide the actual error message you are getting from your email program, and not the above test, we may then be able to get to the bottom of things.
Oh and for the record, I am not suggesting for one minute there isn't a problem on VM's side, there could well be.