CDOSYS Isue

[tddeffner]

I was hoping you guys can help me out. I am working on an email script using CDOSYS. Inside our network it works just fine. I can send emails. Now when we try on the client side on a different workstation it seems to have a fit, and brings up this strange message saying something needs to be changed on the client side browser setting. We do not want this, it will just confuse our clients.

Anyone know what I am talking about? Anyone know a way around it?

[DrBunchman]

Hi tddeffner,

What's the exact error message? And what code are you using to send the email?

Dr B

[tddeffner]

Not exactly sure what the error message was but it had a button that said add on it. I am just using basic asp mail code.

I am essentially using this code.

http://www.w3schools.com/asp/asp_send_email.asp

This is all server side though, why would the client get a message about it.

[DrBunchman]

I don't know - without seeing the error message it is very hard to say what the problem might be.

Is the script trying to do anything else apart from sending the email? It's not trying to use activex or perhaps javascript which might be switched off on the client machines browser?

Dr B

[tddeffner]

No nothing and it works for me, but I might have different browser settings. No javascript or vbscript is in that area of the script either.

[tddeffner]

Ok just found that its not an error its actually a warning asking if you want to change settings. My Question is though first how to not give that warning, and second why would it matter its all server side.

[tddeffner]

Ok the warning is asking to trust the site. Still this can be confusing we do not want this, anyway it can be avoided?

[tddeffner]

Ok the warning is asking to trust the site. Still this can be confusing we do not want this, anyway it can be avoided?

[jhardman]

Ok the warning is asking to trust the site. Still this can be confusing we do not want this, anyway it can be avoided?

Find out at what point the error comes up - right when the page loads? As you said, if it is all server-side, I don't see any reason it shoudl come up, unless all content from that site is blocked (worth looking into - IT people like to install IE with settings that block all content from untrusted sites forcing the user to accept trust for each new page you connect to, at least two of my clients have their browsers set up that way).

Try a plain old "hello world" HTML page, see if it pulls up the same warning. If that is the case than it is a browser/Network issue and your client's IT team that installed the browser caused the problem and there is no way around it without changing browser settings. Tell them they have to install Firefox.

Jared