Hi Jim,
The telnet shows that the server can connect to the Exchange
Server, so that eliminates any connectivity issues.
Have a look at this, which gives a stepwise guide to testing
a mail server with telnet.
http://support.microsoft.com/?kbid=153119
As you say, it doesn't seem that the problem is at the
Exchange server end, but that wasn't what the test was
intended for. I asked you to do the test because if there
were connectivity problems, they would have shown up.
To completely eliminate the Exchange Server from the
equation I would still follow through the telnet steps to
see if the machine can actually send mail through the
Exchange Server - it may think that you are trying to relay
through it or something.
If you eliminate the Exchange Server, the problem has to be
the utl_smtp program, in which case you might have better
luck on an Oracle forum.
One gotcha with this type of SMTP program is that the
program send SMTP commands to the server, and if the server
is contactable the return code of each command is *always*
zero signifying a success. The SMTP server *then* sends
messages to the program, such as 220, 500, etc, which
indicate the result of the SMTP server executing the
command. I'd expect the Oracle program to do things
properly, but once the mail is completed (by a line with
only "." on it) then SMTP part of Exchange passes the
message to the rest of Exchange, which has its own rules and
may drop the email silently. That's why a complete telnet
test is so useful.
But as I said, you may have more luck on am Oracle forum. If
you do the SMTP test let us know what happens. Be aware that
communicating with an SMTP through telnet is unforgiving.
You can't correct a line of input easily. You may also not
see what you are typing. It can be frustrating, but is so
useful!
Cheers,
Cliff