Linux T&T » Zimbra

CLI zmtlsctl to set Zimbra Web Server Mode

WladyX — Wed, 27 Apr 2011 11:27:49 +0000

zmtlsctl [mode]

http – http only, the user would browse to http://zimbra.domain.com
https – https only, the user would browse to https://zimbra.domain.com http:// is denied.
both – A user can go to http:// or https:// and will keep that mode for their entire session.
mixed – If the user goes to http:// it will switch to https:// for the login only, then will revert to http:// for normal session traffic. If they browse to https:// then they will stay https://
redirect – Like mixed if the user goes to http:// it will switch to https:// but they will stay https:// for their entire session.

source

Installing a StartSSL SSL certificate on zimbra

WladyX — Thu, 28 Oct 2010 10:01:46 +0000

1. Download the ca.pem [1] and sub.class1.server.ca.pem [2] to /tmp/

2. Cat the CA certs to form a single CA certificate chain file

 cat ca.pem sub.class1.server.ca.pem > ca_bundle.crt

3. Place server certificate in /tmp/ssl.crt.

4. Place the private key in /opt/zimbra/ssl/zimbra/commercial/commercial.key

5. Deploy the commercial certificate with zmcertmgr as the root user.

 cd /opt/zimbra/bin
 ./zmcertmgr deploycrt comm /tmp/ssl.crt /tmp/ca_bundle.crt

6. Restart the zimbra services

 su zimbra
 zmcontrol stop
 zmcontrol start

source

Zimbra Database errors – table didn’t close properly

WladyX — Tue, 14 Sep 2010 13:13:00 +0000

error:
Database errors found. /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password={password] zimbra.jiveID warning : 1 client is using or hasn't closed the table properly

solution:
su - zimbra mysql use zimbra repair table jiveID;

source

Zimbra: Transport Table for external servers

WladyX — Wed, 10 Mar 2010 09:49:47 +0000

Configuring transport tables to relay emails to a different mail server. In this example I am forwarding all emails for otherdomain.com to smtp.otherdomain.com . You can add as many transport maps as you need. All commands should be run as a user ‘zimbra’. After 5.0.9, postfix_transport_maps has been modified a bit, so we’ll show both ways.

$ zmlocalconfig   |grep -i postfix_transport_maps

This will show you the current transport maps file configuration:

postfix_transport_maps = proxy:ldap:/opt/zimbra/conf/ldap-transport.cf

Create your transport file (owner/group-owner should be zimbra):

vi /opt/zimbra/postfix/conf/transportfile
otherdomain.com     :[smtp.otherdomain.com]

You can also add multiple transport maps, for example:

mydomain.com     :[mail.otherdomain.com]
mydomain.org     :[mail.otherdomain.com]
hisdomain.net    :[mail.otherdomain.com]

In this example all emails for 3 different domains will go to mail.otherdomain.com, so destination will be changed, while user name will remain as in original email address.

Convert the transport file into maptype database file:

$ postmap /opt/zimbra/postfix/conf/transportfile

The file transportfile.db will be created in this directory. Define the new transport file (original, not *.db one) BEFORE the default one. Run:

$ zmlocalconfig -e postfix_transport_maps=hash:/opt/zimbra/postfix/conf/transportfile,proxy:ldap:/opt/zimbra/conf/ldap-transport.cf

Finally, make sure that the relay_domains parameter in main.cf contains all domains handled by the server, whether locally or relayed elsewhere:

$ vi /opt/zimbra/postfix/conf/main.cf
relay_domains = otherdomain.com, mydomain.com, mydomain.org, hisdomain.net, locallyhandleddomain.com, localaliaseddomain.com

Restart Zimbra:

zmcontrol stop
zmcontrol start

This will forward all emails for the example domains and subdomains to host smtp.otherdomain.com while allowing local domains to continue to be delivered locally. However you’ll need to be careful at zimbra upgrades. The modification will be overwritten by the upgrade. If you still not able to set the correct transport tables, contact Zimbra Support.

http://wiki.zimbra.com/index.php?title=Transport_Table_for_external_servers

Zimbra upgrade

WladyX — Fri, 22 Jan 2010 10:26:41 +0000

0. backup transport files if any
1. stop zimbra
1a. check if every process is really stopped. don’t want to see stalled mysql or something – happened to me once
2. tar zimbra installation folder
3. tar /var/lib/rpm !!! (I forget often to do this)
4. START ZIMBRA!!! (else upgrade could fail)
5. upgrade
6. if everything works, delete backups, else untar and try again
7. restore transport files if any, eg:
a. su – zimbra
b. cp /test/transportfile /opt/zimbra/postfix/conf
c. postmap /opt/zimbra/postfix/conf/transportfile

Source

Canonical Address in Zimbra GAL

WladyX — Wed, 09 Dec 2009 12:34:45 +0000

zmprov mcf -zimbraGalLdapAttrMap zimbraMailDeliveryAddress,zimbraMailAlias,mail=email,email2,email3,email4,email5,email6,email7,email8,email9,email10,email11,email12,email13,email14,email15,email16

zmprov mcf +zimbraGalLdapAttrMap zimbraMailCanonicalAddress,mail=email

zmprov fc config

http://chen23.com/docs/zimbra/custom_address_in_gal/