Re: How to remove a mail domain

Tech-Archive recommends: Fix windows errors by optimizing your registry

Niels Koldborg wrote:
I have now tryed to mail to a rapidis account that is new and another
old one.
I have to both accounts mailed from within thr informi.dk doman
I have to both accounts mailed using OWA.
I have to both accounts mailed from VPN connetion.

I get the same NDR every time.
I every time see the same in the Messaging Tracking Center.

Hope this info is helpfull.

/Niels


I know the suggestions seemed redundant, but from the results it seems like
Exchange still believes it is authoritative for the domain.

I have not been able to find the article on manually reconfiguring Exchanges
authoritative domains.

One question first. Is "rapids.com" exaclty the same as your active
directory domain name?

If not, then I would suggest readding your @rapids.com to the recepient
policy, then unchecking the Exchange responsible for delivery to this domain
box. Then removing it from the recepient policy comletly as you have. This
should ensure that Exchange doesn't try to delivery mail to this domain
locally.



"kj [SBS MVP]" <KevinJ.SBS@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23p6ttnv$HHA.4612@xxxxxxxxxxxxxxxxxxxxxxx

The reporting MTA is important for troubleshooting your NDR. If
it's not the originating Exchange Server (&SBS) then the removal
of the domain likely has occured.

Can you re-verify this and re-report the whole NDR message.



I think i misunderstod your question, so I vil clarify

My domain informi.dk is the SBS 2003 Premium, the Exchange on this
machin has been hosting
informi.dk and rapidis.com.
I have deleted the domain rapidis.com it is no longer hostet on
informi.dk.
I have set up a SBS 2003 R2 Premium the Exchange on this is hosting
rapidis.com
and is reciving mail from every one.
rapidis.com is a startup company, and is now ready to go it alone.

When any user from the domain informi.dk send a mail to rapidis.com
the user gets a NDR
With the following message:
This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

ti@xxxxxxxxxxx

And txt file with the folloving message is attatch:
Final-Recipient: rfc822;ti@xxxxxxxxxxx
Action: failed
Status: 5.1.1
X-Display-Name: 'ti@xxxxxxxxxxx'

I hope this clerar things

Niels.



Thanks for clarification / update. Please post the exact and
complete NDR. Also try sending from OWA to a brand new, never used
user/address in the rapidis domain.

--------

Numeric Code: 5.1.0

Possible Cause: This code indicates a general categorizer-based
failure (bad address failure). An e-mail address or other attribute
could not be found in the directory. This issue may occur if contact
entries do not have the targetAddress attribute set. This issue
occurs most frequently when MDAccess receives "object not found"
errors from DSAccess when the Categorizer is doing the homeMDB
lookup on a user. This issue also occurs if you used Microsoft Outlook to
save
your e-mail message as a file and someone opens and replies to this
message offline. The message property only preserves the
legacyExchangeDN when Outlook delivers the message. Therefore, the
homeMDB lookup may fail. Troubleshooting: Verify the recipient address
and resend the
message. Verify that the recipient address is formatted correctly
and that the categorizer was able to correctly resolve the recipient.
. Numeric Code: 5.1.1

Possible Cause: . The e-mail account does not exist at the
organization the message was sent to. This issue may occur if there
was a problem when users were moved between sites. For example, if a
former Administrative_Group_1 user moves to Administrative_Group_2
and then replies to an old e-mail message, or if the user does not
re-create his or her Outlook profile, an old Administrative Group
style LegDN address will be used, and an NDR is generated.
. The message was sent to obsolete personal address book
entries.
. The categorizer rejected delivery because you
configured your SMTP contact with see comment SMTP RFC821 characters.
Troubleshooting: Use the troubleshooting procedure described for
numeric code 5.1.0.

--------
--
/kj

--
/kj


.

Relevant Pages

  • Re: How to remove a mail domain
    ... My active directory domain name is gistek.local and my public on informi.dk ... I know the suggestions seemed redundant, but from the results it seems like Exchange still believes it is authoritative for the domain. ... This should ensure that Exchange doesn't try to delivery mail to this domain locally. ... Can you re-verify this and re-report the whole NDR message. ...
    (microsoft.public.windows.server.sbs)
  • Re: Ex2003 NDR Looping
    ... >There are always about 1500 of these messages in the Deferred Delivery ... That mail (the NDR) is being passed to your smarthost. ... I say why the Exchange server is sending a NDR back to the smarthost. ...
    (microsoft.public.exchange.admin)
  • Re: delayed email
    ... then you can track and see if Exchange ... > This is the first time I can remember getting and NDR. ... >> there some external recipients? ... >>> This is an automatically generated Delivery Status Notification ...
    (microsoft.public.exchange.admin)
  • RE: Sent mail delays (all external mail)
    ... > probably mails to non-existent users from your exchange server. ... > You can right-click on these and choose delete no NDR. ... > In global settings on the properties of message delivery. ... Looking in the queues, I see tons of NDRs for obvious spam and mass mailing ...
    (microsoft.public.exchange2000.admin)
  • RE: Preventing reverse NDR attacks...
    ... I understand that you want to secure the Exchange server and avoid the NDR ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)