Zimbra - Revision history

Sstrutt: Updated to use Depreciated template

2012-05-01T15:30:30Z

Updated to use Depreciated template

← Older revision		Revision as of 15:30, 1 May 2012
Line 1:		Line 1:
	~~__NOINDEX__~~		{{Depreciated\|category=Zimbra}}

	~~'''This page is now depreciated, as it was becoming too large, and will no loner be updated. All existing and new content can be found via the [[:Category:Zimbra~~\|Zimbra ~~Category page]]'''~~

	== Installation ==		== Installation ==

Sstrutt: Removed category

2012-04-04T09:07:48Z

Removed category

← Older revision		Revision as of 09:07, 4 April 2012
Line 414:		Line 414:
	* '''[http://wiki.zimbra.com/index.php?title=Working_with_Zimlets Zimlets]'''		* '''[http://wiki.zimbra.com/index.php?title=Working_with_Zimlets Zimlets]'''
	* '''[http://wiki.zimbra.com/wiki/Zimbra_Desktop_FAQ#How_to_install_spell_checker_dictionaries.3F Zimbra Client Dictionary Install]'''		* '''[http://wiki.zimbra.com/wiki/Zimbra_Desktop_FAQ#How_to_install_spell_checker_dictionaries.3F Zimbra Client Dictionary Install]'''

	~~[[Category:Zimbra]]~~

Sstrutt: Added NoIndex tag and depreciated note

2012-02-14T13:57:56Z

Added NoIndex tag and depreciated note

← Older revision		Revision as of 13:57, 14 February 2012
Line 1:		Line 1:
			__NOINDEX__

			'''This page is now depreciated, as it was becoming too large, and will no loner be updated. All existing and new content can be found via the [[:Category:Zimbra\|Zimbra Category page]]'''

	== Installation ==		== Installation ==
	The notes below are for the situation of installing a Zimbra server in a split-DNS scenario. Split DNS is required where you have a Zimbra server on an internal (private address range) network. Zimbra needs to be able to resolve its own MX DNS record, therefore if your server is known publicly by one IP address, but in fact has an internal address (and the public IP is NAT'ed to the internal IP) you'll need to use split DNS. The method below uses a DNS server installed locally on the Zimbra server, however you can also use a DNS server on your local network, if you have one available.		The notes below are for the situation of installing a Zimbra server in a split-DNS scenario. Split DNS is required where you have a Zimbra server on an internal (private address range) network. Zimbra needs to be able to resolve its own MX DNS record, therefore if your server is known publicly by one IP address, but in fact has an internal address (and the public IP is NAT'ed to the internal IP) you'll need to use split DNS. The method below uses a DNS server installed locally on the Zimbra server, however you can also use a DNS server on your local network, if you have one available.

Sstrutt: /* Installation */ Added some additional notes

2012-01-30T09:05:24Z

Installation: Added some additional notes

← Older revision		Revision as of 09:05, 30 January 2012
Line 1:		Line 1:
	== Installation ==		== Installation ==
			The notes below are for the situation of installing a Zimbra server in a split-DNS scenario. Split DNS is required where you have a Zimbra server on an internal (private address range) network. Zimbra needs to be able to resolve its own MX DNS record, therefore if your server is known publicly by one IP address, but in fact has an internal address (and the public IP is NAT'ed to the internal IP) you'll need to use split DNS. The method below uses a DNS server installed locally on the Zimbra server, however you can also use a DNS server on your local network, if you have one available.

	=== DNS Records ===		=== DNS Records ===
	Firstly, you need to own a public domain name, then get your ISP to create two DNS records...		Firstly, you need to own a public domain name, then get your ISP to create two DNS records...
Line 7:		Line 9:
	# '''A record''' - Standard DNS record		# '''A record''' - Standard DNS record
	#* EG <code> mail.sandfordit.com [A] -> 158.25.34.124 </code>		#* EG <code> mail.sandfordit.com [A] -> 158.25.34.124 </code>
	#* <code> 158.25.34.124 </code> is the static IP address assigned by your ISP. You'll need to set-up a NAT on your router (often oddly called a virtual server in domestic routers) to map incoming mail on TCP 25 to your email server's actual address (EG <code> 158.25.34.124:25 -> 192.168.1.150:25 </code>.		#* <code> 158.25.34.124 </code> is the static IP address assigned by your ISP. You'll need to set-up a NAT on your router (often oddly called a virtual server in domestic routers) to map incoming mail on TCP 25 to your email server's actual address (EG <code> 158.25.34.124:25 -> 192.168.1.150:25 </code>).

	Note, instead of an A record you can use a CNAME record if you prefer, though obviously the CNAME record will still need to point to a valid A record. Using a CNAME might be preferable, if for example you've multiple services running from a single public IP, that you might want to split out in the future to run on separate IP's, at which point you can replace the CNAME records with A records.		Note, instead of an A record you can use a CNAME record if you prefer, though obviously the CNAME record will still need to point to a valid A record. Using a CNAME might be preferable, if for example you've multiple services running from a single public IP, that you might want to split out in the future to run on separate IP's, at which point you can replace the CNAME records with A records.

Sstrutt: Added "Account Export Incomplete"

2011-11-10T13:54:22Z

Added "Account Export Incomplete"

@@ Line 383: / Line 383: @@
 and so update to say 20 MB, use...
 * <code> zmprov modifyConfig zimbraMailContentMaxSize 20480000 </code>
 == Documentation Links ==
 * '''[http://wiki.zimbra.com/index.php?title=Working_with_Zimlets Zimlets]'''
 * '''[http://wiki.zimbra.com/wiki/Zimbra_Desktop_FAQ#How_to_install_spell_checker_dictionaries.3F Zimbra Client Dictionary Install]'''

Sstrutt: /* Backup */ Added link to modded zmbak script

2011-11-08T07:37:26Z

Backup: Added link to modded zmbak script

← Older revision		Revision as of 07:37, 8 November 2011
Line 195:		Line 195:
	# Exit Zimbra user and create copy of directory		# Exit Zimbra user and create copy of directory
	#* EG <code> cp -rp /opt/zimbra /home/simons/zimbra_backup_100301 </code>		#* EG <code> cp -rp /opt/zimbra /home/simons/zimbra_backup_100301 </code>
			# Once completed, go back to zimbra user and start
			#* <code> su - zimbra </code>
			#* <code> zmcontrol start </code>

	<br>'''More elaborate scripted version'''<br>		<br>'''More elaborate scripted version'''<br>
Line 211:		Line 214:

	To restore, see http://www.zimbra.com/forums/administrators/15275-solved-yet-another-backup-script-community-version-24.html		To restore, see http://www.zimbra.com/forums/administrators/15275-solved-yet-another-backup-script-community-version-24.html

			I've modified the above script, to suit my own purposes. I've added an FTP option so that completed backup's are copied off to a remote FTP server (the copy isn't encrypted so should only be used within a private/secure network - [[Zimbra FOSS Full Backup]]

	=== Upgrade ===		=== Upgrade ===

Sstrutt: /* Procedures */ Added "Change Hostname"

2011-11-07T16:04:48Z

Procedures: Added "Change Hostname"

@@ Line 289: / Line 289: @@
 # If services don't start properly, force java to accept your certificate
 #* EG <code> /opt/zimbra/java/bin/keytool -import -alias new -keystore /opt/zimbra/java/jre/lib/security/cacerts -storepass changeit -file /sslbk/zimbra/commercial/commercial.crt </code>
 === Install Zimlet ===

Sstrutt: /* Procedures */ Added Message Sizes

2011-11-01T17:06:52Z

Procedures: Added Message Sizes

← Older revision		Revision as of 17:06, 1 November 2011
Line 324:		Line 324:
	** EG <code> zmmailbox -z -m simon gfrl </code>		** EG <code> zmmailbox -z -m simon gfrl </code>

	=== Message ~~Purging~~ ===		=== Message Sizes ===
			To see the current max IMAP request size...
			* <code> zmlocalconfig \| grep -i imap_max_request_size </code>
			To increase the size, to say 20MB...
			* <code> zmlocalconfig -e imap_max_request_size=20480 </code>

	~~Check per-user~~ settings		Its also worth being aware of the following settings, which are altered through the admin console...
	~~zmprov ga simon@sandfordit~~.~~com~~ \| ~~grep Lifetime~~		* In Global Settings \| General Information...
			** Maximum size of an uploaded file for Briefcase, Email messages, Calendar appointments and Tasks (KB)
			*** <code> zimbraFileUploadMaxSize </code>
			* In Global Settings \| MTA...
			** Maximum message size (KB)
			*** <code> zimbraMtaMaxMessageSize </code>

			And there's also an additional setting, <code> zimbraMailContentMaxSize</code>, which also appears to affect the maximum size of attachments. To see what you're set to currently use...
	~~more~~ /~~opt/zimbra~~/~~log/mailbox.log \| grep MailboxPurge~~		* <code> zmprov getConfig zimbraMailContentMaxSize </code>
			and so update to say 20 MB, use...
			* <code> zmprov modifyConfig zimbraMailContentMaxSize 20480000 </code>

	== Documentation Links ==		== Documentation Links ==
	* '''[http://wiki.zimbra.com/index.php?title=Working_with_Zimlets Zimlets]'''		* '''[http://wiki.zimbra.com/index.php?title=Working_with_Zimlets Zimlets]'''
	* '''[http://wiki.zimbra.com/wiki/Zimbra_Desktop_FAQ#How_to_install_spell_checker_dictionaries.3F Zimbra Client Dictionary Install]'''		* '''[http://wiki.zimbra.com/wiki/Zimbra_Desktop_FAQ#How_to_install_spell_checker_dictionaries.3F Zimbra Client Dictionary Install]'''

Sstrutt: /* Procedures */ Added "Migrate Commercial Certificate To New Server"

2011-10-14T21:02:43Z

Procedures: Added "Migrate Commercial Certificate To New Server"

@@ Line 262: / Line 262: @@
 # Upload CSR to certificate authority
 # Install received keys via GUI and restart server
 === Install Zimlet ===

Sstrutt: /* Zimbra Appliance */ Added license bit

2011-08-11T10:25:06Z

Zimbra Appliance: Added license bit

@@ Line 149: / Line 149: @@
 * [[#High_CPU_Workaround|High CPU Workaround]] - Quite why you have to tweak a VMware provided appliance to make it run efficiently on VMware is mind boggling
 * [[Ubuntu#Setup_.28v10.29|SNMP Install]]
 == Maintenance ==