DotNetNuke

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

smcmiata — Fri, 19 May 2006 17:37:14 GMT

Oops, my above reply should have included this quote:
SMc

ErikVB:

Ahh, the virus scanner makes sense. I heard of someone that had the same problem (with macafee enterprise 8) ... Why in earth would a virusscanner block ports actively? That means if the can't kill the worm, they just kill everything ....

[B]cheers,

erik

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

smcmiata — Fri, 19 May 2006 17:11:19 GMT

I have the same issue on my development server. I added "w3wp.exe" to the list of Excluded Processes and that works as well.

Now, my problem is when I add that file to the excluded list (or uncheck the rule: "Prevent mass mailing worms from sending mail" check box in the port blocking dialog box) Macafee reverts back to the orginal settings within about an hour +/-.

So, I make a change, click Apply, OK in the dialog windows, but after a little while when I go back to the settings, they have changed back.

Is there a way to make changes in Macafee, and get them to stick?

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

djbaldwin — Wed, 30 Nov 2005 12:27:21 GMT

Check your Log Viewer for the portal and you can see why CDO puked.

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

mikeh36 — Thu, 03 Nov 2005 16:33:02 GMT

I'm assuming you're getting the CDO.Message error when you're testing your SMTP settings. Do you have a valid email for your host account? By valid I mean that it isn't something like host@localhost/dotnetnuke or something similar. If the host email isn't valid you'll get that error.

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

smobley — Thu, 03 Nov 2005 14:33:58 GMT

Hi folks,

Here is a new one for you. I have installed a fresh copy of windows 2003 standard edition, and then the appropriate services along with DNN 3.1.X. Now, when I installed the OS, I setup the Win2003 SMTP and POP services, and they are all at the defaults.

Now everything works fine it appears, however jus to note that I didn't setup the SMTP information under the host setting.

Here is what is odd. When I change someones role, they get get a notification email (so long as that is checked.) Thats not a bad thing per se, but what is strange is when I actually go ahead and enter in localhost in the SMTP server parameter, I get the Cannot access the CDO.MESSAGE error...

How can that be? As obviously its finding it to send the notifications on role changes, or is that using a difference component?

Thanks

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

coloradowebdev — Thu, 14 Apr 2005 14:11:02 GMT

the weirdest thing...

i went through a process of modifying the Globals.SendMail function. Basically, I hard coded the server, username, password, etc, and i received the test e-mail.

i then began to back my way out, replacing the body, subject, etc, with the variables again. i kept receiving the test e-mails.

it wasn't until i put back the variables for the to/from that i stopped receiving the emails again. (i forget offhand, but i think i didn't get the e-mail unless both the to and from were hard coded).

so i went back to the hostsetting.aspx page and made a few changes to have it display what it was passing as the to and from. interestingly, it was the exact same e-mail address as i thought; the host email. and it looked just fine. no extra spaces. no weird formatting. nothing out of the ordinary.

just in case, i replaced the sendmail line with:

Dim strMessage As String = SendNotification(txtHostEmail.Text.Trim, txtHostEmail.Text.Trim, "", Services.Localization.Localization.GetSystemMessage(PortalSettings, "EMAIL_SMTP_TEST_SUBJECT"), "", "", "", txtSMTPServer.Text, optSMTPAuthentication.SelectedItem.Value, txtSMTPUsername.Text, txtSMTPPassword.Text)

For some reason, that seemed to work. Now all my messages are going through.

No clue. But its working. Maybe it will help someone else.

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

coloradowebdev — Wed, 13 Apr 2005 17:48:46 GMT

I've tried a number of different servers, authentication types, etc etc. The weird thing about all of this is that while DNN (3.0.12, btw) either throws me a CDO.Message error or says ''Email sent successfully'' from the Test option and I don't actually receive the message, a simple .aspx page on the same domain with the same settings works just fine. Further, it works fine with a number of different combinations of authentication/servers/username, etc.

is there some different mechanism or permission or something that DNN would use versus a regular old .aspx page?

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

wvaneck — Wed, 13 Apr 2005 15:39:32 GMT

Hi,

DNN uses the webmail component from the .Net framework. The webmail component is dependent on the cdosys.dll. This is dll gets installed in your windows\system32 directory when you install the SMTP service.

No SMTP service no cdosys.dll, means no web mail. It just doesn't matter if you connect to a remote server or not.

Try to place a copy from your web server on your stand-alone machine and register the dll.

Wouter

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

ErikVB — Tue, 12 Apr 2005 17:23:57 GMT

Ahh, the virus scanner makes sense. I heard of someone that had the same problem (with macafee enterprise 8) ... Why in earth would a virusscanner block ports actively? That means if the can't kill the worm, they just kill everything ....

cheers,

erik

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

liffey — Tue, 12 Apr 2005 16:52:09 GMT

FYI

I was having the same problem on a WinXP box trying to send email through to a Win2003 Server box. Having read all threads referencing CDO I eventually tracked down the problem. It had worked before but "suddenly" stopped.

My problem had been caused by an upgrade to McAfee Virusscan 8. In this there is a setting which blocks port 25 to protect against mass mailing worms. Turning this off solved my problem.

Declan

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

meistvan — Mon, 03 Jan 2005 00:07:49 GMT

I'm testing smtp service using mailenable on a WinXP Pro box.

right after the installation, without changes I was able to get the test to work, but only once.

after that, I get the same CDO error that is mention in this thread.

My eventual target is Win 2003 server, but want to test out everything prior to moving to my production platform.

Thoughts?

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

J7Mitch — Mon, 04 Oct 2004 15:59:41 GMT

Glad it's working Rad. I should have had you check the administrators address sooner I guess.

Your SMTP snap-in should be under Internet Information Services (that's the snap-in you add to see the SMTP virtual server anyway)

If your MailEnable machine is the same as the webserver then you can Relay from 127.0.0.1, but if it is not then you better look into why it's allowing the relay without authentication real quick (open relay blacklisting can happen within hours).

You should not allow relay without authentication, and maybe from trusted IP address (if you trust everyone using that IP).

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

raca — Mon, 04 Oct 2004 03:31:55 GMT

I finally have success.

(Not to forget to ask you BTW, I lost snap-in for my SMTP in IIS6. I am sure I didn't uninstall it. How to find it?)

These are my current DNS settings.
Host Name Record Type Address
@ (none) A 207.164.21.230
mail A 207.164.21.229
www A 207.164.21.230
* MX (MX Pref 10) mail.rentalvista.com.
@ MX (MX Pref 10) mail.rentalvista.com.

As John suggested (thank you John) I typed in webmaster@rentalvista.com for Host email and only set SMTP server settings this time to mail.rentalvista.com and it worked even without user or user/password combination. I do have SMTP setup and added 127.0.0.1 in Relay dialog and I am not sure if SMTP is used at all. I think yes based on the interpretation bellow.

Bellow is header of email message that was successfully sent via Test button from Host Settings module.



Received: from wizard ([207.164.21.230]) by QS-QUOTE.NET with MailEnable ESMTP; Sun, 03 Oct 2004 22:37:17 -0400


thread-index: AcSpuxOaip1I8NpLQZyoonSwElcH4g==


Thread-Topic:   IWEG12345 SMTP Configuration Test  


From: <webmaster@rentalvista.com>


To: <webmaster@rentalvista.com>


Subject:   IWEG12345 SMTP Configuration Test  


Date: Sun, 3 Oct 2004 22:37:22 -0400


Message-ID: <001801c4a9bb$139a8a10$1ea8a8c0@wizard>


MIME-Version: 1.0


Content-Type: text/plain;


	charset="iso-8859-1"


Content-Transfer-Encoding: 7bit


X-Mailer: Microsoft CDO for Windows 2000


Content-Class: urn:content-classes:message


Importance: normal


Priority: normal


X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181

I interpret line:
Received: from wizard ([207.164.21.230]) by QS-QUOTE.NET with MailEnable ESMTP
like this: The message was received from 207.164.21.230 machine (my web machine) with what?? SMTP service (what else would sent it from that address)

Line:
X-Mailer: Microsoft CDO for Windows 2000
should confirm what I said above.

To conclude. I believe that if I disable (or uninstall or remove 127.0.0.1 from relay) SMTP
service in IIS then I would need SMTP extra user/password combination to directly send email via MailEnable machine.
Can you guys confirm this. I am just tired from the whole experiment and I would like if I finally understand this issue.

I will probably do a final experiment. If you suggest how to recover SMTP snap-in I will try to stop the services (I know I can do it from Services panel) and try sending a Test email with
SMTP and User/Password combination directly via MailEnable server.

Thank you John and Scott for being with me. I hope others might benefit from this thread.

Rad

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

mrswoop — Sun, 03 Oct 2004 16:00:29 GMT

Agreed. Thanks John... I'm pretty interested in the results of this thread myself.

Cheers,
Scott

Re: Could not access 'CDO.Message' object. (Proper SMTP settings!!!)

J7Mitch — Sun, 03 Oct 2004 12:17:56 GMT

Scott may be right, it could be the CDO setup on the server, but I assumed that was correct since the original questions were about DNS. Not good to assume, but the other checks were good to narrow down the possibilities. With this last test, I agree with Rad that CDO is probably configured on the server OK, since most servers have CDO on them by default and this is hardly ever the problem. The DNN code only trys to send and if anything fails at all it says Could not access 'CDO.Message' object, but the original stack trace and the test indicate that the remote SMTP did not respond correctly.

Two more things to try:

1. You can put your webserver's IP or domain name into the SMTP server field and see if the SMTP service is running on it.

2. Since you are trying to relay through a remote server it probably requires that the FROM address in your sent e-mails are valid in the domain that you are authenticating and sending with. Try making your FROM property webmaster@rentalvista.com
You do this in DotNetNuke by setting the Administrator's e-mail address. When logged in as admin, click on the administrator link for the user profile and change the e-mail address there.