Differences between version 3 and predecessor to the previous major change of ZimbraNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Wednesday, February 22, 2006 9:58:29 am | by GreigMcGill | Revert |
| Older page: | version 1 | Last edited on Wednesday, February 22, 2006 9:36:57 am | by GreigMcGill | Revert |
@@ -7,5 +7,31 @@
!!Configuring [Zimbra] With An Existing MTA For Testing
Say you'd like to try out this flashy new technology, and deploy Zimbra as part of an existing domain. This is a lot harder than it could be. Here is what I did.
-*saving at
this point so noone gets zealous and overwrites!
*
+* Mail domain (external MXs serve
this): example.com
+
* Internal domain: internal.example.com
+* Primary MTA (runs exim, but that doesn't matter): mta.internal.example.com
+* [Zimbra] Server: zimbra.internal.example.com
+
+# Create example.com as your primary domain during setup of [Zimbra].
+# Create your "guineapig user" accounts on the [Zimbra] server which have the same email addresses as their existing MTA counterparts. For the purposes of this example, they are user1 and user2.
+# su to the zimbra account, and run the following (in multiple lines for clarity, though you could have zmprov md domain attr1 value1 attr2 value2 ...):
+<pre>
+zmprov cd zimbra.internal.example.com zimbraDomainType alias
+zmprov md zimbra.internal.example.com zimbraMailCatchAllAddress @zimbra.internal.example.com
+zmprov md zimbra.internal.example.com zimbraMailCatchAllForwardingAddress @example.com
+zmprov md zimbra.internal.example.com zimbraMailTransport smtp:mta.internal.example.com
+zmprov mcf zimbraMtaRelayHost mta.internal.example.com
+zmprov mcf zimbraMtaDnsLookupsEnabled FALSE
+zmcontrol stop
+zmcontrol start
+</pre>
+# Create a DNS A record in your INTERNAL DNS zone files for zimbra.internal.example.com. You should have already done this, but I'll put it here for maximum clarity.
+# Make sure you allow mta.internal.example.com to relay mail for zimbra.internal.example.com
+# Assuming you wish to deliver the guineapig users email to both the new [Zimbra] server for testing purposes, and also to the existing server for backup purposes, you will need to add aliases to your MTA's alias table like the following:
+<pre>
+user1: user1,user1@zimbra.internal.example.com
+user2: user2,user2@zimbra.internal.example.com
+</pre>
+
+You're done. I don't think I've forgotten anything. :)
