Re: filter recipients who are not in the directory questions

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Unfortunately, the linux which is the relay and anti-spam will stay there.
The client decides and I have no power on changing anything regarding the
mail architecture. Since the linux deletes all spam that it receives, the
level of identification must stay low.

I will try to put the setting back (filter recipients who....), put back the
tarpit registry, and remove the linux from the smtp properties (relay). I
think this will make an anonymous smtp connection to the exchange so that the
filtering will work. But this is an opinion only. Not sure this will work. I
just don't understant why even though I am using this setting, it does not
work on the only network that I have a mail relay in front of the exchange
which appears in the smtp properties for relaying.

Thanks for your ideas.

"Ben Winzenz [Exchange MVP]" wrote:

> So if a remote server is offline for an hour, any mail that you try and send
> to them will get NDR'd back to your sender?
>
> It's not what I would recommend. There is a reason that the defaults are
> what they are. 20 minutes is way too low IMHO.
>
> If you are doing this to deal with NDR's to invalid outbound recipients
> (from spam or viruses), then having a good antispam solution should take
> care of this for you. That, or put some other smtp server in front of
> Exchange (inbound) that doesn't accept encapsulated addresses like Exchange
> does.
>
> --
> Ben Winzenz
> Exchange MVP
> MessageOne
> Read my blog!
> http://winzenz.blogspot.com
> http://feeds.feedburner.com/winzenz (RSS Feed)
>
>
> <joedonato@xxxxxxxxx> wrote in message
> news:1138298936.815079.165790@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > What we have done to lower our NDR queue is to just drop anything that
> > can't be delivered after 20 minutes.
> >
> > Assuming your exchange server is delivering directly to the internet...
> > On the SMTP Properties Delivery tab change Outbound mine is set like
> > this...
> >
> > 1st 6 Min
> > 2nd 5 Min
> > 3rd 4 Min
> > subsequent 3 Min
> > Delay Notif 17 Min
> > Expiration timeout 20 Min
> >
> > This greatly reduces our queue and we have not seen any ill effects,
> > make sure you keep your local at least a day.
> >
>
>
>
.

Relevant Pages

  • Re: Exchange Server 2003 - Relay
    ... Exchange, i.e. relay or do you want outbound email to go through the spam ... I'm running a linux box to do Spam flitering - ... You need to add an SMTP connector then set the linux server as a Smart ...
    (microsoft.public.exchange.admin)
  • Re: Exchange Server 2003 - Relay
    ... i.e. relay or do you want outbound email to go through the spam ... You should always use a connector if you want to smarthost. ... I'm new to Exchange 2003, I'm running a linux box to do Spam ...
    (microsoft.public.exchange.admin)
  • Re: Exchange Server 2003 - Relay
    ... Exchange, i.e. relay or do you want outbound email to go through the spam ... You should always use a connector if you want to smarthost. ... I'm running a linux box to do Spam flitering - ...
    (microsoft.public.exchange.admin)
  • Problem setting up relay
    ... Exchange deals with internal email fine. ... The IP of the linux box is entered into the relay section of Exchange. ...
    (microsoft.public.exchange.admin)
  • Re: Internal Email Relay
    ... I'd like this box to relay internally to the exchange server ... users on the Linux box and gradually move everyone to Exchange. ... forward is tdenham@xxxxxxxxxxxxxxxxxxxxx the smtp properties had to be ...
    (microsoft.public.exchange.admin)