This message was rejected due to the current administrative policy by the destination server

I get this NDR report back. I can receive mail from anywhere but I cant send to any email address all are stuck in the queue Please help.
gritzalisAsked:
Who is Participating?
 
plimpiasConnect With a Mentor Commented:
Make sure your firewall is allowing you to send out for port 25 and 110 TCP.
0
 
gritzalisAuthor Commented:
Firewall does allow for that. I can connect to Port 25 on others mail servers.
0
 
ans-ansdenverConnect With a Mentor Commented:
Are you on a blackhole list, spam list? is your reverse DNS set up? When you say " can not send to all " what are your test sending to? Can you post an NDR?  It there a 550 error? Does your email server send to a smart host for filtering or virus?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
gritzalisAuthor Commented:
I'm not blacklisted or spam listed

Reverse DNS is setup

I have used different types of email addrress to send but cant not inc. hotmail and yahoo

I use DNS to send not smarthost

NDR -->This message was rejected due to the current administrative policy by the destination server

Error 4.3.2

0
 
ikm7176Connect With a Mentor Commented:
restart the SMTP service on your exchange server or start SMTP Virtual server in the ESM. All the exchange services should be started.

If you are using smtp connector check the connector delivery restrictions and relay restrictions.

4.3.2 - This NDR is generated when a queue has been frozen. Unfreeze the queue

This error seems to occur due to misconfiguration on your exchange server.
0
 
George SasConnect With a Mentor IT EngineerCommented:
What if you FORCE connection ?
What if you send a mail to yourself ?
Have you enabled any kind of Filtering on your exachange?
0
 
gritzalisAuthor Commented:
The problem was the fortinet Firewall.
Although the policy were right, it needed a reboot.
0
 
George SasIT EngineerCommented:
:)
Good you solved the problem.
Sometimes it helps to restart the Exchange services.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.