<div>
Yes. &nbsp;Just open up Exchange System Manager and expand Servers then expand yourservername and then protocols and smtp. &nbsp;Right-click the &quot;Default SMTP Virtual Server&quot; and click on Properties. &nbsp;Now click on the &quot;delivery&quot; tab and then click the &quot;Advanced&quot; button at the bottom.<br />
<br />
You will now see the &quot;Full Qualified Domain Name&quot; section. &nbsp;This is what appears in the HELO statement. &nbsp;Simply edit it to your preferred FQDN
</div>


Yes.  Just open up Exchange System Manager and expand Servers then expand yourservername and then protocols and smtp.  Right-click the "Default SMTP Virtual Server" and click on Properties.  Now click on the "delivery" tab and then click the "Advanced" button at the bottom.

You will now see the "Full Qualified Domain Name" section.  This is what appears in the HELO statement.  Simply edit it to your preferred FQDN

<div>
Wayne<br />
beat you to it lol
</div>


<div>
Thank you Gearge and Wayne. Thats what I needed I edit that, but just wondered if there was another step to it. 
</div>


Thank you Gearge and Wayne. Thats what I needed I edit that, but just wondered if there was another step to it.

<div>
if you are forwarding smtp from the internet through a firewal to your exchange server you couls ask your isp to register mail.domain.com against your external IP. just be carfull about email relaying, everyone scans for smtp ports.
</div>


if you are forwarding smtp from the internet through a firewal to your exchange server you couls ask your isp to register mail.domain.com against your external IP. just be carfull about email relaying, everyone scans for smtp ports.

<div>
george - I used too many words!
</div>


<div>
<div class="content wysiwyg-content">
I know that Exchange, by design, does not send the fully qualified doamin name in the HELO command. Is there a way to force it to send the FQDN??<br />
<br />
I am running Exchange 2003 on Windows Server 2003 SBS.<br />
<br />
Thanks
</div>
</div>


I know that Exchange, by design, does not send the fully qualified doamin name in the HELO command. Is there a way to force it to send the FQDN??

I am running Exchange 2003 on Windows Server 2003 SBS.

Thanks

How to force Exchange to send FQDN in HELO command

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).