[ExchangeList] Re: Recipient filtering - Exchange 2003

  • From: "Carl Houseman" <c.houseman@xxxxxxxxx>
  • To: <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 23 May 2006 12:44:07 -0400

Yep, I did all of those things.  Still doesn't work.  Haven't bounced the
server yet.

  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Michael B. Smith
Sent: Monday, May 22, 2006 8:43 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003


It should work. Did your reset of Exchange services include an IISreset?
 
The most specific connector wins in an even-cost situation.
 
  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Carl Houseman
Sent: Monday, May 22, 2006 10:47 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003


I just gave this a try on the "lab" system.   Doesn't seem to work.   The
message ignored the connector which specified yahoo.com in the address space
and used the regular connector.  I even stopped and restarted all Exchange
services with no change in behavior.
 
Maybe I did something wrong, but I have another connector which specifies
certain address spaces for directing to a smart host, and messages route via
that connector based on recipient domain just fine.   The default connector
has a cost of 2, the other connectors have a cost of 1.
 
Carl

  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of MAHADEVAN
Subramanyan
Sent: Monday, May 22, 2006 8:50 AM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003



Yes Mark, it seems to be good.

But since I have configured one of the SMTP connector with * in the address
space, will this meet the requirement, if I configure another SMTP connector
with "yahoo.com" in address space with a lower/higher cost??? Since it needs
to be done in the production environment, I just want to confirm.

Thanks, Mahadevan

  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of Mark Fugatt
Sent: Monday, May 22, 2006 3:16 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003

What you could do is create an SMTP Connector with the address space of
yahoo.com and then set to deny messages from all users.

Mark Fugatt 
Dedicated Supportability Engineer (Exchange) 
Microsoft Limited
Desk:   +44 (0)118 909 5630
Mobile: +44 (0)7966 858108
MSN IM: markfu@xxxxxxxxxxxxxxxxx
Blog: http://blogs.technet.com/mfugatt

Dedicated to proactively supporting Microsoft's enterprise Customers

If you have any feedback about my work, please let either myself or my
manager Andy Gitsham know at andygi@xxxxxxxxxxxxx
<mailto:andygi@xxxxxxxxxxxxx?subject=Feedback%20on%20Mark%20Fugatt%20(Exchan
ge%20DSE)>  or telephone +44 118 909 3233

  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of MAHADEVAN
Subramanyan
Sent: 22 May 2006 10:35
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003

Mark.

We are just trying to block mails that are addressed to yahoo.com fro our
exchange server.

I hope sender filtering is to filter mails which are addressed to our
exchange server from any other external domain (eg: incoming mails from
yahoo.com is blocked using sender filtering)

Thanks, Mahadevan.

  _____  

From: exchangelist-bounce@xxxxxxxxxxxxx
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of shorabh upadhyay
Sent: Monday, May 22, 2006 2:57 PM
To: exchangelist@xxxxxxxxxxxxx
Subject: [ExchangeList] Re: Recipient filtering - Exchange 2003

Hi,

             I thinks you are looking for  " Seder Filtering " not for
recipient filtering.Becasue you are looking to Prohibited  to send the mails
to a particular domain in your case which is @ yahoo.com.
             You have  to add this Domain in Sender filtering instead of
recipient filtering.
 

On 5/22/06, Mark Fugatt <markfu@xxxxxxxxxxxxx> wrote: 

http://www.msexchange.org
-------------------------------------------------------That's not what
Recipient Filters are intend to do, the purpose of a Recipient Filter is to
block incoming mail to a certain email address. 

Mark Fugatt
Dedicated Supportability Engineer (Exchange)
Microsoft Limited
Desk: +44 (0)118 909 5630
Mobile: +44 (0)7966 858108
MSNIM: markfu@xxxxxxxxxxxxxxxxx  <mailto:markfu@xxxxxxxxxxxxxxxxx> 
Blog: http://blogs.technet.com/mfugatt
Dedicated to proactively supporting Microsoft's enterprise Customers
If you have any feedback about my work, please let either myself or my
manager Andy Gitsham know at andygi@xxxxxxxxxxxxx or telephone +44 118
9093233



-----Original Message-----
From: exchangelist-bounce@xxxxxxxxxxxxx
<mailto:exchangelist-bounce@xxxxxxxxxxxxx>
[mailto:exchangelist-bounce@xxxxxxxxxxxxx] On Behalf Of MAHADEVAN
Subramanyan
Sent: 22 May 2006 09:10
To: exchangelist@xxxxxxxxxxxxx  <mailto:exchangelist@xxxxxxxxxxxxx> 
Subject: [ExchangeList] Recipient filtering - Exchange 2003

http://www.msexchange.org
-------------------------------------------------------We have Exchange 2003
SP1 & Windows 2003 SP1 Active directory. 

Currently our exchange is configured to forward all mails to one of the
smart host (remote machine). We have configured sender filtering and it is
working fine. But if we configure the recipient filtering to block outgoing
mails to a particular domain (Say for eg: @* yahoo.com*), it is not working
and still we are able to send message to that domain.

Kindly let me know if the recipient filtering will work in our current
exchange configuration (forwarding mails to smart host).


Thanks, Mahadevan
Confidentiality Statement:

This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient) or
copying this information. If you have received this communication in error,
please notify us immediately by return email. 
-------------------------------------------------------
List Archives: //www.freelists.org/archives/exchangelist/
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com  <http://www.techgenix.com> 
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx

ge.org

-------------------------------------------------------
List Archives: //www.freelists.org/archives/exchangelist/
<//www.freelists.org/archives/exchangelist/> 
MSExchange Newsletter: http://www.msexchange.org/pages/newsletter.asp
MSExchange Articles and Tutorials:
http://www.msexchange.org/articles_tutorials/
MSExchange Blogs: http://blogs.msexchange.org/
-------------------------------------------------------
Visit TechGenix.com for more information about our other sites:
http://www.techgenix.com
-------------------------------------------------------
To unsubscribe visit http://www.msexchange.org/pages/exchangelist.asp
Report abuse to listadmin@xxxxxxxxxxxxxx




-- 
Thanks and Regards,

Shorabh S. Upadhyay
Engineer - Exchange Server Support
Progressive Infotech (P) Ltd.
# +91-9891535899 

Confidentiality Statement:

This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient) or
copying this information. If you have received this communication in error,
please notify us immediately by return email.

Confidentiality Statement:

This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient) or
copying this information. If you have received this communication in error,
please notify us immediately by return email.

Other related posts: