550 5.7.1 Requested action not taken: message refused, caused by IMF

Hi all,

For several weeks now, exchange IMF rejects messages received from a certain external domain to only one of the company employee's email adresses.

By testing and sending mails (also via telnet sessions). If i try to send a mail from that domain to the person, i get the error message:
"550 5.7.1 Requested action not taken: message refused
Connection closed by foreign host."

If i then check Message Tracking Center, there are messages "SMTP: Message rejected by Intelligent Message Filtering".

I just enabled archiving and already mails from that external domain are getting dumped in the archive folder.
Even by setting the SCL scale levels to 9 it rejects the external domain.

Is there any way to let IMF accept mails from this domain?

The server is a SBS 2003 with Exchange 6.0 & exchange SP2.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You could use the Global Accept List to enter the IP of the mail server that is trying to send to  you.  That is on the Global Settings/Message Delivery Properties window, Connection Filtering tab, Accept button.
techneitsolutionsAuthor Commented:
Hmm, ok. that could be a solution.

I can't use an ip adres since the domain is owned by a large ISP company, they have serveral relay servers in different ip ranges.

So that is why i want to allow a FQDN.

Right, that is my biggest complaint with IMF - it only allows global accept/denies by IP and not domain.  I've written a basic whitelisting script that will redeliver by domain or address without modifying your existing Exchange and IMF setup.  Please see question 22157822 for the code.


Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
techneitsolutionsAuthor Commented:
Hey nice workarround. So i'll have to leave the archive option enabled then.

Time for some cleanup scripting :)

Yes, in your case you could just add the problematic domain to the whitelist and check the weekly archive folders if anyone complains of not getting all their email.  That's more of a reactive approach instead of proactive, but some of us have a lot more important things to do than look at 15,000 blocked emails a week to see which ones are valid....

I hope this proves to be a viable workaround. Thanks for the points and grade!
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.