| Rev | Author | # | Line |
|---|---|---|---|
| 1 | GreigMcGill | 1 | !![Zimbra] Caveats |
| 2 | |||
| 3 | * [Zimbra] wants a dedicated box. Don't try to fake it. Just give it what it wants, it will make you happy. Specifically, it wants HTTP{s}, SMTP, IMAP{s}, POP3{s}, LDAP, and some other ports for it's own admin functions and auxilliary software (virus and spam scanning for example). | ||
| 4 | |||
| 5 | !!Configuring [Zimbra] With An Existing MTA For Testing | ||
| 6 | |||
| 7 | 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. | ||
| 8 | |||
| 2 | GreigMcGill | 9 | * Mail domain (external MXs serve this): example.com |
| 10 | * Internal domain: internal.example.com | ||
| 11 | * Primary MTA (runs exim, but that doesn't matter): mta.internal.example.com | ||
| 12 | * [Zimbra] Server: zimbra.internal.example.com | ||
| 13 | |||
| 14 | # Create example.com as your primary domain during setup of [Zimbra]. | ||
| 15 | # 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. | ||
| 16 | # 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 ...): | ||
| 17 | <pre> | ||
| 18 | zmprov cd zimbra.internal.example.com zimbraDomainType alias | ||
| 19 | zmprov md zimbra.internal.example.com zimbraMailCatchAllAddress @zimbra.internal.example.com | ||
| 20 | zmprov md zimbra.internal.example.com zimbraMailCatchAllForwardingAddress @example.com | ||
| 21 | zmprov md zimbra.internal.example.com zimbraMailTransport smtp:mta.internal.example.com | ||
| 22 | zmprov mcf zimbraMtaRelayHost mta.internal.example.com | ||
| 23 | zmprov mcf zimbraMtaDnsLookupsEnabled FALSE | ||
| 24 | zmcontrol stop | ||
| 25 | zmcontrol start | ||
| 26 | </pre> | ||
| 27 | # 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. | ||
| 28 | # Make sure you allow mta.internal.example.com to relay mail for zimbra.internal.example.com | ||
| 29 | # 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: | ||
| 30 | <pre> | ||
| 31 | user1: user1,user1@zimbra.internal.example.com | ||
| 32 | user2: user2,user2@zimbra.internal.example.com | ||
| 33 | </pre> | ||
| 34 | |||
| 3 | GreigMcGill | 35 | You're done. I don't think I've forgotten anything. :) |
| 4 | GreigMcGill | 36 | |
| 37 | Currently users on Zimbra emailing each other will not have their email on the main MTA, and so not backed up. As they have been made aware this is a testing environment and should only be used internally for test emails etc., it shouldn't matter, but it would be nice to fix. |
lib/blame.php:177: Warning: Invalid argument supplied for foreach()