Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

Thanks for this hint.

 

I had basically "opened up the whole world" to allow people to email from my computer.

And it didn't work.

 

The ".Insert" method fixed it.

 

 

SmtpMail.SmtpServer.Insert (0,smtpServer);

//SmtpMail.SmtpServer = smtpServer; // There is an issue with setting the smtpserver directly

//the .Insert method was a fix described at: http://www.xtremedotnettalk.com/t69426.html

 

 

 

 

 

 

I was able to fix this problem by using the following code

 

<smtpMailObject>.smtpserver.insert(0,"server name")

 

insted of

 

<smtpMailObject>.smtpserver = "server name"

  • 2 weeks later...
  • 9 months later...
Posted

Quick Fix

 

I resolved this problem by going into the smtp server in exchange, in authentication, and enabled "resolve anonymous e-mail". That allowed be to send! Hope this helps!

  • 3 months later...
Posted

Could not access 'CDO.Message' object

 

Ensure that you have correctly formed email addresses. For example:

 

Dim mMessage As New MailMessage

With mMessage

.From = "Automated Mail"

.To = "you@yourhouse.com"

End With

 

will result in >> Could not access 'CDO.Message' object.

 

(InnerException.Message)

The server rejected the sender address. The server response was: 553 malformed address: <Automated Mail>

 

removing the space, in this instance, from the .From property will resolve the error.

 

Imports System.Web.mail

 

Sub sendmail()

 

Dim mMessage As New MailMessage

With mMessage

.From = "AutomatedMail"

.To = "you@yourhouse.com"

End With

 

SmtpMail.SmtpServer = "[servername]"

SmtpMail.Send(mailMsg)

 

End Sub

 

 

Note: some email servers will have policy restrictions applied to them to prevent spam, e.g. mail may only be allowed to go external if its origin is safe.

 

Check your antivirus from block port 25

and allow your ip address to relay on your SMTP server

  • 16 years later...
Posted
My second experience with "Could not access 'CDO.Message' object." My second experience with "Could not access 'CDO.Message' object." The first time I had it problem it was due to the cdo DLLs not on the server. That was serveral months ago. I setup outlook on the server and that fixed that was fixed. On a different server I setup IPsec packet filtering and it caused the the same "Could not access 'CDO.Message' object." error. Catch the comexception error and it will give you a more descriptive error message than the general httpexception would. To fix this problem the second time all I had to do was unfilter port 25 for SMTP. IT just sucks that the http exception delivers the same "Could not access 'CDO.Message' error message. I think MS just likes to play with us. I know I would. Hope that helps someone  

You it is serious?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...