[SOLVED] Helo command rejected: need fully-qualified hostname

[fabwhack]

Hi all

New Zimbra install; receiving mail works fine, as does sending to most places. However, some recipient hosts are bouncing our mail with:

Helo command rejected: need fully-qualified hostname

There's no split DNS configured; I've got the following in /etc/hosts (Ubuntu):

127.0.0.1 localhost
192.168.1.220 zimbra.company.com zimbra

"hostname" returns zimbra.company.com too. Where can I set the FQHN for Zimbra to use?

[phoenix]

Originally Posted by fabwhack

New Zimbra install; receiving mail works fine, as does sending to most places. However, some recipient hosts are bouncing our mail with:

Helo command rejected: need fully-qualified hostname

There's no split DNS configured;

You need a Split DNS for Zimbra to work correctly.

Originally Posted by fabwhack

I've got the following in /etc/hosts (Ubuntu):

127.0.0.1 localhost
192.168.1.220 zimbra.company.com zimbra

The hosts file is incorrect.

Go to the Zimbra :: Wiki and search for the word 'ubuntu' and follow the set-up instructions in there for the split dns & hosts file.

You should also update your forum profile with the output of the following command (do not post it in this thread):

zmcontrol -v

[fabwhack]

Profile updated, thanks

I've set up Split DNS according to the instructions, and all seems to be working fine. However, sending mail to certain hosts is still bounced: what do I need to do next? The server is still announcing itself as "zimbra", rather than "zimbra.company.com".

[phoenix]

Originally Posted by fabwhack

I've set up Split DNS according to the instructions, and all seems to be working fine.

Did you also update your hosts file to correct the problem with the format of the 127.0.0.1 line?

Originally Posted by fabwhack

However, sending mail to certain hosts is still bounced: what do I need to do next? The server is still announcing itself as "zimbra", rather than "zimbra.company.com".

That doesn't really make sense as it should have got the FQDN from the hosts file for the server name, it should announce itself as "zimbra.company.com" - did you make any other changes during the initial install other than the change for the domain name and create the admin password?

Telnet to your server on port 25, what does it actually show you as the greeting? What are the actual errors that you are seeing in the log files (post some of the lines)?

[fabwhack]

Hosts now shows:

127.0.0.1 localhost.localdomain localhost
192.168.1.220 zimbra.company.com zimbra

I didn't make any other changes during install that I can remember - we have our own internal DNS server that I'd configured with A records, MX etc, which I'm sure is why the installer didn't complain about DNS.

If I telnet to port 25, I get:

220 zimbra ESMTP Postfix

Zimbra.log shows this when sending a mail to a problem recipient:

Jun 27 17:18:40 zimbra postfix/smtp[25712]: 72FB711F61F7: to=<problem@problem.com>, relay=127.0.0.1[127.0.0.1]:10024
, delay=0.77, delays=0.46/0/0/0.3, dsn=2.0.0, status=sent (250 2.0.0 Ok, id=19943-05, from MTA([127.0.0.1]:10025): 250 2.0.0 O
k: queued as 2AF3111F61FA)
Jun 27 17:18:40 zimbra postfix/qmgr[21287]: 72FB711F61F7: removed
Jun 27 17:18:40 zimbra postfix/smtp[25716]: 2AF3111F61FA: to=<problem@problem.com>, relay=mx-cluster-a2.one.com[195.
47.247.193]:25, delay=0.34, delays=0.01/0/0.33/0, dsn=5.5.2, status=bounced (host mx-cluster-a2.one.com[195.47.247.193] refuse
d to talk to me: 504 5.5.2 <zimbra>: Helo command rejected: need fully-qualified hostname)

[fabwhack]

Oops, meant to add (dunno if it's relevant): postconf |grep myhostname shows:

myhostname = zimbra

[phoenix]

Originally Posted by fabwhack

Oops, meant to add (dunno if it's relevant): postconf |grep myhostname shows:

Erm, yes that's most likely what's causing your problem. Did you change it? Change it back to the default FQDN of your sever and the problem should go away. The hosts file is also now correct.

[fabwhack]

The thing is, I can't change it If it try

postconf -e myhostname=zimbra.company.com

... it doesn't "stick" when I restart Zimbra. As soon as Zimbra starts up, it's reverted back to "myhostname=zimbra". How can I stop Zimbra overwriting the setting, or where do I tell Zimbra about the new FQDN?

[phoenix]

Run the following command and see if they all show your old hostname 'zimbra':

zmprov gacf | grep oldhostname
zmprov gs `zmhostname` | grep oldhostname
zmlocalconfig | grep oldhostname

If they do then follow these instructions to change the server name to the one you want. Make sure that you stop mail coming into the system and that you also take a backup before you make the change to the host name.

[fabwhack]

Hooray! That seems to have done the trick. I'd seen reference to the zmsetservername command, but I thought it was only for setting the hostname rather than the complete FQDN. Telnet to 25 shows zimbra.company.com and mail now goes to problem domains OK. There may be other latent problems I don't about yet, but so far so good!

Thanks *very* much for your help!