I have found a way round the problem now by forcing a new smtp send using the SendingMail event of the PasswordRecovery control.
Clearly the Webhosting UK Mail server was relaying the email correctly, provided it was instructed correctly, which I guess the PasswordRecovery control in ASP.NET wasn't doing.
Here is my v.simple code which has got round the problem.
Quote:
Protected Sub PasswordRecovery1_SendingMail(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.MailMessageEventArgs) Handles PasswordRecovery1.SendingMail
Dim thisSMTP As New SmtpClient
thisSMTP.Send(e.Message)
e.Cancel = True
End Sub
|
This seems to do what I assumed the control was doing anyway, so I'm not exactly sure how this has fixed the problem, but i certainly dont get the error any longer and the email arrives at the destination, so I'm happy (apart from wasting so much time trying to find out what i was doing wrong)
Thanks to those who looked at my post and to Gerrard for trying to help me find a resolution.