locked
Mail Restriction forExchange 2007 Users. RRS feed

  • Question

  • Hi guys.

        I am to new this forum . I hope all forum members are fine.I have one query from my Management Side.We are using Exchange Server 2007 With 1 Mailbox Server,1 Hubtransport&CAS Role Server,1 Edge Server.Need from my management side is to be make some users not able to send mails to particular domain(some users only) but they can able to send mail apart from restricted domain.For E.g client1 & client2,client 1 is restrict to unable send mails to yahoo,gmail but able to send mails apart from restricted domain,client 2 able to send mails to all domain.

       When  I tried Transport rule in Edge server it not send mail if one of the id contains restricted domain.For e.g if i want to restrict yahoo,when send mail to yahoo only means its working,but when send mail to yahoo,gnail,hotmail it(Rule) restrict all mails not to relay due to presence of yahoo id when sending mails.


    I hope you are all the guys understood my problem.
    Please revert back me as soon as possible.Thanks a tone.
    Saravanan
    Saturday, January 10, 2009 9:58 AM

Answers

  • Hi,

    That is the normal behavior in this scenario. To reach your goal, we need to separate the different destination email into two ways, you can refer to the following operations:

    1, Deploy another Edge server in your environment.
    2, Don't create Edge Subscription between Hub and Edge server
    3, Create two send connector and configure Edge 1 and Edge 2 as the respective smart host on the send connector.
    4, In the one of the send connector, set the address space as restricted domain, such as yahoo.com, then create the corresponding Transport rule on the associated with Edge server.

    If you plan to saving cost, we can also achieve this aim on the current topology, the steps is create another send connector and set * as the address space. The address space is restricted domain (yahoo.com) on the send connector on the Edge server. But this is very danger since the security is very low due to Hub server needs to be published.

    Thanks

    Allen

    • Marked as answer by Allen Song Wednesday, January 28, 2009 8:15 AM
    Monday, January 12, 2009 9:19 AM

All replies

  • A transport rule would be my first thought, but I would have created it on your internal environment instead. This would be easier to manage with group membership or AD attributes instead of just plain SMTP addresses on your Edge server.

    How does your rule look like?
    larsp at avanade dot com, http://anewmessagehasarrived.blogspot.com
    Saturday, January 10, 2009 6:18 PM
  • Hi,

    That is the normal behavior in this scenario. To reach your goal, we need to separate the different destination email into two ways, you can refer to the following operations:

    1, Deploy another Edge server in your environment.
    2, Don't create Edge Subscription between Hub and Edge server
    3, Create two send connector and configure Edge 1 and Edge 2 as the respective smart host on the send connector.
    4, In the one of the send connector, set the address space as restricted domain, such as yahoo.com, then create the corresponding Transport rule on the associated with Edge server.

    If you plan to saving cost, we can also achieve this aim on the current topology, the steps is create another send connector and set * as the address space. The address space is restricted domain (yahoo.com) on the send connector on the Edge server. But this is very danger since the security is very low due to Hub server needs to be published.

    Thanks

    Allen

    • Marked as answer by Allen Song Wednesday, January 28, 2009 8:15 AM
    Monday, January 12, 2009 9:19 AM
  • Hi guys,

         Thanks for all your Responses.I am achieved those things using Trend Micros - IMSS.
    Saravanan
    Tuesday, February 17, 2009 11:52 AM