Re: Exchange Error
- From: Bilbo <wlp<faux>fake<at>email<dot>hal-pc.org>
- Date: Mon, 18 Feb 2008 21:16:36 -0600
On Mon, 18 Feb 2008 18:06:18 -0600, Bilbo
<wlp<faux>fake<at>email<dot>hal-pc.org> wrote:
I have just this weekend converted two (2) e-mail domains from an
outside ISP to our SBS 2003 Exchange SP2 server. I had a few hiccups
but apart from failure to get reverse DNS setup by the DNS host,
things began to look sorta OK. I even managed to get a user up on
RPC-HTTP and it's working for her.
Tomorrow, the users come back to work and begin to use their email in
earnest. I began to relax.
Then, THIS thing blew out: (domains and server munged by me)
Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3015
Date: 2/18/2008
Time: 3:53:57 PM
User: N/A
Computer: SERVER
Description:
A non-delivery report with a status code of 5.3.0 was generated for recipient rfc822;
addressee@xxxxxxxxxxxxx (Message-ID
<86EB40A8E885BF458F6B517B1A250B0801D4F2@xxxxxxxxxxxxxxxxxxx>).
Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA route.
For more information, click http://www.microsoft.com/contentredirect.asp.
Solution: Check your route and topology; use the winroute tool to ensure
the routes are properly replicated between servers and routing groups.
Notice that the .local domain was used for this one. I've just
completed a line-by-line audit of my user email addresses and ALL of
them have public domains as their defaults and NO account has the
local domain as its default. So, I'm stumped.
Clicking on http://www.microsoft.com/contentredirect.asp link produces
the famous "We're sorry..." screen.
I've never seen winroute before but if it's anything like EXBPA, it
won't tell me a think I can understand.
I still have that local domain in the Recipient Policies list but of
course, it's not the default. Should I uncheck it? Does that have
any bad implications about Windows Login?
I feel like I'm awfully close to being smoothly running but this
worries me.
Suggestions appreciated...
I've run WinRoute and it doesn't seem to tell me that anything's
wrong. There are two entries at the end named "Denied Originators"
and "Denied Distribution Lists" which have little red "x" on their
icons as opposed to the "Allowed..." versions which have little blue
checkmarks. I've been able to find nothing that explains the real
significance of these icons/glyphs so I'm not sure if WinRoute is
trying to tell me something's bad or that it couldn't find anything.
My Server is SBS2003 SP1 (Exchange SP2) (Win2003 SP2) that has just
had two e-mail domains moved onto it from outside. It also has AUTD
running for the benefit of the boss's pocket PC (WM5) (Cingular 8125)
and it has Intelligent Message Filter running plus TrendMicro's
Client/Server Messaging Security (v6) with spam filter running. The
server allows neither NDRs nor Delivery Reports. It does support the
Out-Of-Office Assistant functions including forwarding to the
internet. And it's also supporting RPC-HTTP connections.
This server hasn't yet carried any real traffic but that'll change in
the morning. At extremely low traffic levels, it seems to be doing
what we want it to do. We are receiving an awful lot of SPAM and IMF
seems to be doing a creditable job of dealing with it. Trend seems to
complement it nicely.
But the "acid test" will start in about 8-1/2 hours. THEN, I'll start
getting LOTS of feedback -- or not?
Thanks for any insights.
--
BilBo
.
- Follow-Ups:
- Re: Exchange Error
- From: Duncan McC
- Re: Exchange Error
- References:
- Exchange Error
- From: Bilbo
- Exchange Error
- Prev by Date: Re: ID-ing Hackers
- Next by Date: Re: VSS Errors in EventID and problems with ntbackup
- Previous by thread: Exchange Error
- Next by thread: Re: Exchange Error
- Index(es):
Relevant Pages
|
