Thank you for your answer,
I already installed a working multi-server topology.
I will read again the doc...
Search found 16 matches
- Mon Feb 04, 2019 3:13 pm
- Forum: Installation and Upgrade
- Topic: Install Webmail on MTA
- Replies: 2
- Views: 1146
- Mon Feb 04, 2019 2:25 pm
- Forum: Installation and Upgrade
- Topic: Install Webmail on MTA
- Replies: 2
- Views: 1146
Install Webmail on MTA
Hello all, I've a question, how can I put the WebMail on my mta ? I explain: I'm on multi-server topology. I have an LDAP, MTA and MDA servers. On first time i add installed LDAP server with: - zimbra-ldap Second time I had installed MTA with: - zimbra MTA - zimbra store - zimbra apache - zimbra spe...
- Mon Jan 14, 2019 2:49 pm
- Forum: Installation and Upgrade
- Topic: Error Please fix your /etc/hosts file
- Replies: 1
- Views: 5159
Re: Error Please fix your /etc/hosts file
It's good i forgot change the hostname of the VM.
And now it's working.
And now it's working.
- Mon Jan 14, 2019 2:40 pm
- Forum: Installation and Upgrade
- Topic: Error Please fix your /etc/hosts file
- Replies: 1
- Views: 5159
Error Please fix your /etc/hosts file
Hello everybody, I've a problem with my installation of Zimbra multiserver. I had configure my hosts file like: 192.168.1.254 ns.domain.net ns 192.168.1.252 ldap.domain.net ldap 192.168.1.251 mda.domain.net mda 192.168.1.250 mta.domain.net mta And my resolv.conf like: search domain.net nameserver 19...
- Wed Oct 31, 2018 10:53 am
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
I found the solution !
I had install iptables package on my LDAP server and I had enter this line:
And now I can resolv my ldap password on my MTA.
Tank you all for your help !
I had install iptables package on my LDAP server and I had enter this line:
Code: Select all
-A INPUT -p tcp -m state --state NEW -m tcp --dport 389 -j ACCEPT
Tank you all for your help !
- Mon Oct 29, 2018 4:02 pm
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
My DNS is working, I had disable LinuxSE, iptables.
The problem is why MTA can't conntect to ldap with telnet ?
The 389 port of LDAP is open and the MTA didn't see it.
The redurection is perfectly fonctionnal.
The problem is why MTA can't conntect to ldap with telnet ?
The 389 port of LDAP is open and the MTA didn't see it.
The redurection is perfectly fonctionnal.
- Mon Oct 29, 2018 3:10 pm
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
It was a bug, I made mistake when I had type my ldap domain so my MTA is working I have this:
ldap.domain.loc has adress 192.168.1.252
ldap.domain.loc has adress 192.168.1.252
- Mon Oct 29, 2018 3:01 pm
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
The contact of MTA to LDAP is a telnet connexion failed. ping 192.168.1.252: YES can you ping ldap.domain.loc YES telnet 192.168.1.252 389 NO telnet ldap.domain.loc 389 NO output of 'host ldap.domain.loc' not found: 3(NXDOMAIN) but host 192.168.1.252 = ldap.domain.loc has address 192.168.1.252 and 2...
- Mon Oct 29, 2018 2:10 pm
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
So, my MTA can't contact the LDAP server, yet LDAP listen the 389 port on my first network card (192.168.1.252) that's I want. When I contact the LDAP server from MTA, I have this message: ldap.domain.loc: Unknown host So I had put nmap ldap and the 389 port is not appears Nmap scan report for ldap ...
- Mon Oct 29, 2018 11:37 am
- Forum: Administrators
- Topic: LDAP Admin Password: Not verified
- Replies: 23
- Views: 10653
Re: LDAP Admin Password: Not verified
The LDAP port 389 is open but I can't connect from MTA server. Servers have no replication. My files: LDAP server: /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.1.252 ldap.domain.loc ldap 192.168.1.251 mda.domain.loc mda 192.168.1.250 mta.domain.loc mta 192.168.1.254 ns.domain.loc ns ...