Solved

How do I prevent the internal FQDN from showing in the received header - Exchange 2010

Posted on 2010-09-12
23
3,450 Views
Last Modified: 2012-06-21
Exchange 2010 SP1
Lets say MX points to mymail.mydomain.com
The exchange server internal FQDN is red.mydomain.com
FQDN on send connector is set to mymail.mydomain.com

However when I send a message...when external receipient gets msg...the header still shows the internal FQDN of the exchange server i.e. red.mydomain.com

How do I prevent this from showing in the header for external receipient???
you see this in the begining of header...  received: from mymail.mydomain.com
but then the internal name shows as you scroll down...  received: from red.mydomain.com

I tried changing the default in the Server Config > hub T area and removing Exc Auth, restart Transport service, but that did not work
0
Comment
Question by:BigBadWolf_000
  • 11
  • 9
  • 3
23 Comments
 
LVL 32

Expert Comment

by:endital1097
ID: 33657439
set-receiveconnector "client servername" -fqdn mail.domain.com
0
 
LVL 49

Accepted Solution

by:
Akhater earned 400 total points
ID: 33657447
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657709
endital1097: in PS 2010SP1 I do not have a set-receiveconnector  cmdlet
Akhater: I do not have the "Get-SendConnector " cmdlet in  2010SP1
I also did...
get-help set-*
t-help get-*
....I don't see them listed, I am running PS in elevated admin mode
0
 
LVL 32

Expert Comment

by:endital1097
ID: 33657721
you need to run it from the exch management shell
you can also go to properties of the connector from the exch management console and updat the fqdn

you also can check your send connector fqdn in the gui under organization config - hub trnasport - send connector tab
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657786
endital1097: Thanks ...
In EMC - I do have the send connector FQDN set to mymail.mydomain.com  ... and this display s in the start of the header...however in the rest of the references in the Header the internal FQDN is still displayed>>> I tried changing the FQDN for bothe Client and Default in Server Gongig > Hub > receive connectors....restart ExcTransprt Svc....no luck

0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657792
0
 
LVL 32

Assisted Solution

by:endital1097
endital1097 earned 100 total points
ID: 33657803
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33657877
use the link I gave you and run it form EMS (Exchange Management Shell)
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657916
Akhater: I did that....it worked for the receive: part...However, it still displays the internal FQDN in the Message-ID and Content-Type areas of the header....any thoughts
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33657925
you used the article I liked to ? get-sendconnector  & remove-adpermission?
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657947
yes.....although I am not comfortable with removing permissions...I would like to use a transport rule intstead.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 49

Expert Comment

by:Akhater
ID: 33657957
as far as I know it is only doable using the remove-adpermission as shown in the first link I gave you
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657980
But it does not hide is completely still shows with  Message-ID and Content-Type areas of the header
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33657986
did you restart the msexchangetransport service ?
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33657996
yes
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33658004
You said message ID ?

do you mind pasting a relevant portion of the email ?
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33658047
I remove the IP and replaced actual internal FQDN with the one in example....

Date: Sun, 12 Sep 2010 19:55:45 +0000
Message-ID: <09E87EBD9D23234287C62CB74C10CC200469C4@RED.MyDomain.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [xx.xx.xx.xx]
Content-Type: multipart/alternative;
 boundary="_000_09E87EBD23459C4087C62CB74C10CC200469C4REDMyDomain_"
MIME-Version: 1.0
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33658085
i take it this is an outbound email ??
for the message ID please go to Organization config -> hub transport -> pick the send connector
there change/set a FQDN in the reserved place this should solve it


for the x-originating-ip as far as I know it is new with 2010 SP1 you can easily remove it with a transport rule

set your rule applies to emails sent to users outside my organization and in the action remove header x-originating-ip

0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33658269
Akhater: FQDN is alreadyset to externa,l name in  Organization config -> hub transport -> send connector ......and MsgID shows internal name

FYI....transport rule works to remove header "received" to not display internal name
so no permissions need to be changed

However still need help with MsgID and Content-type showing internal name
How can I set multple action values in a transport rule???
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33658284
How can I set multple action values in a transport rule???

actually you can't just create multiple transport rules
0
 
LVL 14

Author Comment

by:BigBadWolf_000
ID: 33658353
It seems like you can set multiple transport rules (with different priorities).....however it does not let me enter multple action values ...like an Outlook rule would...

i.e I want to set for condition outgoing mail...action remove headers...valuse = recieved, message-id....but it lets me put in only one value
0
 
LVL 49

Expert Comment

by:Akhater
ID: 33658357
yes exactly what I said, create multiple transport rules all with the same condition each in the action remove one of the headers
0
 
LVL 14

Author Closing Comment

by:BigBadWolf_000
ID: 33658415
Thanks for all your help on this issue
0

Featured Post

The curse of the end user strikes again      

You’ve updated all your end user’s email signatures. Hooray! But guess what? They’re playing around with the HTML, adding stupid taglines and ruining the imagery. Find out how you can save your signatures from end users today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

911 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now