Solved

Exchange 2007 changing HELO message

Posted on 2011-02-11
5
769 Views
Last Modified: 2012-05-11
let me start by saying I am not familair with Exchange 2007.

A client of mine is running SBS 2008 and Exchange 2007.  Under Server Cnofig Hb Transport - I see 2 Receive connectors that allow you to change the HELO message to a FQDN.  Both are cofigured for the local FQDN.  One is labeled Client and the other Default.  I am able to change rthe Client connector to something like mail.companyname.com but not the Default.  If I were to restart Exchange, would this produce the desired effect of changing the HELO message?
0
Comment
Question by:GDavis193
  • 3
  • 2
5 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34877263
You won't be able to change this without removing the Exchange Servers permission group.

It's really not necessary to change this and I would recommend you don't.
0
 

Author Comment

by:GDavis193
ID: 34877387
Well I was trying to figure out why a users email was kicked back (554).  We use MX Logic and the message was sent to the recipients mail server but it was kicked back for some reason.  SPF records are good as well as PTR records.  No blacklists.  No attachements.  Had another user from same domain test and it's also rejected.  MX Logic support couldnt provide an answer - the only thing I saw that didn't match up was the HELO message.

Perhaps I'm going down the wrong road?
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 34877399
So you send via MX Logic or just receive?

Check your send connector FQDN, does that match your rDNs(PTR)?
0
 

Author Comment

by:GDavis193
ID: 34879399
No.  I think that's what might be part of the problem.  
Not knowing Exchange2k7 I poked around and saw 1 send connector under Org Config_> Hub Transport but the FQDN box is BLANK.

There are 2 receive connectors under Server Config > Hub Transport labeled Default and Client.  Defualt can't be changed as is set to iinernal FQDN (servername.domainname.local).  The client CAN be changed but is currently set to internal FQDN.

We both send/receive through MX Logic.
0
 
LVL 74

Accepted Solution

by:
Glen Knight earned 500 total points
ID: 34879414
You won't be able to change the one that starts with default, for the same reason I mentioned above.

If you send and receive via MX Logix then the problem lies with their configuration not yours.
0

Featured Post

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.

Question has a verified solution.

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

Suggested Solutions

Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
how to add IIS SMTP to handle application/Scanner relays into office 365.

777 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