Exchange 2007 Single Server FQDN issue with SMTP connector

Logically that makes sense, I used the set-sendconnector command to define my FQDN on my send connector and when I use get-sendconnector -identity "sendconnector" | fl
it shows that my FQDN is mail.domain.com not the local computer name. However, the Received: line in the internet header of emails I send out show that it is coming from localcomputer.domain.local instead of the FQDN of the send connector. I know I can use a transport rule to remove that line in the header but I have my reverse DNS setup for mail.domain.net.

Also, when I telnet into my mail server from the outside it shows up as computername.domain.local. The EHLO/HELO response is generated from the receive connector. See link below for verification.

In Exchange 2007 SP1 you can not change the FQDN in the Default receive connector to anything but computername.domain, domain, or $null.
http://technet.microsoft.com/en-us/library/bb690954.aspx

According to some articles I have seen you can create specific receive connector's for internet traffic, but I don't know how to leave the default connector and create another connector using port 25 for the internet since it won't let you create a second connector that manages the same port.

I know I possible have two issues here, but it is difficult for me to tell where my problems are coming from at this point since I only seem to be generating local FQDN info on sent emails and EHLO/HELO telnet sessions.

If you telnet in to the machine then you will only see the local server name, because that is all that is valid for INBOUND email.
For outbound email it will show what is set on the Send Connector.

However if you read too far back you will see the internal server name in the headers where the message goes through Transport. That is perfectly acceptable and will not cause the email to be flagged as spam. All the remote servers are worried about is how the connection to them appears.

If you have changed the connector, then ensure that you have restarted the Transport Service for the changes to take effect.

Simon.

That is good to know, I was scrambling trying to figure out how I could get an Edge server running. Shouldn't I see my external FQDN somewhere in the header for a sent message though? If not how would I test that outside sources are getting the FQDN of my external address through my Send Connector?

That is the problem the External FQDN is nowhere to be found in the header. I know that the send connector is set to send the external FQDN because when I use the 'get-sendconnector -identity "sendconnector" | fl ' command it lists my external FQDN under the FQDN field. I have restarted the transport service and rebooted my machine and still no dice.

Any suggestions besides using the set-sendconnector to get the fqdn to show up.

Here is a copy of a header wtih the following:

mali.recipient.com being the recipients FQDN
70.167.x.x is my Exchange servers external IP Address
localserver.localdoamin.local is the local address of my server which is where I would expect to see my external FQDN

Microsoft Mail Internet Headers Version 2.0
Received: from psmtp.com ([64.18.2.129]) by mail.recipeintdomain.com with Microsoft SMTPSVC(6.0.3790.1830);
       Fri, 11 Sep 2009 12:27:27 -0700
Received: from source ([70.167.x.x]) (using TLSv1) by exprod7mx171.postini.com ([64.18.6.14]) with SMTP;
      Fri, 11 Sep 2009 19:27:26 GMT
Received: from localserver.localdomain.local ([fe80::3da6:2766:10dc:8d1e]) by
 localserver.localdomain.local ([fe80::3da6:2766:10dc:8d1e%11]) with mapi; Fri,
 11 Sep 2009 12:09:08 -0700
From: recipient Stowe <sender@localdomaintech.net>
To: recipient Stowe <recipient@recipeintdomain.com>
Date: Fri, 11 Sep 2009 12:08:53 -0700
Subject: RE: Test
Thread-Topic: Test
Thread-Index: AQHKMkXFr7lB3Y/tdUWA6FXVK95L05DQKuwwgAGXI/g=
Message-ID: <E0C0961D73A5344B965FA497645E2162069EC45F@localserver.localdomain.local>
References: <E0C0961D73A5344B965FA497645E2162069EC45E@localserver.localdomain.local>,<16F3E409255BF14888B4C1BE0BF5F3B30E1231@recipientServer.recipientdomain.local>
In-Reply-To: <16F3E409255BF14888B4C1BE0BF5F3B30E1231@recipientServer.recipientdomain.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
      boundary="_000_E0C0961D73A5344B965FA497645E2162069EC45Flocalservermatch_"
MIME-Version: 1.0
X-pstn-neptune: 0/0/0.00/0
X-pstn-levels:     (S:99.90000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 3 (1.0000:1.0000) s cv gt3 gt2 gt1 r p m c
X-pstn-addresses: from <sender@localdomaintech.net> [41/2]
Return-Path: sender@localdomaintech.net
X-OriginalArrivalTime: 11 Sep 2009 19:27:27.0108 (UTC) FILETIME=[E57E7440:01CA3315]

--_000_E0C0961D73A5344B965FA497645E2162069EC45Flocalservermatch_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

--_000_E0C0961D73A5344B965FA497645E2162069EC45Flocalservermatch_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


--_000_E0C0961D73A5344B965FA497645E2162069EC45Flocalservermatch_--

What is between Exchange and the internet?

This line is correct and to be expected:

Received: from localserver.localdomain.local ([fe80::3da6:2766:10dc:8d1e]) by
 localserver.localdomain.local ([fe80::3da6:2766:10dc:8d1e%11]) with mapi; Fri,
 11 Sep 2009 12:09:08 -0700

Are you a Postini customer?
This is the line where the FQDN should show.

Received: from source ([70.167.x.x]) (using TLSv1) by exprod7mx171.postini.com ([64.18.6.14]) with SMTP;
      Fri, 11 Sep 2009 19:27:26 GMT

Otherwise delete the Send Connector and create it fresh.

Simon.