CDOSYS problem

[Ranger]

A couple of weeks ago our confirmation emails have stopped working. When I check the event log on our server and for each mail that is meant to be sent I get the following warning event :-

Message delivery to the remote domain <'mydomain.com'> failed. The error message is 'An SMTP protocol error occurred.
'. The SMTP verb which caused the error is 'RCPT'. The response from the remote server is '550-EHLO/HEL0 argument <(name of the machine)> must be a syntactically-valid
550 fully-qualified domain nam'.

Nothing has changed around this area so i'm not really sure why this problem started.

Any help would be appreciated.

Thanks

[Rob]

I realise nothing has changed, but please post your code.

[Ranger]

Hi - sorry, when i said nothing has changed I meant there has been no code changes. And there has been no code changes since i started working on this project.

Thanks

Here is the code :-

Code: Select all

Function MSCSExecute(config, orderform, context, flags)
 Dim iMsg, iConf, iFlds
 Dim item, bIsBookOrder
 
 Set iMsg = CreateObject("CDO.Message")
 Set iConf = CreateObject("CDO.Configuration")
 Set iFlds = iConf.Fields
 With iFlds
  .Item("http://schemas.microsoft.com/cdo/con...tion/sendusing") = 2 'cdoSendUsingPort
  .Item("http://schemas.microsoft.com/cdo/con...ion/smtpserver") = config.smtpserver
  .Item("http://schemas.microsoft.com/cdo/con...nectiontimeout") = 10
  .Item("http://schemas.microsoft.com/cdo/con...tpauthenticate") = 0 'cdoAnonymous
  .Item("http://schemas.microsoft.com/cdo/con...tlatestversion")   = True
  .Update
 End With
 
 With iMsg
  Set .Configuration = iConf
  .To = orderform.Value("user_email_address")
  .Cc = <***our email***>
  .From = <***our email***>
  .Subject = "New Order Confirmation"
  .TextBody = orderform.Value("_po_text")
  .Send
 End With
 Set iMsg = Nothing
 Set iConf = Nothing
 Set iFlds = Nothing
 
 MSCSExecute = 1
End Function

[Rob]

Hmmm.... maybe the machine has been patched recently and some settings have changed.....

Sometimes it is a requirement lately to make sure that the FROM address is an address on the websites domain AND actually exists..... maybe something you can look at.

[Ranger]

Thats a possibility. I will have a look and post back on how I get on.

MMMMmm in fact not really sure how to do that as our web server is co-located and just on a workgoup and with a couple of users added to allow remote desktop in.

Funnily enough the current mail from address is from a user/domain on our network.

Thanks

[Ranger]

Hi

Still having no luck finding any information on this subject. Does anybody have any suggestions to help.

Thanks.

FAO Rob - When you said the FROM address may have to be an address on the websites domain. No users have email addresses set up so i'm not really sure how to do that.

Cheers

Nickie

[Ranger]

Hi

I have found the 'Bad Mail' item in 'C:\Inetpub\mailroot\Badmail' and there is a tad more information in it.

Final-Recipient: rfc822;me@mydomain.com
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;550-EHLO/HEL0 argument (<mywebserverdomain>) must be a syntactically-valid
550 fully-qualified domain name or address literal

Not actually sure what 'rfc822' is in the line 'Final-Recipient:'

Cheers

[Rob]

Originally Posted by Ranger

Hi

I have found the 'Bad Mail' item in 'C:\Inetpub\mailroot\Badmail' and there is a tad more information in it.

Final-Recipient: rfc822;me@mydomain.com
Action: failed
Status: 5.0.0
Diagnostic-Code: smtp;550-EHLO/HEL0 argument (<mywebserverdomain>) must be a syntactically-valid
550 fully-qualified domain name or address literal

Not actually sure what 'rfc822' is in the line 'Final-Recipient:'

Cheers

So... I was right then

[Ranger]

OK - fixed it last night.

The problem was that when sending a text e-mail using a 'remote server' the
smtpserver field in the configuration object needs to point to a domain which is the same as whats in the FROM address. The only thing i cant work out is why it stopped working on our web server as no settings or code was changed but the IP address being used was that of our web server. So i changed this to point to our exchange server (on a different location/network) and it worked.

Thank god for that as I didn't want to worry about that over the festivities.

Cheers