Re: SBS 2003 NDRs
- From: "SuperGumby [SBS MVP]" <not@xxxxxxxxxxx>
- Date: Sat, 13 Sep 2008 07:06:24 +1000
actually, you haven't cross-posted (a good thing where one message is sent
to multiple groups) but instead multiposted (bad juju, same question as
separate messages to multiple groups). Crossposting allows people who
participate in each group to track threads properly.
I probably would have got around to finding your message in
microsoft.public.backoffice.smallbiz, which is actually the SBS 4.5
discussion group (and I think should be abolished).
I'm guessing that 'So I've asked for our IP to be unblocked via a web-based
form' is referring to a form at AT&T regarding 'allowed services' in/out of
your IP. If so this should fix the problem.
Meanwhile, you might want to try sending via smart host, using the AT&T mail
server as relay. This can be achieved by running the CEICW, you can tell the
CEICW not to modify the first couple of items, only Exchange, and select the
option to 'forward mail to this server', specifying the AT&T mail server.
"Doc Rock" <DocRock@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A562B1C-066F-4F5E-AC52-8BCD047CA8C0@xxxxxxxxxxxxxxxx
Greetings All,
Please excuse the cross-post (I initially posted this the "Small Business
Server" group, which looks like it doesn't get as much traffic)..
We recently moved office locations and are connected to a newly
provisioned
bonded AT&T T1 circuit (keep in mind we had no issues prior to the move).
Now
I'm getting the following NDRs from AT&T sites, i.e., pacbell.net and
sbcglobal.net:
The message cannot be delivered due to a configuration error on the
server. Please contact your Administrator.
<XXX.XXX.local #5.3.0 smtp;553 5.3.0 nlpi084 - m8CF5nSa003032,
DNSBL:521< our IP
>_is_blocked.__For_information_see_http://att.net/blocks>
So I've asked for our IP to be unblocked via a web-based form. I just want
to make sure I'm going down the right path because when I check the
application logs I see the following:
A non-delivery report with a status code of 5.3.0 was generated for
recipient rfc822;XXX@xxxxxxxxxxx (Message-ID
<9F5A5B2C4B2CA04D817A2AA1383EB799672A7A@xxxxxxxxxxxxx>).
Causes: Exchange mistakenly attempted mail delivery to an incorrect MTA
route.
And just to add to the confusion, when I run the Best Practices tool...I
see
an alert indicating that I don't have the DNS A records listed in the
public DNS resolvers. The A record that's being referenced is the name of
the
local server, i.e., xxx.xxx.local (which doesn't make any sense). I've got
my
forward DNS zones pointing to the public resolvers. I've also got an
appropirate PTR record created for our IP block too..
Thanks for any suggestions.
Dan
.
- References:
- SBS 2003 NDRs
- From: Doc Rock
- SBS 2003 NDRs
- Prev by Date: SBS 2003 NDRs
- Next by Date: Re: Domain name does not stick in third box
- Previous by thread: SBS 2003 NDRs
- Next by thread: Re: SBS 2003 NDRs
- Index(es):
Relevant Pages
|
