Uh oh...
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Uh oh...
Can you post your /var/mail/zimbra.log and /opt/zimbra/log/zimbra.log when you try your test?
Uh oh...
Ok, after a reinstall it sends it to foo.com with no errors, but it never reaches its destination. It's also on a lan named foo.com. maybe that's the problem? Although there is nothing like that in my hosts file so I'm assuming I've done something wrong somewhere. My paste below shows /opt/zimbra/log/zimbra.log is empty. and my /etc/hosts file is ok. I can send to all other domains; my gmail account, my hotmail account, etc. but not foo.com. Any other ideas? because the users have to be able to email one another on foo.com. Would the relay host have anything to do with it? I'm using one.
[root@zimbra log]# ls
amavisd.pid clamd.log freshclam.log myslow.log tomcat.pid zmmtaconfig.log zmmyinit.log
audit.log clamd.pid freshclam.pid mysqld.log zimbra.log zmmtaconfig.pid
[root@zimbra log]# cat zimbra.log
[root@zimbra log]# cat zimbra.log | more
[root@zimbra log]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
[root@zimbra log]# ls
amavisd.pid clamd.log freshclam.log myslow.log tomcat.pid zmmtaconfig.log zmmyinit.log
audit.log clamd.pid freshclam.pid mysqld.log zimbra.log zmmtaconfig.pid
[root@zimbra log]# cat zimbra.log
[root@zimbra log]# cat zimbra.log | more
[root@zimbra log]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Uh oh...
/etc/hosts is short. You need a line with the real server IP and host.domain then host.
So like:
host.domain host
Did you also check /var/log/zimbra.log?
So like:
host.domain host
Did you also check /var/log/zimbra.log?
Uh oh...
[QUOTE]
Maybe that's the problem then because I used that domain name during the configuration phase of the installation.
in /var/log/zimbra.log I parsed this. It looks like that's what it's complaining about no?
Oct 12 17:38:26 localhost postfix/smtpd[3105]: initializing the server-side TLS engine
Oct 12 17:38:26 localhost postfix/smtpd[3105]: connect from localhost.localdomain[127.0.0.1]
Oct 12 17:38:26 localhost amavis[2378]: (02378-01) AUTH not needed, user='', MTA offers ''
Oct 12 17:38:26 localhost postfix/trivial-rewrite[3101]: warning: do not list domain localhost.localdomain in BOTH mydestination and virtual_mailbox_domains
Oct 12 17:38:27 localhost postfix/smtpd[3105]: 0DAAD8A06AA: client=localhost.localdomain[127.0.0.1]
Oct 12 17:38:27 localhost amavis[2378]: (02378-01) response to RCPT TO for : "250 Ok"
Oct 12 17:38:27 localhost postfix/cleanup[3102]: 0DAAD8A06AA: message-id=
Oct 12 17:38:27 localhost postfix/qmgr[3094]: 0DAAD8A06AA: from=, size=990, nrcpt=1 (queue active)
Oct 12 17:38:27 localhost postfix/smtpd[3105]: disconnect from localhost.localdomain[127.0.0.1]
Oct 12 17:38:27 localhost amavis[2378]: (02378-01) FWD via SMTP: -> , 250 2.6.0 Ok, id=02378-01, from MTA([127.0.0.1]:10025): 250 Ok: queued as 0DAAD8A06AA
Oct 12 17:38:27 localhost postfix/smtp[3106]: warning: My hostname localhost is not a fully qualified name - set myhostname or mydomain in /opt/zimbra/postfix-2.2.3/conf/main.cf
Should I reinstall yet again and actually create a domain? or can I just create it in main.cf? The first time I did I was getting all sorts of hostname errors but that was before I ran 'yum update' which I saw in a different post. Since then it's been working until I can't email foo.com. Shouldn't it be giving me problems emailing all domains and not just this one?
[QUOTE]
Maybe that's the problem then because I used that domain name during the configuration phase of the installation.
in /var/log/zimbra.log I parsed this. It looks like that's what it's complaining about no?
Oct 12 17:38:26 localhost postfix/smtpd[3105]: initializing the server-side TLS engine
Oct 12 17:38:26 localhost postfix/smtpd[3105]: connect from localhost.localdomain[127.0.0.1]
Oct 12 17:38:26 localhost amavis[2378]: (02378-01) AUTH not needed, user='', MTA offers ''
Oct 12 17:38:26 localhost postfix/trivial-rewrite[3101]: warning: do not list domain localhost.localdomain in BOTH mydestination and virtual_mailbox_domains
Oct 12 17:38:27 localhost postfix/smtpd[3105]: 0DAAD8A06AA: client=localhost.localdomain[127.0.0.1]
Oct 12 17:38:27 localhost amavis[2378]: (02378-01) response to RCPT TO for : "250 Ok"
Oct 12 17:38:27 localhost postfix/cleanup[3102]: 0DAAD8A06AA: message-id=
Oct 12 17:38:27 localhost postfix/qmgr[3094]: 0DAAD8A06AA: from=, size=990, nrcpt=1 (queue active)
Oct 12 17:38:27 localhost postfix/smtpd[3105]: disconnect from localhost.localdomain[127.0.0.1]
Oct 12 17:38:27 localhost amavis[2378]: (02378-01) FWD via SMTP: -> , 250 2.6.0 Ok, id=02378-01, from MTA([127.0.0.1]:10025): 250 Ok: queued as 0DAAD8A06AA
Oct 12 17:38:27 localhost postfix/smtp[3106]: warning: My hostname localhost is not a fully qualified name - set myhostname or mydomain in /opt/zimbra/postfix-2.2.3/conf/main.cf
Should I reinstall yet again and actually create a domain? or can I just create it in main.cf? The first time I did I was getting all sorts of hostname errors but that was before I ran 'yum update' which I saw in a different post. Since then it's been working until I can't email foo.com. Shouldn't it be giving me problems emailing all domains and not just this one?
[QUOTE]
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Uh oh...
You should not need to edit main.cf If you do it may break things. You need to have a correct /etc/hosts. I recommend you create a valid /etc/hosts with the server's real IP and domain you want to use. Then install and create that domain at install time.
Uh oh...
Yet another install? Heh. No biggie, I can do it with my eyes closed, just not necessarily correctly Thanks for the help. So far it seems a great product though! I know this is something I've done. If my lan domain here is foo.com should I name it something like mail.foo.com?
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Uh oh...
[quote user="agnOstos"]Yet another install? Heh. No biggie, I can do it with my eyes closed, just not necessarily correctly Thanks for the help. So far it seems a great product though! I know this is something I've done. If my lan domain here is foo.com should I name it something like mail.foo.com?[/QUOTE]
You should make the domain the domain you expect to get mail at. If you expect to send to joe@foo.com the domain should be foo.com and then from everywhere foo.com should resolve to this box.
You should make the domain the domain you expect to get mail at. If you expect to send to joe@foo.com the domain should be foo.com and then from everywhere foo.com should resolve to this box.
Uh oh...
Sorry to take up so much of your time. I thought I knew what I was doing a little bit more than is taking place. Now that I've created it foo.com I get the following, which is the same when I tried it the first install.
Creating db...done
Setting the hostname to foo.com...done
Setting the LDAP host to foo,com...done
Initializing ldap...done
Creating server foo.com...done
Creating domain foo.com...done
Creating admin account admin@foo.com...done
Adding foo.com to zimbraMailHostPool in default COS...done
Initializing mta config...done
Configuring SNMP...done
Setting services on foo.com...done
Setting up SSL...done
Starting servers...Calling GetServiceInfoRequest (foo.com)
RESPONSE: (Zimbra::Mon::serviceInfo)
host
ip
name foo.com
done
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.C
ommunicationException foo.com:389)
Installation complete!
Operations logged to /tmp/install.log.8360
********************************************************
That log doesn't exist by the way.
Creating db...done
Setting the hostname to foo.com...done
Setting the LDAP host to foo,com...done
Initializing ldap...done
Creating server foo.com...done
Creating domain foo.com...done
Creating admin account admin@foo.com...done
Adding foo.com to zimbraMailHostPool in default COS...done
Initializing mta config...done
Configuring SNMP...done
Setting services on foo.com...done
Setting up SSL...done
Starting servers...Calling GetServiceInfoRequest (foo.com)
RESPONSE: (Zimbra::Mon::serviceInfo)
host
ip
name foo.com
done
ERROR: service.FAILURE (system failure: getDirectContext) (cause: javax.naming.C
ommunicationException foo.com:389)
Installation complete!
Operations logged to /tmp/install.log.8360
********************************************************
That log doesn't exist by the way.
-
- Ambassador
- Posts: 4558
- Joined: Fri Sep 12, 2014 9:52 pm
Uh oh...
I see " Setting the LDAP host to foo,com...done" Did you enter a comma rather than a dot for the LDAP host? Can you post you latest /etc/hosts. Want to make sure that is et correctly now.