Re: Cannot send mail to "some" domains

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

Jim

When I go into the recipient policy tab I have 4 policies.

The first is the Organizations name and is set to highest. The filter is:
(&(mailNickname=*)(legacyExchangeDN=/O=xxxxx/OU=xxxxx/*))

Under the Policy tab I only have my SMTP address and X400 checked. This is
the SMTP address on the regular emails.

The 2nd policy is "Excluded Users from Mailbox Cleanup and is set to 1st.
The filter is:
(&(& (objectClass=user)
(|(mailnickname=user)(mailnickname=user)(mailnickname=user))))

Nothing is selected and it is set to Generate Report Only. I am told this
is the policy to not have the 3 users deleted items cleaned every 30 days.
But nothing is selected in the Policy tab. ????

The 3rd policy is "Office" with a priority of 2. The filter is:
(&(&(& (mailnickname=*) (|
(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*))) ))))

Sent, Deleted items and System Cleanup are selected and Delete immediately
is in the drop down. I am told this is the policy that runs against everyone
to clean out the mailboxes.

The last policy is called "default Policy" and its priority is set to
lowest. The filter is:
(mailnickname=*)

They have 9 SMTP addresses listed with only 8 selected. The one that is
Primary is the same SMTP address in the first policy which is our domain.
The X400 is also selected.

I have 2 RUS configured. One for the Enterprise and another for the domain
name. Both have the new Exchange Server listed and pointing to the FSMO
Domain Controller.

Any help would be appreciated.

Thanks




"Jim" wrote:

no worries...I can hang with you, at least until I have passed on all that I
know to check... : )

To verify:

Open ESM, Expand Recipients, select Recipient Policies, select any of the
policy and rt. click, select properties, on the first tab (General) that
appears, look in to the Filter Rules box and check what is listed. If the
policy is not the Default Policy (ie one that has been created), then you
should see information specific to the mailbox store, server, etc.

You might want to enable Message tracking and then try sending test emails.
Then go to the Tools section in ESM, select message Tracking Center, then
fill out the info on the right, select Find Now...once it returns a set of
results in the white space below, you can click on the result and it will
give you more information as what is happening to the message.

Also, you mentioned that you have a connector to your Old Exchange? Has
that been removed?

The messge track will show you how that message is moving in/out of your
system...and if there is a connector component, it will show up in the
message track info.


"aja44" wrote:

Jim,

I was able to test SMTP from the Exchange server and was able to connect and
send an email. I immediately received the NDR in OWA. I also went into ADUC
and deleted the contact for the user, force replicated between my 2 DC's and
then tried to send an email via OWA to the user and immediately received the
NDR.

I currently find 4 Recipient Policies. One is named for the Organization
and has 8 or 12 SMTP addresses listed and checked. None of which are the
domains I cannot send to. Another is the default policy which just has my
domain's SMTP address along with the X400. The other 2 policies are for Mail
maintenance (one to setup when and the other to exclude 3 users from having
their deleted items deleted). I have run the RUS and has not fixed anything.
I do not know enough about these policies to want to delete them and
recreate them. Is there a utility that I can run to see if the domains I am
having issues sending to are somehow in my system? One of the email
addresses is user@xxxxxxxxxxxxx which I know we dont host that domain so that
may be a moot point.

Since we moved everything from our old server to the new one I have stopped
replication for the Public Folders, moved all the mailboxes, and deleted the
SMTP connector between the two boxes. I do however have the old server still
up and running with Exchange installed on it. I was afraid to take it down
until this was fixed but could this be causing a loop of some kind?

You also mentioned confirming that the recipient policy is applied to the
new server, how can I confirm that?

Thanks again for you time and patience...



"Jim" wrote:

Though the recipient policies are global you must still select the mailboxes
to which the policy will apply. If you have moved the mailboxes, you might
want to verify that the policy is being applied to the Exchange server where
the mailboxes are actually sitting. I do not recall if the settings will
automatically follow the mailboxes...Susan may have the answer to
this...sorry, I don't recall.

The smart host is defined within the properties of the SMTP protocol, which
is server specific. Though this is a moot point, as you have said you do not
use a smart host.

If you are not performing smtp relaying, I have always found it best to
perform smtp tests from the actual Exchange server, as that is the box that
is trying to connect to other mail servers. By performing the test on the
actual Exchange server, you may end up discovering that the problem could be
a network or other issue (Layer 1, Layer 2, layer 3, etc.).

Based on your description it sounds like there is a conflicting address in
your AD (such as a Contact). If you have contacts defined in your ADUC, are
you forwarding them as well? If you find Contacts, as a test...can you
delete them and then try sending to the address?

"aja44" wrote:

Jim,

Thanks for helping...

They are external addresses I am trying to send to. There is no recipent
policy defining any SMTP address for these domains. I am told that a few
years ago one of the domains was on their old server but not any more. I
checked through the default and a domain named Recipient policys and they do
not have the SMTP addresses stated.

And I found 2 of the 3 accounts I have been told email gets bounced back to
have contacts in the AD. I deleted one of them and re-created it and it
still failed.

Thanks,
The Exchange Server is NOT in the DMZ. I do not know what a smarthost is?
This was a working 2000 Exchange server and this problem began after we moved
the mailboxes and Public folders to the new 2003 Exchange Server. But dont
all the Recipient Policies and a smarthost be part of the Domain and not the
individual server? New to Exchange 2003.. :-)



I do not think I tried sending via Telnet on the Exchange server last night.
I did it from my home PC. I do not have the VPN client on the machine I am
on now so will have to try that when I am home tonight. Does that make much
of a difference if I do it from the Exchange server commandline or from any
machine?




"Jim" wrote:

Also, do you have contacts set for any of these users that you are trying to
send to?

"aja44" wrote:

Jim,

Thanks,

I was able to telnet to my server and send email to myself as well as my
personal account via telnet. I still received errors sending this way to the
same domains I was having issues with using OWA or Outlook. I am either
getting the following errors: 5.1.1 or 5.4.6

I deleted the contact in AD for the one user that received the 5.4.6 error
and recreated it. I then received the 5.1.1 error the first few times I
tried to send and then eventually went back to the 5.4.6 error.

HELP PLEASE

"Jim" wrote:

The following has always worked for me when testing:

1. Telnet to server host (FQDN) or IP using port 25
2. type helo (sometimes you may need to type the domain name in addition to
helo)
3. mail from: email address <Enter>
4. rcpt to: email address <Enter>
5. data <Enter>
6. Subject: whatever <Enter>
7. Type message <Enter>
8. <Enter>
9. .
10. <Enter>
11. quit <Enter>


hope this helps,

Jim




"aja44" wrote:

Susan,

I must be doing something wrong because it keeps failing and I tried to
connect to other mail systems that I know are up and running and can't
connect there either. I am using:

telnet mail.domain.com 25

Is that correct?

"Susan" wrote:

I would try sending an email to one of these addresses/domains via a telnet
session? sometimes you can get more information that way...

--
Susan Conkey [MVP]



"aja44" <aja44@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A7D2F58D-5BB1-49A8-85BE-ED86505AB8BD@xxxxxxxxxxxxxxxx
We recently performed an Exchange migration from 2000 to 2003 on new
hardware. We can send internal email with no issues. I have not been
told
of anyone not receiving inbound emails at this time. But I have had 2 or
3
people say that they can no longer send emails to particular domains. I
have
seen two different types of Error Messages returned to the users inbox. I
have tried sending from different accounts logged in on Outlook or OWA and
I
get an immediate Undeliverable message in my inbox. I can however send to
the addresses from my personal email account outside. When I go into the
Event Viewer on my Exchange Server I do not have any NDR listed or errors.

Error 1 :
Your message did not reach some or all of the intended recipients.

Subject: test
Sent: 3/12/2007 10:11 PM

The following recipient(s) could not be reached:

user@xxxxxxxxxx on 3/12/2007 10:11 PM
The e-mail account does not exist at the organization this message was
sent to. Check the e-mail address, or contact the recipient directly to
find
out the correct address.
<newmailservername.domain.com #5.1.1>

Error 2:

user@xxxxxxxxxxxxxx on 3/13/2007 12:42 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.
<oldmailservername.domain.com #5.4.0>

Any help would be appreciated.

Regards



.

Relevant Pages

  • Re: company name change
    ... RUS (Recipient Update Service). ... After adding the new SMTP domain in Recip Policies and making it primary, ... Re: uncheck - yes. ... If you furthermore choose to Apply the policy Now ...
    (microsoft.public.exchange.admin)
  • Re: microsoft madness pop3 connector
    ... the default SMTP recipient policy which also includes the domain.local. ... Next, go to the user properties, SMTP address tab. ... >The connector has to validate that the domain specified in the recipient ...
    (microsoft.public.windows.server.sbs)
  • RE: POP3 Connector problems
    ... added to the recipient address, we need to know how POP3 connector works: ... When the pop3 connector downloads email it appends mspop3connector to ... This mail is submitted to SMTP via CDO. ... To add a recipient policy for the expected domain: ...
    (microsoft.public.windows.server.sbs)
  • Re: Reply to policy using pop3 connector and smtp connector
    ... smtp address, ... Recipient policies, you'll see the Default policy. ... > connector so we can send mails from exchange. ...
    (microsoft.public.exchange.admin)
  • Re: Reply address in Exchange
    ... MX records for this SMTP address be added to a public DNS ... >If you send through your Exchange SMTP, ... >apply the default Recipient Policy, ...
    (microsoft.public.windows.server.sbs)