Exchange Server Forums

Exchange HELO name

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Management >> Exchange HELO name

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Exchange HELO name - 17.Jan.2008 10:01:14 AM

DoogieHowser

Posts: 41
Joined: 3.Nov.2007
Status: offline

What is the proper way of changing the Exchange HELO response name? Ours says "fcexchange01.fcdom01.local" to all servers that send us email. I would like it to reflect our mail server name "mail1.domain.com" or "mail2.domain.com" ... I know how to do this in Exchange 2003 with just one name but when I try the same prinicple Exchange 2007 freaks out and Hub Transport stops working. :(

Thanks
Doogie

Post #: 1

Featured Links*

RE: Exchange HELO name - 17.Jan.2008 10:17:39 AM

Confused2

Posts: 66
Joined: 16.Nov.2007
From: Scotland
Status: offline

Did you change the FQDN on the Receive and Send Connectors within HT Server and Organisation Configuration respectively?

(in reply to DoogieHowser)

Post #: 2

RE: Exchange HELO name - 17.Jan.2008 11:58:27 AM

John Weber

Posts: 584
Joined: 20.Apr.2005
From: Portland, Oregon
Status: offline

That is the place to do it. The properties of your internet receive connector.

There is also this from the chm...

You may want to modify the default SMTP banner for Internet-facing SMTP Receive connectors on an Edge Transport server so that the server name and messaging server software are not disclosed by the SMTP banner.

Modifying the Default SMTP Banner

To use the Exchange Management Shell to modify the default SMTP banner

Run the following command:

Copy Code

Set-ReceiveConnector <ConnectorIdentity> -Banner "<220 RemainingBannerText>"
For example, to modify the SMTP banner on an existing Receive connector that is named "From the Internet" so the SMTP banner displays "220 Contoso Corporation", run the following command:

Copy Code

Set-ReceiveConnector "From the Internet" -Banner "220 Contoso Corporation"

(in reply to DoogieHowser)

Post #: 3

RE: Exchange HELO name - 19.Jan.2008 7:33:11 PM

DoogieHowser

Posts: 41
Joined: 3.Nov.2007
Status: offline

quote:

ORIGINAL: John Weber

That is the place to do it. The properties of your internet receive connector.

There is also this from the chm...

You may want to modify the default SMTP banner for Internet-facing SMTP Receive connectors on an Edge Transport server so that the server name and messaging server software are not disclosed by the SMTP banner.

Modifying the Default SMTP Banner

To use the Exchange Management Shell to modify the default SMTP banner

Run the following command:

Copy Code

Set-ReceiveConnector <ConnectorIdentity> -Banner "<220 RemainingBannerText>"

For example, to modify the SMTP banner on an existing Receive connector that is named "From the Internet" so the SMTP banner displays "220 Contoso Corporation", run the following command:

Copy Code

Set-ReceiveConnector "From the Internet" -Banner "220 Contoso Corporation

Hi Sorry your links are all broke so I haven't got a clue what you are saying. :(

Doogie

(in reply to John Weber)

Post #: 4

RE: Exchange HELO name - 20.Jan.2008 1:19:27 PM

Sembee

Posts: 3503
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

You don't need to use PowerShell to change the entries, just use the GUI.
Most people only need to change the Send Connector, as that is the main one that causes problems.

With regards to the receive connector setting, it depends on how many servers you have. If you only have one then you can turn of the Exchange server authentication option and set your own FQDN. Otherwise the FQDN must either be the FQDN of the server or its netbios name. Exchange 2007 SP1 checks that and will fail if it is not set to that.
What may work, but I haven't tested it, is to remove the Exchange server authentication type from the Default Receive Connector and add it to the client connector. If you remove the Exchange Server authentication type you should be able to change the FQDN without problem. Do remember to restart the Exchange Transport Service after making the change.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to DoogieHowser)

Post #: 5

RE: Exchange HELO name - 20.Jan.2008 6:56:15 PM

DoogieHowser

Posts: 41
Joined: 3.Nov.2007
Status: offline

Yes we have one server and are hosting one domain. I would have preferred to have had the MSCE guy who originally setup everything make the FQDN their public name but for whatever the reason he gave it some useless .local one.

We haven't installed SP1 yet as I have seen people complaining that SP1 doesn't allow Outlook 2003 to do certain things, I think Outlook Anywhere (maybe?), and since this company doesn't want to run Office 2007 even though they have the licenese for it SP1 is staying off Exchange for the time being.

Can you give any links to how-to do this change?

Thanks
Doogie

(in reply to Sembee)

Post #: 6

RE: Exchange HELO name - 20.Jan.2008 7:43:01 PM

Sembee

Posts: 3503
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

Where are you reading these reports about Exchange 2007 SP1 stopping Outlook 2003 from working correctly? It is the first I have heard of anything like that.
I can assure you that it does not. I beta tested Exchange 2007 SP1 as I am an Exchange MVP and there are no problems with that service pack Outlook 2003. My primary workstation continued to run Outlook 2003 with Exchange 2007 SP1 without any issues.
Lots of people seem to have issues with Outlook Anywhere/RPC over HTTPS, but that has been the case since RTM - nothing was changed in that regard with Exchange 2007 SP1.
I also do not consider service packs of any product to be an optional installation. I would strongly suggest that you reconsider your decision not to install Exchange 2007.

There is nothing wrong with using .local for a domain name when a new domain is setup. There are arguments for either. If you are ever bored on a Windows discussion list, ask whether you should use .local or a .com or similar internet type domain. The discussion will go on for days.

As for the change, it simply a matter of finding the receive connector in EMC under Server Config, Hub Transport and looking at the properties. Change it. Apply OK out and restart the Exchange Transport Service. When you come to install Exchange 2007 SP1 you will have to change it back to allow the service pack to install as it is a hard failure on the pre-install check.

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to DoogieHowser)

Post #: 7

RE: Exchange HELO name - 20.Jan.2008 7:54:16 PM

DoogieHowser

Posts: 41
Joined: 3.Nov.2007
Status: offline

I have already attempted to change the recieve connector on Exchange 2007 EMC do the actual internet mail server name; even setup DNS server to make mail.domain.com valid when and if Exchange 2007 checks it and restarted the Exchange Transport server, however a few days later the connector stopped working all together and there was errors in the event viewer pointing that the FQDN in Exchange Transport was invalid. I can't remember the exact error as I attempted this a month or so ago but I know when I changed the FQDN back to the .local and restarted the transport the error went away.

Update:

Okay I attempted this just now and noticed the error message in the logs was stating the fact I didn't have a certificate for the FQDN in question, so went to technet and read some more creating a cert for "C=CA O=First Coverage CN=mail.firstcoverage.com" - then I created a new cert for it and enabled it with the services of SMTP... but oh wait I need POP3 SSL.. damn it!

Can this be re-enabled?

Doogie

< Message edited by DoogieHowser -- 20.Jan.2008 8:31:22 PM >

(in reply to Sembee)

Post #: 8

RE: Exchange HELO name - 20.Jan.2008 8:37:43 PM

Sembee

Posts: 3503
Joined: 17.Jan.2008
From: Somewhere near London, UK
Status: offline

If you don't have a certificate for the FQDN then Exchange will lot it heavily, because Exchange wants to use TLS/SMTP over SSL. However that doesn't actually stop Exchange from working, the errors will be logged.
If you have changed the SSL certificate being used then you can change it using PowerShell. Another option would be to use PowerGui - http://www.powergui.org.

However your best long term solution is to use a SAN/UM certificate that contains both the internal FQDN, the external FQDN and the autodiscover.domain.com URL. These were quite expensive to begin with, but GoDaddy are now doing UM certificates for US$60/year: http//www.certificatesforexchange.com/

Simon.

_____________________________

Simon Butler,
Exchange MVP
Blog: http://www.sembee.co.uk/
Web: http://www.amset.info/
In the UK? Hire me: http://www.amset.co.uk/

(in reply to DoogieHowser)

Post #: 9

RE: Exchange HELO name - 21.Jan.2008 12:15:45 PM