[SOLVED] CentOS 5/Zimbra 5 MTA won't start

[glgcag]

I'm installing Zimbra for the first time, as well as I'm a total Linux noob too! (I'm putting a test server together for possible future migration COMPLETELY out of the Microsoft world- I'm currently MS everything, including Exchange.)

I've tried Ubuntu server, Debian and openSUSE, but I settled on CentOS 5 for the Zimbra install.

Though the actual install completed, when I go into the admin console for Zimbra, the MTA isn't started. Here are the pertinent errors from the install log:

No results returned for A lookup of mail01.example.com
Checked nameservers:
192.168.168.3
24.205.1.14
66.215.64.14


DNS ERROR resolving mail01.example.com
It is suggested that the hostname be resolveable via DNS
checking isEnabled zimbra-mta
zimbra-mta is enabled

Interface: 192.168.168.3
Interface: 127.0.0.1


DNS ERROR - none of the MX records for mail01.example.com
resolve to this host

Additionally, there was a port conflict regarding MTA on port 25 in the install as well.

Any help for how to fix this is appreciated!

[th350urc3]

assuming, you've created the appropriate A and MX records, please make sure you have an entry for mail01.example.com in your hosts file

sample hosts

127.0.0.1
xx.xx.xx.xx mail01.example.com

xx = whatever your the local ip of zimbra box is.

hope this helps.

[janderson]

For the port conflict, sendmail is installed in CentOS by default. Stop it by doing

service sendmail stop
chkconfig --del sendmail

[phoenix]

Originally Posted by th350urc3

assuming, you've created the appropriate A and MX records, please make sure you have an entry for mail01.example.com in your hosts file

sample hosts

127.0.0.1
xx.xx.xx.xx mail01.example.com

xx = whatever your the local ip of zimbra box is.

hope this helps.

The /etc/hosts file would be incorrect, it should read as follows:

127.0.0.1             localhost.localdomain localhost
xx.xx.xx.xx           mail01.example.com mail01

[phoenix]

Originally Posted by glgcag

DNS ERROR - none of the MX records for mail01.example.com resolve to this host

In addition to the changes to your hosts file detailed in the post above you xan check your DNS with the following (run on your zimbra server):

host `hostname`  <-- type that command as-is with backticks not single quotes
dig yourdomain.com mx
dig yourdomain.com any

and post the output.

There's also a 'how-to' for installing on CentOS5 if you search through the forums.

[santunez]

Hello.

I have the problem. The solutions is:

comment in your hosts file the line

127..0.0.0 localhost.localdomain localhost

and add the IP of server

#127..0.0.0
xxx.xxx.xxx

Bye

[adavis]

Uninstall Sendmail, it is installed by default. This will fix your problem. I had the same issue you did. Make sure your MX record is set up right as well.

[glgcag]

Wow, awesome info, thanks!

janderson & adavis, I stopped sendmail and MTA came up fine, I read that I should make sure sendmail is stopped but I think with all the hosts/DNS problems I forgot!

phoenix/bill & th350ourc3, thanks for the hosts help! I fixed it and all went well!

Another question about hosts though- I went into the zimbra admin console to create my domain which is not mail01.example.com, but example.com, which I have my external MX records at GoDaddy.com pointing to. I'm able to send email out with this domain, but no email is getting through. Are there additional steps when adding a domain (such as DNS and hosts file configuration) that I should be taking?

Also, can I delete the default created domain of mail01.example.com once I've created my actual domain?

Again, thanks for all the help!

[mmorse]

su - zimbra
zmprov gacf

as well as:

zmlocalconfig | grep admin

(To see what references of admin@mail01.domain.com you'd need to correct.)

See here for changing the address of the daily report : [SOLVED] Changing the email address for the Daily Email

Don't know the status of the bug, but on version upgrade it used to get reset to admin@server.domain.com...
So to make it easier on yourself you could just leave that mail01.domain, then make admin@mail01.domain.com fwd > admin@domain.com

Notes: You can also rename the spam/ham to something shorter or without random numbers on the end if you want (be sure to change the actual account name as well not just
zimbraSpamIsSpamAccount/zimbraSpamIsSpamAccount values).
You'd have to move the global wiki account as well before deleting the mail01.domain.com

[mmorse]

Realized your new, zmprov commands are like:

zmprov mcf zimbraValueUWantChanged desiredValue

mcf = ModifyConfig

These are good references:
Zmprov (Provisioning - Zimbra :: Wiki)
Zmprov Examples - Zimbra :: Wiki
Bulk Provisioning - Zimbra :: Wiki

zmlocalconfig is per serer, much like zmprov getServer mail01.domain.com (set with modifyServer or ms)

If you execute 'zmlocalconfig' without argument, it shows the present configuration parameters and values.
(your looking for references of admin@mail01.domain.com)
Then simply:

zmlocalconfig -e smtp_destination=admin@domain.com

also relevant to that is:
smtp_source=admin@domain.com (the from)
smtp_notify=yes
zmlocalconfig zimbra_mtareport_max_recipients=50
zimbra_mtareport_max_senders=50

If this is NE (though I imagine it's FOSS because you say you've tried Debian at one point) on 4.5.6+ the backup tab in the admin console allows for setting these zmprov attributes:
zimbraBackupReportEmailRecipients
zimbraBackupReportEmailSubjectPrefix
zimbraBackupReportEmailSender

In short, anything you set on the server level will override global settings. If you don't modify the server values at all it will just use global of course