I posted this to an Exchange newsgroup but they seem to think this is a
"Developer Issue", so here it is again.
Kal
*********************************
I have access to two LANs each with an Exchange Server and a webserver.

There is an MSDN article "Sending SMTP Mail by Port 25 Using CDOSYS". I
copied this code and on the first network it worked perfectly. This one uses
Exchange 2000 on SBS 2000.

The server that worked has an address of 10.0.0.x and the exchange server
has an address of 10.0.0.y and relay explicitly allowed for 10.0.0.x. This
webserver is used for test and has no external ip address.

The webserver that does not work has two addresses 10.1.1.x and
209.111.251.y (assigned to the website). The exchange server has an address
of 10.1.1.z and relay explicitly allowed for 10.1.1.x. This one is Exchange
2003 on Windows 2003 with Intelligent Message Filter and recipient
filtering. I have tried it with both from and to addresses resident on the
Exchange Server and with other combinations of addresses.

The page fails with the not very informative error in the subject. I added
an explicit route for 10.1.1.0 but it made no difference. Does the webserver
try to send the message via the external address? If so, I suppose this is
seen as a forbidden relay.

Is there a solution?

The above is as posted to the public.inetserver.iis.smtp_nntp group a few
days ago, but have not received useful feedback.

Since then I have repeated the experiment from two other computers with only
one NIC, the address of which is explicitly allowed to relay. The error
message here is:
a.. Error Type:
(0x80040211)
/email/msdnEmail.asp, line 55

(This is the '.Send' line)

************

Or we can simplify the question: How do you "Sending SMTP Mail by Port 25
Using CDOSYS" when the SMTP server is Exchange Server 2003 with Intelligent
Message Filter and Recipient Filter?

Kal

Hi Kal,

Yes, both SMTP/CDO and Exchange are not in MSDN managed newsgroup
support boundary. Since the code can work fine with Exchange 2000
SMTP but not work with Exchange 2003, I think you can try posting the
issue to Exchange newsgroup(also unmanaged) for some ideas.

Another way for you to get a solid and more effective support on this
issue is to create a support incident to Microsoft Customer Support
Service. Each MSDN subscriber should have 2 free incident accounts.
You can find your local support center's phone number from the link
below:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no
rights.

See the newsgroup microsoft.public.dotnet.framework for resolution of this
issue.

That newsgroup was dealing mostly with SmtpMail, which as I understand it,
uses CDOSYS. That immediate problem was that IMF was filtering attachments
named .log.

For some unknown reason ASP based CDO has also begun to work. I made a
couple of apparently trivial changes in exchange, neither of which should
make a difference, but here they are anyway.

In Exchange, we have both Recipient Filtering and Connection Filtering
enabled.

There might have been a case mismatch between exchange and CDO. I did make
sure that they were both lower case in the test that worked.

I added my internal network to the "Always accept list" in connection
filtering.
Kal
[quoted text, click to view]