Exchange Help: -------------------------------------------------------------------------------------------------- For servers that have both the Hub Transport server role and the Mailbox server role installed, the only way to remove the server name from the Received: headers of the outgoing message is to use the Remove-ADPermission cmdlet to remove the Ms-Exch-Send-Headers-Routing permission from the security principals that use the connector. This action will remove all the Received: headers from the message as the message leaves the Hub Transport server. We recommend that you don't remove the Received: headers for internal messages, because the Received: headers are used for maximum hop count calculations -------------------------------------------------------------------------------------------------- I want to ask you for something: Give an concrete example of this command for Exchange Managemeny Shell (with all necessary command-line switches). Thanks, Mike.AK (mike.ak@mail.ru)
Removing internal host names and IP addresses from message headers http://exchangepedia.com/blog/2008/05/removing-internal-host-names-and-ip.html -- Bharat Suneja Microsoft Corporation blog: exchangepedia.com/blog This posting is provided "AS IS" with no warranties, and confers no rights. Please do not send email directly to this alias. This alias is for newsgroup purposes only. ---------------------------- "mike.ak" wrote in message news:Ot$717u3IHA.4272@TK2MSFTNGP03.phx.gbl... > Exchange Help: > -------------------------------------------------------------------------------------------------- > For servers that have both the Hub Transport server role and the Mailbox > server role installed, the only way to remove the server name from the > Received: headers of the outgoing message is to use the > Remove-ADPermission cmdlet to remove the Ms-Exch-Send-Headers-Routing > permission from the security principals that use the connector. This > action will remove all the Received: headers from the message as the > message leaves the Hub Transport server. We recommend that you don't > remove the Received: headers for internal messages, because the Received: > headers are used for maximum hop count calculations > -------------------------------------------------------------------------------------------------- > I want to ask you for something: > Give an concrete example of this command for Exchange Managemeny Shell > (with all necessary > command-line switches). > > Thanks, Mike.AK (mike.ak@mail.ru) >
it work !!! thank you very much ! "Bharat Suneja [MSFT]" wrote in message news:%23pmjH1y3IHA.4988@TK2MSFTNGP06.phx.gbl... > Removing internal host names and IP addresses from message headers > http://exchangepedia.com/blog/2008/05/removing-internal-host-names-and-ip.html > > -- > Bharat Suneja > Microsoft Corporation > blog: exchangepedia.com/blog > > This posting is provided "AS IS" with no warranties, and confers no > rights. Please do not send email directly to this alias. This alias is for > newsgroup purposes only. > ---------------------------- > > > > > "mike.ak" wrote in message > news:Ot$717u3IHA.4272@TK2MSFTNGP03.phx.gbl... >> Exchange Help: >> -------------------------------------------------------------------------------------------------- >> For servers that have both the Hub Transport server role and the Mailbox >> server role installed, the only way to remove the server name from the >> Received: headers of the outgoing message is to use the >> Remove-ADPermission cmdlet to remove the Ms-Exch-Send-Headers-Routing >> permission from the security principals that use the connector. This >> action will remove all the Received: headers from the message as the >> message leaves the Hub Transport server. We recommend that you don't >> remove the Received: headers for internal messages, because the Received: >> headers are used for maximum hop count calculations >> -------------------------------------------------------------------------------------------------- >> I want to ask you for something: >> Give an concrete example of this command for Exchange Managemeny Shell >> (with all necessary >> command-line switches). >> >> Thanks, Mike.AK (mike.ak@mail.ru) >> >
