Link to home
Start Free TrialLog in
Avatar of bwander
bwander

asked on

SBS 2003, Exchange outbound mail fails with 4.3.2

We recently installed SBS 2003 Std. and in Exchange we have messages destined for a particular domain that will not go out.  If I fail the messages I receive the following NDR:

This message was rejected due to the current administrative policy by the destination server.  Please retry at later time. If that fails, contact your system administrator. <#4.3.2>

This is default install.

I have seen some solutions referencing this error, but they appear to apply to EXCH 5.5 migrations, not fresh installs.

Any ideas?
Avatar of Locst3r
Locst3r

What is the output you get from message tracking?
the destination server may not have set up a recipient policy for that domain

Try to telnet to port 25
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q153119&

this will find out if you can communicate with the remote server...we can find out more from there...

Have you checked www.mail-abuse.com or www.ordb.org to see if
you're listed as an open SMTP relay?

Also contact that destination domain to see if they have you on any blocklists.

Also, some domains perform a Reverse lookup, so if your external IP address
does not have  a PTR record, they will block the mail. Still others will
block mail that comes from a range of IP addresses that are know to be
dynamic subnets
to see the last comment about reverse dns go here http://www.dnsstuff.com/pages/expert.htm
Avatar of bwander

ASKER

I have looked at the message tracking log, but I don't see anything that would help me resolve the issue.  What should I look for?


The destination domain is blackberry.net.  I tried to telnet to port 25, but was unsuccessful.

We are not listed as an open SMTP relay.

you could try and set up a smart host to deliver to this domain http://support.microsoft.com/default.aspx?kbid=297988&product=exch2k
Avatar of bwander

ASKER

Additional info:

The messages being sent are from the blackberry redirector software running on our PCs.  We didn't have any problems with a Windows 2000 Server, running Exchange 2000 SP4.  It was only after upgrading to SBS 2003 (running Exchange 2003) that this problem appeared.

Any other ideas?
ASKER CERTIFIED SOLUTION
Avatar of bwander
bwander

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I have found that Exchange 2010 generates that message when port 25 on the firewall is blocked outbound.