• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 826
  • Last Modified:

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.
0
techneitsolutions
Asked:
techneitsolutions
  • 3
  • 2
1 Solution
 
TWBitCommented:
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.
0
 
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.

0
 
TWBitCommented:
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.

http://www.experts-exchange.com/Software/Office_Productivity/Groupware/Outlook/Q_22157822.html
0
 
techneitsolutionsAuthor Commented:
Hey nice workarround. So i'll have to leave the archive option enabled then.

Time for some cleanup scripting :)

Cheers!
0
 
TWBitCommented:
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!
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now