ksb
Guest
|
 Posted:
Thu Mar 31, 2005 5:01 am Post subject:
testing new front-end/smtp problem? |
|
|
new and first front-end server is up. it is running ex2003 with owa, pop,
impa, smtp. We have one ex2k backend server running owa, pop, imap and smtp.
Once cutover into production, we would like to change the dns aliases of the
back-end server to then be the front-end. so, owa users and users of pop and
impa will not need to change the url they use or their incoming and smtp
servers settings.
We have not made those dsn changes yet, but would like to test that all is
working or WILL work once we cut over.
We have owa, pop and imap all working, using the temporary dns name. using
the temp dns name, users are NOT able to send mail to internal exchange
recipients. The ARE able to send to external domains. We have the f/e smtp
configured to use a smarthost at this time for testing purposes.
The error we receive in the app log on the f/e when attempting to send to an
internal Exchange address is pasted at the bottom of this poest.
Question: is it simply not possible for us to test this functionality
before the cutover? Or, did we miss something in the config? TIA!
Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3021
Date: 3/30/2005
Time: 1:40:07 PM
User: N/A
Computer: FE
Description:
A non-delivery report with a status code of 5.4.8 was generated for
recipient rfc822;joe@maildomain.com (Message-ID
<000701c53571$0ba18b00$420f010a@usa.maildomain.blah.blah.org>).
Cause: This message is a warning about a looping condition. One known case
is that one of the recipient policies includes a local domain that matches
the fully qualified domain name (FQDN) of an Exchange server in the
organization. When the Transport Categorizer is processing mail destined for
a domain that matches an Exchange ServerÆs FQDN, it will return NDR the
message with this error.
Solution: Check your recipient policies. If you have a recipient policy
with a local domain that matches the FQDN of an Exchange server in your
organization you must remove that entry. For example, if you have a
recipient policy with server1.example.com, change the recipient policy to
example.com
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in
