Zimbra with DynDNS and port 2525

[dontpanic]

Hi,

I am trying to install Zimbra under CentOS 5 and I am getting the error :-

Initialising ldap... failed. (29440).

I have included more specifics on the error message below, but first its probably best to describe what I am trying to do, and what I have done so far...

Our company is currently running Lotus Domino 6.5, and mail comes in on port 25. There is an entry in our router that directs traffic on port 25 to our mail server. I need to leave Lotus running to get our mail while I setup Zimbra to replace it.

Since the CentOS server I am trying to setup runs on this same network, I decided to
use DnyDNS to setup a custom domain, and use their mail relay to direct mail traffic to this new server using port 2525. I have put an entry in our firewall/router to send all outside traffic on port 2525 to the CentOS server.

- our company domain, on which the lotus mail server currently runs, is svp.com.au
- the new custom dyndns domain is svpaus.com

I'm not sure how the error I am getting relates to what I am trying to do, so I will just try and include as much information here as possible, so hopefully someone can tell me what is going wrong.

I don't know how to tell Zimbra to listen on port 2525. I have seen the posts which talk about '587' and the bugfix, but my situation is a bit different. Firstly, I want to use ONLY port 2525, not 25 AND 2525. Secondly, in the postings where it says to edit master.cf and look for the line "smtp inet n - n - - smtpd", this line does not exist in my master.cf, the closest thing I can see is

smtp unix - - n - - smtp

Is it possible that this line doesnt exist because the installation has not yet completed? I have included my entire master.cf below if it helps.

-----------------------------------------------------------------
my dyndns entries look like this
------------------------------------------------------------------
svpaus.com A 202.4.77.58
svpaus.com MX 10 mail.svpaus.com
mail.svpaus.com A 202.4.77.58
------------------------------------------------------------------
my /etc/hosts file looks like this
------------------------------------------------------------------
# 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
202.4.77.58 mail.svpaus.com mail
----------------------------------------------------------------------
the IP address of my zimbra server is 172.21.0.37
-------------------------------------------------------------------------------

I also got these messages during the installation :-

DNS ERROR resolving MX for mail.svpaus.com
It is suggested that the domain name have an MX record configured in DNS
Change domain name? [Yes] y
Create Domain: [mail.svpaus.com] svpaus.com
MX: mail.svpaus.com (202.4.77.58)

Interface: 172.21.0.37
Interface: 127.0.0.1
Interface: 192.168.122.1


DNS ERROR - none of the MX records for svpaus.com
resolve to this host
It is suggested that the MX record resolve to this host
Re-Enter domain name? [Yes] n
done.
Checking for port conflicts
Port conflict detected: 25 (zimbra-mta)
Port conflicts detected! - Any key to continue

Thanks for any suggestions...
Will.

---------------------------------------------------------------------------------
the log file contained the following (igore the timestamp) :-

Fri Feb 17 02:59:03 2006 checking isEnabled zimbra-ldap
Fri Feb 17 02:59:03 2006 zimbra-ldap is enabled
Fri Feb 17 02:59:03 2006 Initializing ldap...
Fri Feb 17 02:59:03 2006 *** Running as zimbra user: /opt/zimbra/libexec/zmldapinit
IO::Socket::INET: connect: timeout at /opt/zimbra/libexec/zmldapinit line 160.
Fri Feb 17 03:01:50 2006 failed. (29440)
Fri Feb 17 03:01:50 2006

ERROR

Fri Feb 17 03:01:50 2006

Configuration failed

Fri Feb 17 03:01:50 2006 Please address the error and re-run /opt/zimbra/libexec/zmsetup.pl to
Fri Feb 17 03:01:50 2006 complete the configuration.
Fri Feb 17 03:01:50 2006
Errors have been logged to /tmp/zmsetup.01001900-0000455073920.log

--------------------------------------------------------------------------------------------------------

line 160 is

my $ldap = Net::LDAP->new("$ldap_master_url") or die "$@";

---------------------------------------------------------------------------------------------------------
master.cf
---------------------------------------------------------------------------------------------------------

#submission inet n - n - - smtpd
# -o smtpd_etrn_restrictions=reject
# -o smtpd_client_restrictions=permit_sasl_authenticate d,reject
465 inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
#submission inet n - n - - smtpd
# -o smtpd_etrn_restrictions=reject
# -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes
#628 inet n - n - - qmqpd
pickup fifo n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 300 1 qmgr
#qmgr fifo n - n 300 1 oqmgr
tlsmgr unix - - n 1000? 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounce unix - - n - 0 bounce
defer unix - - n - 0 bounce
trace unix - - n - 0 bounce
verify unix - - n - 1 verify
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
smtp unix - - n - - smtp
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay unix - - n - - smtp
-o fallback_relay=
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - n - - showq
error unix - - n - - error
discard unix - - n - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
anvil unix - - n - 1 anvil
scache unix - - n - 1 scache
#
# ================================================== ==================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent. See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ================================================== ==================
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
#
# The Cyrus deliver program has changed incompatibly, multiple times.
#
old-cyrus unix - n n - - pipe
flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
# Cyrus 2.1.5 (Amos Gouaux)
# Also specify in main.cf: cyrus_destination_recipient_limit=1
cyrus unix - n n - - pipe
user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
#
# See the Postfix UUCP_README file for configuration details.
#
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# Other external delivery methods.
#
ifmail unix - n n - - pipe
flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix - n n - - pipe
flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
#
# AMAVISD-NEW
#
smtp-amavis unix - - n - 10 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=20
127.0.0.1:10025 inet n - n - - smtpd
-o content_filter=
-o local_recipient_maps=
-o virtual_mailbox_maps=
-o virtual_alias_maps=
-o relay_recipient_maps=
-o smtpd_restriction_classes=
-o smtpd_delay_reject=no
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,rej ect
-o mynetworks_style=host
-o mynetworks=127.0.0.0/8
-o strict_rfc821_envelopes=yes
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0
-o receive_override_options=no_header_body_checks,no_ unknown_recipient_checks,no_address_mappings

[phoenix]

The set-up you require would be a Split Domain, check out the wiki article and see if it describes what you need.

[dontpanic]

Thanks Bill,

I am not sure if the split-domain is the same as what I am trying to achieve; this situation seems to describe 2 mail servers on the same domain. I don't have access to the configuration for mail forwarding from our existing host/relay (long story, don't ask) so I wouldn't know how to direct certain user's mail to the correct server - unless there is a way to do this from the router or within our network.

I really need to completely configure a 'parallel' mail system, and when it all works I will migrate the whole thing over, which is why I thought I could run a different domain inside our current network... is this actually possible?

Also, there is still the problem that my master.cf does not contain the smtp entries as described in the article.

Any other suggestions?

Thanks,
Will.

[dontpanic]

Hi,

I re-read the split-domain article, and it seems as though it would be an easier way to do things, however I have a couple of questions...

- this is my first Zimbra installation, and my first linux installation, so it will take some time. I cannot take the existing Domino server offline until the new system is fully functional

- our existing mail server is svpnmai1.svp.com.au. If I install another mail server, say zimbra.svp.com.au also on port 25, and create a user "zimbrauser" in the new zimbra system, how do I get the new zimbra server to ONLY pickup mail for zimbrauser@svp.com.au and not interfere with any other users?

- if instead of port 25, I setup the zimbra server on port 2525, how do I then send mail to zimbrauser@svp.com.au on port 2525 instead of 25, so that the router directs mail correctly? is there some way to do this using my dyndns account, even though it is setup for the svpaus.com domain?

Thanks,
will.

[phoenix]

For the split domain to work you need to forward mail for unknown users to the zimbra server, you then create those users on the Zimbra server. Obviously the new zimbra users in your case will just be test accounts. The new zimbra users should then be able to send/receive email. I'm assuming that Domino can be configured to forward all mail for unknown users to the zimbra server? I don't really know that much about Domino I'm afraid.

[dontpanic]

I asked a local consultant, a Domino expert, this question and he said that he does not know of any way to do this, so I am back to my original questions. I think I can sort out the MX forwarding problem (if there is one) and get my router to forward traffic on port 2525 to my mail server. But I still have the two Zimbra setup issues as described in my first post -

- ldap initialisation problem
- how to setup my zimbra server to listen on port 2525, and not listen on port 25.

Thanks again,
Will.