Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- From: "Rich Matheisen [MVP]" <richnews@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 16:26:48 -0500
andrew.schmitt@xxxxxxxxx wrote:
>Under "message delivery | general" we have all of the internal network
>in the "Permimeter IP List and Internal IP Range Configuration".
That's fine. That only affects the SenderID stuff.
>I know
>that IMF and connection filtering are different but in the pre-SP2
>environment, as far as I understood a message was checked against the
>"Global Accept List" under Connection Filtering and if it was on that
>list no other filtering would be applied thereafter, IMF or otherwise.
That's true. I misunderstood the information in your description,
thinking "Exception" rather than "Allow".
>So we have our internal network in there as well.
How have you specified that network? Single addresses or by network?
If by network can you post the address and network mask?
>We can setup one of
>the SMTP virtual servers to not apply the IMF filter but the design
>right now has our perimeter postfix server delivering mail to both
>internal systems in a round-robin fashion to help split up the load as
>well as provide some failover.
>
>Did the filtering process change so this is no longer the case?
No, not that I know of.
Do exception addresses under connection filtering affect Intelligent
Message Filter behavior?
Exception e-mail addresses under connection filtering have no
effect on Intelligent Message Filter behavior.
Does Allow Address under connection filtering affect Intelligent
Message Filter behavior?
IP Allow addresses under connection filtering allows mail to
bypass Intelligent Message Filter, which results in messages that
have no SCL value stamped on them. These messages can be filtered
by Outlook 2003 Junk E-mail rules. Intelligent Message Filter does
not specify an SCL by design because content scanning was actually
bypassed. In this case, setting an SCL of 0 would not be an
accurate value from Intelligent Message Filter.
>Is
>there no way at this point to whitelist IP ranges from IMF scanning as
>there was in the past?
What you're doing should work.
--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- From: andrew . schmitt
- Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- References:
- Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- From: Rich Matheisen [MVP]
- Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- Prev by Date: Re: Accessing other mialboxes
- Next by Date: How to detect unused Dist.List?
- Previous by thread: Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- Next by thread: Re: Connection Filtering Allow IPs and Exchange 2003 SP2
- Index(es):
Relevant Pages
|