CDO SDNI connection not authorized

[rdemyan via AccessMonster.com]

I have implemented typical CDO code found here. It works at home, but not in
my client's highly secure network. Here's the error message:

"The message could not be sent to the SMTP server.
The transport error code was 0x800ccc6f. The server response was 554 5.7.1
GATE8-SDNI Connection not authorized.

Any ideas, suggestions, help is appreciated.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[David W. Fenton]

"rdemyan via AccessMonster.com" <u6836@uwewrote in
news:67a124d0a5af2@uwe:

I have implemented typical CDO code found here. It works at home,
but not in my client's highly secure network. Here's the error
message:

"The message could not be sent to the SMTP server.
The transport error code was 0x800ccc6f. The server response was
554 5.7.1 GATE8-SDNI Connection not authorized.

Any ideas, suggestions, help is appreciated.

The firewall is not allowing traffic on the port you're using.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[rdemyan via AccessMonster.com]

Thanks, for the response David.

How can I figure out which port I can use?

David W. Fenton wrote:

>I have implemented typical CDO code found here. It works at home,
but not in my client's highly secure network. Here's the error

[quoted text clipped - 5 lines]

>>
Any ideas, suggestions, help is appreciated.

The firewall is not allowing traffic on the port you're using.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Lyle Fairfield]

rdemyan via AccessMonster.com wrote:

I have implemented typical CDO code found here. It works at home, but not in
my client's highly secure network. Here's the error message:

"The message could not be sent to the SMTP server.
The transport error code was 0x800ccc6f. The server response was 554 5.7.1
GATE8-SDNI Connection not authorized.

Any ideas, suggestions, help is appreciated.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

If your machine has Outlook Express and an account in OE that works for
sending e-mail then (again) if you don't specify a sender or password
or smtp server CDO should/may/does for me default to that account and
has the same permissions.
Otherwise I suppose one has to open one's firewall and tell it to allow
CDO to go. The log should show when and how and what specifically was
blocked.

[rdemyan via AccessMonster.com]

I don't know anything about ports, so here's probably a stupid question.

Why can't I just use the same port that users use to send e-mail from Outlook?
Lyle Fairfield wrote:

>I have implemented typical CDO code found here. It works at home, but not in
my client's highly secure network. Here's the error message:

[quoted text clipped - 8 lines]

>Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

If your machine has Outlook Express and an account in OE that works for
sending e-mail then (again) if you don't specify a sender or password
or smtp server CDO should/may/does for me default to that account and
has the same permissions.
Otherwise I suppose one has to open one's firewall and tell it to allow
CDO to go. The log should show when and how and what specifically was
blocked.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Lyle Fairfield]

"rdemyan via AccessMonster.com" <u6836@uwewrote in
news:67a3473481e21@uwe:

I don't know anything about ports, so here's probably a stupid
question.

Why can't I just use the same port that users use to send e-mail from
Outlook?

It's likely 25 ? that is used to send mail. Your security/firewall may
allow Outlook to pass through but not other apps. My !!!!!guess!!!!! is
that you have to tell it (the firewall) to let CDO pass. Firewalls etc are
definitely not an area of expertise for me so I hope someone else can jummp
in here.

--
Lyle Fairfield

[rdemyan via AccessMonster.com]

IT will never allow it and I don't want to bring it up.

The reason I'm using CDO is to get around the Outlook security issue that
brings up a message every time an e-mail is generated. I'm doing a "mass" e-
mail to to individuals in the company (up to 100) and providing them with
customized reports (to be clear this is not spam).

I saw a post where someone created the e-mails and stored them in the
'Drafts' folder of Outlook. Never thought about doing this. But if I could
do that and if the sender could then send all of the emails contained in the
Drafts folder with one click that would work (I've never tried that so I
don't even know if it is possible).

Lyle Fairfield wrote:

>I don't know anything about ports, so here's probably a stupid
question.

Why can't I just use the same port that users use to send e-mail from
Outlook?

It's likely 25 ? that is used to send mail. Your security/firewall may
allow Outlook to pass through but not other apps. My !!!!!guess!!!!! is
that you have to tell it (the firewall) to let CDO pass. Firewalls etc are
definitely not an area of expertise for me so I hope someone else can jummp
in here.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[Lyle Fairfield]

rdemyan via AccessMonster.com wrote:

IT will never allow it and I don't want to bring it up.

The reason I'm using CDO is to get around the Outlook security issue that
brings up a message every time an e-mail is generated. I'm doing a "mass" e-
mail to to individuals in the company (up to 100) and providing them with
customized reports (to be clear this is not spam).

I saw a post where someone created the e-mails and stored them in the
'Drafts' folder of Outlook. Never thought about doing this. But if I could
do that and if the sender could then send all of the emails contained in the
Drafts folder with one click that would work (I've never tried that so I
don't even know if it is possible).

Well, automating Outlook may be a solution. I find that Outlook
frequently invents new barriers to be hurdled when it is used in that
way.

If I were doing this I would read up on Telnet
eg
http://weblogs.asp.net/owscott/archi...15/394681.aspx
http://www.activexperts.com/activemail/telnet/

and test the values I am using in my CDO code in a Command Prompt (DOS)
window using those examples first.

[rdemyan via AccessMonster.com]

I took your advice and learned that I need to use port 587. Now I can send e-
mails without authentication. However, I've also discovered that the server
is rejecting any e-mail addresses outside the company.

I'm still planning to include an option to use Outlook, because who knows
what IT might do in the future.

Thanks.

Lyle Fairfield wrote:

>IT will never allow it and I don't want to bring it up.

[quoted text clipped - 8 lines]

>Drafts folder with one click that would work (I've never tried that so I
don't even know if it is possible).

Well, automating Outlook may be a solution. I find that Outlook
frequently invents new barriers to be hurdled when it is used in that
way.

If I were doing this I would read up on Telnet
eg
http://weblogs.asp.net/owscott/archi...15/394681.aspx
http://www.activexperts.com/activemail/telnet/

and test the values I am using in my CDO code in a Command Prompt (DOS)
window using those examples first.

--
Message posted via http://www.accessmonster.com

[Lyle Fairfield]

"rdemyan via AccessMonster.com" <u6836@uwewrote in
news:67a8d825cb299@uwe:

I'm still planning to include an option to use Outlook, because who
knows what IT might do in the future.

Years ago I had an app that sent e-mails (in-house) via Outlook. Before it
did so it verfied addresses in the big system address or contact list. Then
came the Melissa virus. To baffle Melissa, IT entered twenty totally blank
addresses into the list. Pow! The e-mailing part of my application blew up!
And it was MY fault! Just ask IT and they'll confirm that.

So I fixed that. Later they did something (not sure what) to insert
"mail." after "@" in all in-house addresses. They didn't tell anybody, of
course. Again my application failed and again, it was MY fault.

After that I started to use CDO and I searched around and found some SMTP
servers that were totally open. I don't think such things exist any more.

--
Lyle Fairfield

[rdemyan via AccessMonster.com]

As I mentioned in my previous post, authentication is not required. Is there
a way that I can get the SMTP Server by using code. The actual string is
fairly long and no one will ever remember it. Also, it can change depending
upon location of the user trying to send the email. Right now, I've been
going into Outlook and finding it there and then essentially copying and
pasting the string into a pop up form that I display for the user to enter
the SMTP Server address. It's a hassle and if there is a relatively
straightforward way to get the SMTP server in code and not bother the user
with entering it, that would be nice.

Thanks for any help, suggestions, etc.

Lyle Fairfield wrote:

>I'm still planning to include an option to use Outlook, because who
knows what IT might do in the future.

Years ago I had an app that sent e-mails (in-house) via Outlook. Before it
did so it verfied addresses in the big system address or contact list. Then
came the Melissa virus. To baffle Melissa, IT entered twenty totally blank
addresses into the list. Pow! The e-mailing part of my application blew up!
And it was MY fault! Just ask IT and they'll confirm that.

So I fixed that. Later they did something (not sure what) to insert
"mail." after "@" in all in-house addresses. They didn't tell anybody, of
course. Again my application failed and again, it was MY fault.

After that I started to use CDO and I searched around and found some SMTP
servers that were totally open. I don't think such things exist any more.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200610/1

[David W. Fenton]

"rdemyan via AccessMonster.com" <u6836@uwewrote in
news:67a2c78a0743c@uwe:

David W. Fenton wrote:

>>I have implemented typical CDO code found here. It works at
home, but not in my client's highly secure network. Here's the
error

[quoted text clipped - 5 lines]

>>>
Any ideas, suggestions, help is appreciated.

The firewall is not allowing traffic on the port you're using.

How can I figure out which port I can use?

You'll have to ask the sysadmin in charge of the firewall.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"rdemyan via AccessMonster.com" <u6836@uwewrote in
news:67a2c78a0743c@uwe:

How can I figure out which port I can use?

Having read through your replies to Lyle, I wonder what SMTP server
you are connecting to? Perhaps your firewall is blocking access to
that particular SMTP server on Port 25.

I wonder why you're attempting what you're doing. Why can't you use
your company's SMTP server? If you don't do that, then your messages
are likely going to be treated as spam, which could cause major
problems for your company, since they will look like they are coming
from the same IP address as the whole of your company network.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Lyle Fairfield]

rdemyan via AccessMonster.com wrote:

As I mentioned in my previous post, authentication is not required. Is there
a way that I can get the SMTP Server by using code. The actual string is
fairly long and no one will ever remember it. Also, it can change depending
upon location of the user trying to send the email. Right now, I've been
going into Outlook and finding it there and then essentially copying and
pasting the string into a pop up form that I display for the user to enter
the SMTP Server address. It's a hassle and if there is a relatively
straightforward way to get the SMTP server in code and not bother the user
with entering it, that would be nice.

Thanks for any help, suggestions, etc.

Lyle Fairfield wrote:

I'm still planning to include an option to use Outlook, because who
knows what IT might do in the future.

Years ago I had an app that sent e-mails (in-house) via Outlook. Before it
did so it verfied addresses in the big system address or contact list. Then
came the Melissa virus. To baffle Melissa, IT entered twenty totally blank
addresses into the list. Pow! The e-mailing part of my application blew up!
And it was MY fault! Just ask IT and they'll confirm that.

So I fixed that. Later they did something (not sure what) to insert
"mail." after "@" in all in-house addresses. They didn't tell anybody, of
course. Again my application failed and again, it was MY fault.

After that I started to use CDO and I searched around and found some SMTP
servers that were totally open. I don't think such things exist any more.

I'm running out of ideas but here's my take on SMTP servers.

1. My website FFDBA.com has an SMTP server assoicated with it. I can
send e-mail from my local machine with CDO specifying it, the port(25)
and my username and password.
2. I use Cogeco.Ca as my ISP. As long as I am hooked up through them I
don't have to specify any of the things I mentioned in #1. My machine
is recognized as a valid connection and CDO sends e-mails directly
through smtp.cogeco.ca; but when I'm in Vancouver I can't connect
through Cogeco and then I must provide all that information.
3. I have a paid Yahoo e-mail account. I can send e-mail through it
using the logon Password etc, and Port 587 which is not the default,
25.
4. I have a free Aim/AOL account. I can use its smtp server from
anywhere to send e-mail with CDO if I have the requisite logons.
5. When I was running IIS servvices on my work station I could send
using its SMTP, that is my machine was its own server, but I don't run
IIS any more.

Those examples pretty much show what I know ....