Re: reject messages to a domain

On Mon, 18 Sep 2006 13:24:02 -0400, "Matt" <matt@xxxxxxxxxx> wrote:

When I sent a test message to a non existent domain by telneting to the
Exchange SMTP, it bounced immediately with the message:
hdh@xxxxxxxx on 9/18/2006 12:36 PM

The destination server for this recipient could not be found in Domain Name
Service (DNS). Please verify the email address and retry. If that fails,
contact your administrator.

<our.smtp.server.edu #5.4.0>

it would follow that the same thing should happen to our retired email
domain unless it's cached somewhere. The domain itself exists as bing owned
by someone, but there are no records associated. Maybe that's the
difference.


Yes, if the domain is not-existent, it should bounce back immediately.
Why the need to for this?

Matt


"Susan" <sconkey@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eSoJGM02GHA.2196@xxxxxxxxxxxxxxxxxxxxxxx
it wouldn't fail immediately...Exchange will keep looking for some kind of
way to deliver...usually, a "delay" notification will be generated in 3 -
4 hours...eventually it will time out...

--
Susan Conkey [MVP]



"Matt" <matt@xxxxxxxxxx> wrote in message
news:uj6biJ02GHA.4764@xxxxxxxxxxxxxxxxxxxxxxx

"Andy David - MVP" <adavid@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:rpftg2l2vg47p7pugf95q2igd2n78o7b1g@xxxxxxxxxx
On Mon, 18 Sep 2006 11:42:39 -0400, "Matt" <matt@xxxxxxxxxx> wrote:

Already have. I have many user that are still sending to the retired
domain. Is there something wrong with connector I configured?

Removing the MX wont do anything but force Exchange to check for a A
record it can send to, then timeout.

There's no MX or A record anymore. So, it should bounce immediately as
this one did:
hdh@xxxxxxxx on 9/18/2006 12:36 PM

The destination server for this recipient could not be found in Domain
Name Service (DNS). Please verify the email address and retry. If that
fails, contact your administrator.

<hermes70.engr.pitt.edu #5.4.0>

Maybe the record is cached somewhere. I've flushed the DNS and netbios
cache on the server. Used ipconfig /flushdns and nbtstat -R . Any other
places it may be holding onto an old record?


Maybe smarthost to a IIS box running SMTP on your domain?
If that IIS server doesnt accept for that domain, it should 550
immediately and the rejection info relayed back to the sender.

I guess another work-around is to add that domain to your recipient
policy. It should bounce since you are not really authoriative.




"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:ezg9$Uz2GHA.4636@xxxxxxxxxxxxxxxxxxxxxxx
Remove the MX record for the domain.

Nue
"Matt" <matt@xxxxxxxxxx> wrote in message
news:%23sEwJFz2GHA.4164@xxxxxxxxxxxxxxxxxxxxxxx



"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%2306Yqly2GHA.1548@xxxxxxxxxxxxxxxxxxxxxxx
In news:eCom$dy2GHA.4648@xxxxxxxxxxxxxxxxxxxx,
Matt <matt@xxxxxxxxxx> typed:
Hello,

Win2k3/Ex2k3 all up to date.

I would like to immmediately bounce all messages sent to a
particular
domain. I've made an SMTP connector with address space set to
domain2Reject.com and selected Reject on the Delivery Resctricions
tab. I adjusted the registry and restarted the services according
to
the KB article http://support.microsoft.com/kb/277872/EN-US/ , but
there seems to be no difference in what happens to these messages.
They
get queued and timeout according to the Internet connector that
is configured for the * address space. The 2 connectors have the
same
priority (1) .
Any clue what I'm doing wrong, or how else to do this? Maybe an
SMTP
sink?
This is likely a unique situation to our environment, but suffice
to
say that we're not able to stop these messages from coming to our
server yet, their is no where to deliver them and we want people to
get bounces quickly to resend their message appropriately. I also
cannot use the Global anti-spam features to deal with this becuase
of
our environment.
Thanks in advance,
Matt

The SMTP connector would act on mail sent *from* your server(s), not
to
it, so I'm a little confused as to why you mentioned "stop these
messages from coming to our server". Can you provide a little more
detail as to a) what you want to do/prevent and b) your existing
configuration ?


Yes, I'm talking about mail sent fom our server. Our mail server is
queueing mail bound for a domain that has no where to go anymore
because
we retired this email domain. We would like messages that are
accidently
sent to it by users using the server to send to bounce immmediatly.
I
complicated the question with unecessary details. Sorry, to confuse.

Matt











.

Relevant Pages

  • RE: SMTP Mail service not connectiong
    ... It looked like had a faulty SMTP connector and reset the Email ... > connector in the Exchange Server? ... > This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBCs SMTP server quit working with SMTP connector
    ... SMTP connector and default SMTP virtual server. ... > Thank you for posting in the SBS newsgroup. ...
    (microsoft.public.windows.server.sbs)
  • RE: Cant Send Mail - SMTP Issues
    ... Internet mail server does not have the correct DNS configuration required ... AOL.com also requires that for every inbound SMTP connection, ... SMTP connector in SBS 2k3 is automatically ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: SBCs SMTP server quit working with SMTP connector
    ... Thank you for posting in the SBS newsgroup. ... Connector and Default SMTP Virtual Server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Your message did not reach some or all of the intended recipie
    ... 'SmallBusiness SMTP connector' Properties? ... Please also make sure Default SMTP Virtual Server is listening 'All ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Loading