|
Home > Archive > IIS and SMTP > April 2004 > SMTP strange behavior
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SMTP strange behavior
|
|
|
| I have a W2K box that sits on my DMZ and acts as a web
server and SMTP gateway to my internal network. This
morning I added a new domain to my list for inbound
routing and followed the same procedure for doing so that
I have followed numerous times before. While all of the
settings go in place fine, it never started working and
relaying is still being prohibited to this domain. In my
troubleshooting for this... I wrote a small SMTP script,
telneted into the SMTP port and ran it. The interesting
thing is that the SMTP server does not respond with 250 OK
for the RCPT entry and only repeats the address. That is
not what all of the articles I have found indicate should
happen. I should get the 250 OK response and don't. This
box already relays inbound for about 18 domains and the
configuration for it is two 2 checkboxes and one IP
address. Not too difficult, but it is not working. Could
the box have been hacked? I looked for signs (tools, user
accounts, group accounts etc.) and found nothing. Any
ideas anyone?
| |
| Darin Roulston [MSFT] 2004-04-11, 3:37 pm |
| In your post you say that relaying is prohibited to this internal domain.
Are you getting back a "Relaying Prohibited" non-delivery report when you
try to send to this domain or is it just not making it? You're right the
configuration should be straightforward, some other things to confirm:
1.) For Outbound security ensure that it is using anonymous if that's what
the internal server allows (compare to other domains).
2.) Ensure that the domain is set for remote and not local.
3.) Ensure that you are forwarding all mail to smarthost and that the
smarthost can be resolved (if it is FQDN). Might want to try IP in
square-brackets if you're not sure.
If this all looks correct then you may want to have a look into your
metabase using metaedit utility. I won't go into detail but if you drill
down under the smtp node you can see the domains you've defined and what
there route action is. If this one is different you'll want to find out why
in the configuration, or why the setting is not making it down to the
metabase. You can get the metaedit utility from
http://support.microsoft.com/defaul...&NoWebContent=1
--
Darin Roulston
Microsoft PSS
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights
"Rob H" <anonymous@discussions.microsoft.com> wrote in message
news:191b401c41c04$a0fabb90$a401280a@phx
.gbl...
> I have a W2K box that sits on my DMZ and acts as a web
> server and SMTP gateway to my internal network. This
> morning I added a new domain to my list for inbound
> routing and followed the same procedure for doing so that
> I have followed numerous times before. While all of the
> settings go in place fine, it never started working and
> relaying is still being prohibited to this domain. In my
> troubleshooting for this... I wrote a small SMTP script,
> telneted into the SMTP port and ran it. The interesting
> thing is that the SMTP server does not respond with 250 OK
> for the RCPT entry and only repeats the address. That is
> not what all of the articles I have found indicate should
> happen. I should get the 250 OK response and don't. This
> box already relays inbound for about 18 domains and the
> configuration for it is two 2 checkboxes and one IP
> address. Not too difficult, but it is not working. Could
> the box have been hacked? I looked for signs (tools, user
> accounts, group accounts etc.) and found nothing. Any
> ideas anyone?
|
|
|
|
|