[SOLVED] delivering mail to a domain name and not a machine's FQDN

[bubarooni]

OK, I've finally got my Zimbra box up and running. This box will replace a decrepit old Exchange server.

Both boxes sit behind a firewall. To get mail to the Exchange box, I have a static command on the firewall that ties it's inside IP to the IP tied to the MX Record.

As a test, after hours, I swapped the inside IP of the Exchange server with the inside IP of the new Zimbra box on the firewalls static command. The new server sent and received email.

However, the only way it would receive email was if I put the FQDN of the server in the email address. i.e.

myname@mail.mydomain.com
instead of:
myname@mydomain.com

i've got close to 200 users so that is a deal breaker. I can't take it live until this is resolved. I figure I've mucked up something during install but have no idea what it could be. Can I make a change in file, in the Zimbra GUI or do I need to reinstall?

RHEL 5
Zimbra 5.0.5

[mmorse]

Seeing as you just swapped IP's (and you're posted no other DNS dig commands to show the configuration yet) I hate to suggest this because you're not a new forum user, but sometimes it's the simple things - let's take another tact:
Look in your domains list/are your accounts named user@mail.domain.tld? (simple way to check: run 'zmaccts') If so, 2 options:

A) zmprov -l renameDomain mail.domain.tld domain.tld
(that's a lowercase eLL)

B) Leave that one alone and create domain.com, then simply a lot of:
zmprov renameAccount user@mail.domain.tld user@domain.tld
(or use the domain drop down list in the admin console gui in the general tab of each account)

After you do either of these you should check for old mentions of mail.domain.com
zmprov gacf | grep mail.domain.com
zmlocalconfig | grep mail.domain.com
etc (for instance the spam/ham accounts might need a pointer fixed, daily email reports address. etc)

[bubarooni]

'I hate to suggest this'... don't worry about that! i'm a windows/exchange guy and there is no detail to small or simple that i may have overlooked! i've still got noob status on this topic.

well, as luck would have it, i'm still just in the testing phase and haven't migrated my user accts from the exchange server as of yet. i just have one test user.

did i cause this because of the way i configured one of the files related to the named service i set up (named.conf, host, etc..., i'm using split dns because of the firewall)? was it something i answered incorrectly during install?

if so, i think i would be better off uninstalling the whold app, fixing those files and then reinstalling. i'd really like to have it perfect when i take it live and fear that if i try the steps mentioned in your post i'll miss something and only discover the error after everyones migrated over and screaming at me about this or that...

[mmorse]

Don't waste your time, was that a 'yes' the accounts are named user@server.domain.com?

[mmorse]

Though you might post your /etc/hosts anyway, if the accounts are just named user@mail.domain.com you probably did nothing you can't easily correct, at the time of your setup (looking at your older threads) you probably just had the dns A & mx record working fine on mail.domain.com and thus didn't get prompted to change the domain etc.

[bubarooni]

affirmative on the user@server.domain.com thing!

[bubarooni]

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.168.1.23 mail.mydomain.com mail

...sorry to see you are working today, but i'm sure happy for the help!

[mmorse]

zmprov -l renameDomain mail.domain.tld domain.tld

[bubarooni]

so i use my actual domain name in that command, i.e.

zmprov -l renameDomain mail.MyRealDomain.tld MyRealDomain.tld

or run it verbatim like you have it?

[mmorse]

Yes put your domain's name in