Re: Filter Recipients who are not in the Directory not working?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



No RBL lists domains just because that functionality is not working. If you
ended up in an RBL that probably means you have more serious problems. Maybe
you are an open relay?

Check the exact reason why you was listed in the RBL. This really should be
your top priority.

You may want to test your IP and DNS using the online test from here:
www.dnsstuff.com


--
Alexander Zammit
WinDeveloper Software
IMF Tune - Unleash the Full Intelligent Message Filter Power
http://www.windeveloper.com/imftune/


"John D. Gwinner" <jgwinneratdazsidotcom@xxxxxxxxxxxx> wrote in message
news:ecBPrf5SHHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
No one has any idea?

We've gotten listed on RBL's as a result of this issue! I hope no one
else is having this.

== John ==


"John D. Gwinner" <jgwinneratdazsidotcom@xxxxxxxxxxxx> wrote in message
news:%231mADpwSHHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
Folks:

I'm having some issues with Backscatter.

I'm looking to turning on "Filter Recipients who are not in the
Directory"

I've followed all the instructions:

Global Settings->Message Delivery->Recipient Filtering->"Filter
Recipients who are not in the Directory" ON
Server->Protocols->SMTP->Default SMTP->General->Advanced->(IP
address)->Apply Recipient Filter ON
(Actually, ALL of the filters are checked).

If I have a specific email address listed in the Recipient Filtering, my
SMTP server does generate a:
550 5.7.1 Requested action not taken: mailbox not available

However, if it's someone that doesn't exist in the AD at all, I get a
2.1.5:
250 2.1.5 bullpucky@xxxxxxxxxx

(DNS name changed to protect the guilty).

I don't have an email account named Bullpucky, nor joebob, nor
whothehellcanfigurethisout@xxxxxxxx

All of these generate 2.1.5's.

Any idea why an individual Recipient listed would work, but the Active
Directory Check wouldn't?

No errors in the Event Log.

My tarpitting DOES seem to work - at least, the 5.7.1 does take a while
to generate, but the non AD mail accounts return the 2.1.5 right away.

I've stoped and restarted both the raw service (Service control manager)
and the SMTP server in the Protocols tab.

I've hit the docs and helpfile and I don't see that "Filter Recipients
who are not in the Directory" is exclusive with anything.

Mail delivery is working fine - no errors.

Exchange 2003, SP2, On Windows Enterprise Server 2003, Active Directory,
single forrest, all patched up.

== John ==





.



Relevant Pages

  • Re: Filter Recipients who are not in the Directory not working?
    ... IMF Tune - Unleash the Full Intelligent Message Filter Power ... Check the exact reason why you was listed in the RBL. ... Recipients who are not in the Directory" ON ...
    (microsoft.public.exchange.admin)
  • Re: SBS/Exchange 2003 Incoming mail lockdown using Postini
    ... We contract with Postini ... > 3)Right click on Message Delivery and select properties ... > 5)Enable Filter Recipients who are not in the Directory ...
    (microsoft.public.exchange.admin)
  • Re: Edit reicpient not resetting -
    ... "Peter Jamieson" wrote: ... simplest way to clear out the old filter conditions. ... closes the source and re-opens it, and assign it to a toolbar button. ... Have found that if the previous user has filtered the recipients and I ...
    (microsoft.public.word.mailmerge.fields)
  • Re: Edit reicpient not resetting -
    ... Word complicates things by using two different methods to filter. ... closes the source and re-opens it, and assign it to a toolbar button. ... Have found that if the previous user has filtered the recipients and I ... want to EdIt the recipients a different way. ...
    (microsoft.public.word.mailmerge.fields)
  • Re: SMTP communication problem with the recipients email server
    ... Spam Filters such as Nemx Power Tools for Exchange 2000/2003 are able to ... Filtering is based upon RBL, ... The different recipients do they exist in the same domain as the one ...
    (microsoft.public.exchange.admin)