Solved

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

Posted on 2004-09-27
8
11,725 Views
Last Modified: 2011-08-18
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.
0
Comment
Question by:gritzalis
8 Comments
 
LVL 15

Accepted Solution

by:
plimpias earned 125 total points
Comment Utility
Make sure your firewall is allowing you to send out for port 25 and 110 TCP.
0
 

Author Comment

by:gritzalis
Comment Utility
Firewall does allow for that. I can connect to Port 25 on others mail servers.
0
 
LVL 3

Assisted Solution

by:ans-ansdenver
ans-ansdenver earned 125 total points
Comment Utility
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
 

Author Comment

by:gritzalis
Comment Utility
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
Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

 
LVL 20

Assisted Solution

by:ikm7176
ikm7176 earned 125 total points
Comment Utility
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
 
LVL 13

Assisted Solution

by:George Sas
George Sas earned 125 total points
Comment Utility
What if you FORCE connection ?
What if you send a mail to yourself ?
Have you enabled any kind of Filtering on your exachange?
0
 

Author Comment

by:gritzalis
Comment Utility
The problem was the fortinet Firewall.
Although the policy were right, it needed a reboot.
0
 
LVL 13

Expert Comment

by:George Sas
Comment Utility
:)
Good you solved the problem.
Sometimes it helps to restart the Exchange services.
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.

772 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now