Difference between revisions of "Ajcody-Notes"

Line 4: Line 4:
  
 
  :set list
 
  :set list
 +
 +
==Zimbra Variable==
 +
Ways to check on different zimbra variables.
 +
 +
su - zimbra
 +
zmlocalconfig -i
 +
zmlocalconfig -d
 +
cd /opt/zimbra/conf/attrs
 +
more zimbra-attrs.xml
 +
cd /opt/zimbra/openldap/etc/openldap/schema/
 +
more zimbra.schema
  
 
=General CALDAV Issues=
 
=General CALDAV Issues=
==Lightning & Thunderbird==
+
==Lightning & Thunderbird==
 
===Lightning does not support Caldav + Free/Busy===
 
===Lightning does not support Caldav + Free/Busy===
 
Free/Busy support is only available for the Sun Cal Server.
 
Free/Busy support is only available for the Sun Cal Server.
  
Maybe we could "fake" this out within our Ldap configuration. Like RFE for Apple OD:
+
Maybe we could "fake" this out within our Ldap configuration. Like RFE for Apple OD:
  
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26619
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26619
  
===Address/username lookup doesn't occur within a new appointment===
+
===Address/username lookup doesn't occur within a new appointment===
Unfortunately, I've not figured a way around this at this time.
+
Unfortunately, I've not figured a way around this at this time.
  
 
=Apple/Mac Issues=
 
=Apple/Mac Issues=
Line 21: Line 32:
 
==iCal Issues==
 
==iCal Issues==
  
===Not seeing Calendar's===
+
===Not seeing Calendar's===
'''DO NOT USE SPACES IN THE CALENDAR NAME'''
+
'''DO NOT USE SPACES IN THE CALENDAR NAME'''
  
===iCal & Entourage Use for Calendars - Leopard/10.5 users===
+
===iCal & Entourage Use for Calendars - Leopard/10.5 users===
Because of some core issues with Apple's SyncServices, we recommend that Entourage and iCal users use iCALv3 (Mac 10.5) configured for CALDAV. Please use the Zimbra Connector instructions to setup iCal for CALDAV.  
+
Because of some core issues with Apple's SyncServices, we recommend that Entourage and iCal users use iCALv3 (Mac 10.5) configured for CALDAV. Please use the Zimbra Connector instructions to setup iCal for CALDAV.  
  
For Entourage, this recommendation stems from the fact that Microsoft decided to use WebDAV rather than CALDAV. If MS decides later to include CALDAV support for Entourage, we'll have another option.
+
For Entourage, this recommendation stems from the fact that Microsoft decided to use WebDAV rather than CALDAV. If MS decides later to include CALDAV support for Entourage, we'll have another option.
  
 
Please see bug for details:
 
Please see bug for details:
Line 33: Line 44:
 
http://bugzilla.zimbra.com/show_bug.cgi?id=27380
 
http://bugzilla.zimbra.com/show_bug.cgi?id=27380
  
===Can't see Calendar's after configuring Z-iSync for CALDAV - 10.5 users===
+
===Can't see Calendar's after configuring Z-iSync for CALDAV - 10.5 users===
You didn't follow the directions most likely. Goto iCal > Preferences > Accounts.
+
You didn't follow the directions most likely. Goto iCal Preferences Accounts.
  
 
There should be NO configured accounts prior to configuring Z-iSync for CALDAV.
 
There should be NO configured accounts prior to configuring Z-iSync for CALDAV.
Line 56: Line 67:
 
===Attendee Lookups for iCALv3/MacOS10.5===
 
===Attendee Lookups for iCALv3/MacOS10.5===
  
iCal3 [webdav] needs to use the Apple Directory Access utility for attendees (It's on 10.5). It will only work against Apple OD/CAL servers.
+
iCal3 [webdav] needs to use the Apple Directory Access utility for attendees (It's on 10.5). It will only work against Apple OD/CAL servers.
  
 
RFE filed to include necessary LDAP attributes to provide ical oattendee lookups
 
RFE filed to include necessary LDAP attributes to provide ical oattendee lookups
Line 72: Line 83:
 
iCal.app on Mac 10.4 only uses local entries in Apples Addressbook for address/username lookup for new appointments.
 
iCal.app on Mac 10.4 only uses local entries in Apples Addressbook for address/username lookup for new appointments.
  
Addressbook+LDAP configuration requires a copy of an "all/*" search in ldap into the local addressbook. Sync doesn't seem to work.
+
Addressbook+LDAP configuration requires a copy of an "all/*" search in ldap into the local addressbook. Sync doesn't seem to work.
  
 
Please see this bug comment and the 10.4 section for more details:
 
Please see this bug comment and the 10.4 section for more details:
Line 78: Line 89:
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26619#c3
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26619#c3
  
===iCal calendar color changing modifies calendar name and/or doesn't retain color===
+
===iCal calendar color changing modifies calendar name and/or doesn't retain color===
 
Fixed in 5.0.5 . See bugs for details:
 
Fixed in 5.0.5 . See bugs for details:
  
Line 85: Line 96:
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26625
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26625
  
===New Calendars don't sync unless you select "all". Mac 10.4/Z-isync===
+
===New Calendars don't sync unless you select "all". Mac 10.4/Z-isync===
 
Please see bug for details:
 
Please see bug for details:
  
Line 96: Line 107:
  
 
===Mac clients cause spamming of invitation events when they adjust calendar events===
 
===Mac clients cause spamming of invitation events when they adjust calendar events===
This, at it's root, is caused by other bugs listed here. Usually this will get resolved with the proper upgrades that the bugs require (ZCS 5.0.5+)
+
This, at it's root, is caused by other bugs listed here. Usually this will get resolved with the proper upgrades that the bugs require (ZCS 5.0.5+)
  
There is a RFE/Bug though that will also resolve this, by allowing the "action" of an appointment to be set.
+
There is a RFE/Bug though that will also resolve this, by allowing the "action" of an appointment to be set.
  
 
Please see bug for details [scheduled for 5.0.7]:
 
Please see bug for details [scheduled for 5.0.7]:
Line 104: Line 115:
 
http://bugzilla.zimbra.com/show_bug.cgi?id=10536
 
http://bugzilla.zimbra.com/show_bug.cgi?id=10536
  
===Calendar Invites can't be imported into iCal===
+
===Calendar Invites can't be imported into iCal===
 
If you look at the ics file, you might see an extra return character at the end.
 
If you look at the ics file, you might see an extra return character at the end.
  
You'll see this if an Outlook client send an invite to a user using a Mac with a thick client [Mail.app/Entourage].
+
You'll see this if an Outlook client send an invite to a user using a Mac with a thick client [Mail.app/Entourage].
  
 
This was resolved in the 5.0.5 release. Please see bug for more details:
 
This was resolved in the 5.0.5 release. Please see bug for more details:
Line 113: Line 124:
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26487
 
http://bugzilla.zimbra.com/show_bug.cgi?id=26487
  
===iTunes & iPhone configuration for CALDAV===
+
===iTunes & iPhone configuration for CALDAV===
 
Please see main wiki page on iPhone
 
Please see main wiki page on iPhone
 
http://wiki.zimbra.com/index.php?title=IPhone
 
http://wiki.zimbra.com/index.php?title=IPhone
  
If you follow the instructions about configuring the Zimbra iSync Connector for CALDAV use, there should be no issues about sync'ing with your iPhone.
+
If you follow the instructions about configuring the Zimbra iSync Connector for CALDAV use, there should be no issues about sync'ing with your iPhone.
  
At this time, new events created on a iPhone/CALDAV setup will write the event to a local calendar in iCal.app . There's no way around this yet. It's a limitation at this time with Apple's software. You can change the events calendar assignment though later via iCal.app.
+
At this time, new events created on a iPhone/CALDAV setup will write the event to a local calendar in iCal.app . There's no way around this yet. It's a limitation at this time with Apple's software. You can change the events calendar assignment though later via iCal.app.
  
Please see [http://wiki.zimbra.com/index.php?title=Image:Itunes-iphone.png Screenshot of iTunes & iPhone]
+
Please see [http://wiki.zimbra.com/index.php?title=Image:Itunes-iphone.png Screenshot of iTunes & iPhone]
  
 
===Clearing iCal cache===
 
===Clearing iCal cache===
Line 128: Line 139:
  
 
  #!/bin/sh
 
  #!/bin/sh
  rm -rf '~/Library/Application Support/SyncServices/Local/clientdata/com.apple.iCal'
+
  rm -rf '~/Library/Application Support/SyncServices/Local/clientdata/com.apple.iCal'
 
  rm -rf ~/Library/Calendars
 
  rm -rf ~/Library/Calendars
 
  rm -rf ~/Library/Preferences/com.apple.iCal.plist
 
  rm -rf ~/Library/Preferences/com.apple.iCal.plist
Line 136: Line 147:
  
 
==Use LDAP directory from ZCS for Mac Addressbook / Mail.App / iCal for Mac 10.4==
 
==Use LDAP directory from ZCS for Mac Addressbook / Mail.App / iCal for Mac 10.4==
This is generally for those that aren't using Z-iSync.
+
This is generally for those that aren't using Z-iSync.
  
 
First, test on shell that you have ldap connectivity.
 
First, test on shell that you have ldap connectivity.
  
  ldapsearch -x -H ldap://ZCSserver-name:389 "uid=ajcody"
+
  ldapsearch -x -H ldap://ZCSserver-name:389 "uid=ajcody"
  
 
That returned successfully.
 
That returned successfully.
  
Then Addressbook > Preferences
+
Then Addressbook Preferences
  
  LDAP > + (for new)
+
  LDAP + (for new)
 
  Name: anything really
 
  Name: anything really
 
  Server: ip/hostname that was used successfully in the ldapsearch string
 
  Server: ip/hostname that was used successfully in the ldapsearch string
Line 155: Line 166:
 
  * Save
 
  * Save
  
I have no idea what the "Auto Update LDAP Cards" does.
+
I have no idea what the "Auto Update LDAP Cards" does.
  
 
Then setup Mail.App for IMAP to the Zimbra server. Check preferences to use LDAP - it will use the Address Book configuration that you did prior and it should auto-resolve to a username when you do a new message.
 
Then setup Mail.App for IMAP to the Zimbra server. Check preferences to use LDAP - it will use the Address Book configuration that you did prior and it should auto-resolve to a username when you do a new message.
Line 163: Line 174:
 
One way around this is to do a wildcard search in the Addressbook and drag those items to the local addressbook.
 
One way around this is to do a wildcard search in the Addressbook and drag those items to the local addressbook.
  
Goto to Address Book, selected Directories > my ldap server > and put in the below for the search field:
+
Goto to Address Book, selected Directories my ldap server and put in the below for the search field:
  
 
  *.
 
  *.
  
This search result can then be dragged to the "All" folder in the Group column. It creates a "Last Import" item in the Group column now - it might warn about updating entries that all ready match.
+
This search result can then be dragged to the "All" folder in the Group column. It creates a "Last Import" item in the Group column now - it might warn about updating entries that all ready match.
  
 
==Sync To Do/Tasks Items in Leopard==
 
==Sync To Do/Tasks Items in Leopard==
Line 175: Line 186:
 
No target date, please vote for this RFE.
 
No target date, please vote for this RFE.
  
=What's my time and timezone?=
+
=What's my time and timezone?=
 
I wrote up the steps to make sure the ZCS server is using the correct time and timezone here:
 
I wrote up the steps to make sure the ZCS server is using the correct time and timezone here:
  
Line 188: Line 199:
 
  192.168.0.1 zimbra.test.com        zimbra
 
  192.168.0.1 zimbra.test.com        zimbra
  
If your ZCS server is behind a firewall or is being NAT'd. Make sure that resolution for the hostname on the ZCS server returns the internal IP information rather than the external IP. To test:
+
If your ZCS server is behind a firewall or is being NAT'd. Make sure that resolution for the hostname on the ZCS server returns the internal IP information rather than the external IP. To test:
  
 
  hostname -f
 
  hostname -f
Line 221: Line 232:
  
 
=Disable LDAP Replica=
 
=Disable LDAP Replica=
This is a work in progress, please don't use for production servers at this time.
+
This is a work in progress, please don't use for production servers at this time.
  
 
References:
 
References:
Line 239: Line 250:
 
Update the ldap_url value. Remove the replica LDAP server URL, below assumes you only had one replica.
 
Update the ldap_url value. Remove the replica LDAP server URL, below assumes you only had one replica.
  
  zmlocalconfig -e ldap_url=”ldap://<masterhost>
+
  zmlocalconfig -e ldap_url=”ldap:// ”
  
If other replica's exist, then the list typed is like:
+
If other replica&#39;s exist, then the list typed is like:
  zmlocalconfig -e ldap_url=”ldap://<replicahost1> ldap://<replicahost2> ldap://<masterhost>”  
+
  zmlocalconfig -e ldap_url=”ldap:// ldap:// ldap:// ”  
  
 
The hosts are tried in the order listed. The master URL must always be included and is listed last.
 
The hosts are tried in the order listed. The master URL must always be included and is listed last.
Line 257: Line 268:
 
To now disable ldap from running on the old ldap replica. The - in front of zimbraServiceEnabled is [off], rather than a + for [on].
 
To now disable ldap from running on the old ldap replica. The - in front of zimbraServiceEnabled is [off], rather than a + for [on].
  
  zmprov ms <replicahost> -- -zimbraServiceEnabled ldap
+
  zmprov ms -- -zimbraServiceEnabled ldap
  
 
=IMAPSYNC with admin login=
 
=IMAPSYNC with admin login=
 
Reference - http://wiki.zimbra.com/index.php?title=User_Migration
 
Reference - http://wiki.zimbra.com/index.php?title=User_Migration
  
  imapsync --buffersize 8192000 --nosyncacls --subscribe --syncinternaldates \
+
  imapsync --buffersize 8192000 --nosyncacls --subscribe --syncinternaldates &#92;
  --host1 server.gtds.lan --user1 yourAccount --password1 yourPassword \
+
  --host1 server.gtds.lan --user1 yourAccount --password1 yourPassword &#92;
 
  --user2 yourZimbraAccount --authuser2 admin --password2 adminZimbraPassword --authmech2 LOGIN
 
  --user2 yourZimbraAccount --authuser2 admin --password2 adminZimbraPassword --authmech2 LOGIN
  
 
  I found this description in one of the imapsync files:
 
  I found this description in one of the imapsync files:
  
"You may authenticate as one user (typically an admin user), but be authorized as someone else, which means you don't need to know every user's personal password.  Specify --authuser1 "adminuser" to enable this on host1.  In this case, --authmech1 PLAIN will be used, but otherwise, --authmech1 CRAM-MD5 is the default. Same behavior with the --authuser2 option."
+
&quot;You may authenticate as one user (typically an admin user), but be authorized as someone else, which means you don&#39;t need to know every user&#39;s personal password.  Specify --authuser1 &quot;adminuser&quot; to enable this on host1.  In this case, --authmech1 PLAIN will be used, but otherwise, --authmech1 CRAM-MD5 is the default. Same behavior with the --authuser2 option.&quot;
  
 
=ZCO Zimbra Outlook Connector=
 
=ZCO Zimbra Outlook Connector=
Line 275: Line 286:
 
# Reproduce
 
# Reproduce
 
# Get zco logs
 
# Get zco logs
#* See "Using Logging Control for Troubleshooting" within the below article :
+
#* See &quot;Using Logging Control for Troubleshooting&quot; within the below article :
 
#** http://wiki.zimbra.com/index.php?title=Outlook_Troubleshooting_Options
 
#** http://wiki.zimbra.com/index.php?title=Outlook_Troubleshooting_Options
 
# Check for core dumps - mandatory for all crashes
 
# Check for core dumps - mandatory for all crashes
Line 282: Line 293:
 
#* Creating a Core Dump from a Running Process using WinDbg :
 
#* Creating a Core Dump from a Running Process using WinDbg :
 
#** http://wiki.zimbra.com/index.php?title=Creating_a_Core_Dump_from_a_Running_Process_using_WinDbg
 
#** http://wiki.zimbra.com/index.php?title=Creating_a_Core_Dump_from_a_Running_Process_using_WinDbg
# Winhttp trace (issues where they can't connect - check zco logs first)
+
# Winhttp trace (issues where they can&#39;t connect - check zco logs first)
 
#* DbgViewHttpTrace :
 
#* DbgViewHttpTrace :
 
#** http://wiki.zimbra.com/index.php?title=DbgViewHttpTrace
 
#** http://wiki.zimbra.com/index.php?title=DbgViewHttpTrace
 
# Are there any local failures/server failures?
 
# Are there any local failures/server failures?
 
# Winmsd (dump of the local environment configuration)
 
# Winmsd (dump of the local environment configuration)
#* Start > Run > winmsd
+
#* Start Run winmsd
 
#** This might take awhile to bring up the application
 
#** This might take awhile to bring up the application
#** From app [System Information titled] , File > Export
+
#** From app [System Information titled] , File Export
 
#* What about msinfo32.exe ?
 
#* What about msinfo32.exe ?
 
# External factors (add-ins, other mapi clients)
 
# External factors (add-ins, other mapi clients)
Line 303: Line 314:
 
#* get the .msg of the item from outlook
 
#* get the .msg of the item from outlook
 
# Quick analysis of zco logs
 
# Quick analysis of zco logs
#* sync -> change record creation "-CHANGE RECORD-"
+
#* sync - change record creation &quot;-CHANGE RECORD-&quot;
 
#* follow soap requests, look for soap faults
 
#* follow soap requests, look for soap faults
#* look for the word "exception"
+
#* look for the word &quot;exception&quot;
 
#* follow soap traces
 
#* follow soap traces
 
#* ignore MAPI_E_NOT_FOUND
 
#* ignore MAPI_E_NOT_FOUND
Line 312: Line 323:
 
variable is zimbraPublicServiceHostname , as referenced in /opt/zimbra/openldap/etc/openldap/schema/zimbra.schema
 
variable is zimbraPublicServiceHostname , as referenced in /opt/zimbra/openldap/etc/openldap/schema/zimbra.schema
  
Bugs about the url's for shares that use spaces (%20), the redirection drops the %20
+
Bugs about the url&#39;s for shares that use spaces (%20), the redirection drops the %20
  
 
http://bugzilla.zimbra.com/show_bug.cgi?id=27788
 
http://bugzilla.zimbra.com/show_bug.cgi?id=27788

Revision as of 17:12, 3 June 2008

Contents

General Notes

Dos/Unix New Lines (License issues)

vi file and then

:set list

Zimbra Variable

Ways to check on different zimbra variables.

su - zimbra
zmlocalconfig -i
zmlocalconfig -d
cd /opt/zimbra/conf/attrs
more zimbra-attrs.xml
cd /opt/zimbra/openldap/etc/openldap/schema/
more zimbra.schema

General CALDAV Issues

Lightning & Thunderbird

Lightning does not support Caldav + Free/Busy

Free/Busy support is only available for the Sun Cal Server.

Maybe we could "fake" this out within our Ldap configuration. Like RFE for Apple OD:

http://bugzilla.zimbra.com/show_bug.cgi?id=26619

Address/username lookup doesn't occur within a new appointment

Unfortunately, I've not figured a way around this at this time.

Apple/Mac Issues

iCal Issues

Not seeing Calendar's

'''DO NOT USE SPACES IN THE CALENDAR NAME'''

iCal & Entourage Use for Calendars - Leopard/10.5 users

Because of some core issues with Apple's SyncServices, we recommend that Entourage and iCal users use iCALv3 (Mac 10.5) configured for CALDAV. Please use the Zimbra Connector instructions to setup iCal for CALDAV.

For Entourage, this recommendation stems from the fact that Microsoft decided to use WebDAV rather than CALDAV. If MS decides later to include CALDAV support for Entourage, we'll have another option.

Please see bug for details:

http://bugzilla.zimbra.com/show_bug.cgi?id=27380

Can't see Calendar's after configuring Z-iSync for CALDAV - 10.5 users

You didn't follow the directions most likely. Goto iCal Preferences Accounts.

There should be NO configured accounts prior to configuring Z-iSync for CALDAV.

Remove the current Account listed in iCal and redo configuration for CALDAV with Z-iSync.

Calendar events are displaying the wrong time

Apple expects the year of 1971 for the DTSTART variable within an ICS file. There is no standard that dictates this.

Zimbra (prior to version 5.0.5) was using 1601, this is in /opt/zimbra/conf/timezones.ics .

Please see bug for more details (resolved 5.0.5):

http://bugzilla.zimbra.com/show_bug.cgi?id=22808

Trick to work around address lookup for the Attendee field in iCal Events

Configure the Addressbook using one of the other recommendations on this page.

You can now drag entries from your Addressbook into the Attendee field of iCal.

Attendee Lookups for iCALv3/MacOS10.5

iCal3 [webdav] needs to use the Apple Directory Access utility for attendees (It's on 10.5). It will only work against Apple OD/CAL servers.

RFE filed to include necessary LDAP attributes to provide ical oattendee lookups

See bug [scheduled for 5.0.7]:

http://bugzilla.zimbra.com/show_bug.cgi?id=26619

Free/Busy Lookup not working as expected

The Free/Busy lookup requires auto-attendee lookup to be working.

This requires bug 26619 to be resolved for iCalv3/Mac 10.5.

Attendee Lookup for iCal/Mac 10.4

iCal.app on Mac 10.4 only uses local entries in Apples Addressbook for address/username lookup for new appointments.

Addressbook+LDAP configuration requires a copy of an "all/*" search in ldap into the local addressbook. Sync doesn't seem to work.

Please see this bug comment and the 10.4 section for more details:

http://bugzilla.zimbra.com/show_bug.cgi?id=26619#c3

iCal calendar color changing modifies calendar name and/or doesn't retain color

Fixed in 5.0.5 . See bugs for details:

http://bugzilla.zimbra.com/show_bug.cgi?id=26627

http://bugzilla.zimbra.com/show_bug.cgi?id=26625

New Calendars don't sync unless you select "all". Mac 10.4/Z-isync

Please see bug for details:

http://bugzilla.zimbra.com/show_bug.cgi?id=26653

Directory Access configuration on Macs

File that configures [system wide] for Address Book resolution

/Library/Preferences/DirectoryService/DSLDAPv3PlugInConfig.plist

Mac clients cause spamming of invitation events when they adjust calendar events

This, at it's root, is caused by other bugs listed here. Usually this will get resolved with the proper upgrades that the bugs require (ZCS 5.0.5+)

There is a RFE/Bug though that will also resolve this, by allowing the "action" of an appointment to be set.

Please see bug for details [scheduled for 5.0.7]:

http://bugzilla.zimbra.com/show_bug.cgi?id=10536

Calendar Invites can't be imported into iCal

If you look at the ics file, you might see an extra return character at the end.

You'll see this if an Outlook client send an invite to a user using a Mac with a thick client [Mail.app/Entourage].

This was resolved in the 5.0.5 release. Please see bug for more details:

http://bugzilla.zimbra.com/show_bug.cgi?id=26487

iTunes & iPhone configuration for CALDAV

Please see main wiki page on iPhone http://wiki.zimbra.com/index.php?title=IPhone

If you follow the instructions about configuring the Zimbra iSync Connector for CALDAV use, there should be no issues about sync'ing with your iPhone.

At this time, new events created on a iPhone/CALDAV setup will write the event to a local calendar in iCal.app . There's no way around this yet. It's a limitation at this time with Apple's software. You can change the events calendar assignment though later via iCal.app.

Please see Screenshot of iTunes & iPhone

Clearing iCal cache

Make and run script:

#!/bin/sh
rm -rf '~/Library/Application Support/SyncServices/Local/clientdata/com.apple.iCal'
rm -rf ~/Library/Calendars
rm -rf ~/Library/Preferences/com.apple.iCal.plist
rm -rf ~/Library/Caches/com.apple.iCal
rm -rf ~/Library/Preferences/IcalExternalSync.plist
rm -rf ~/Library/Preferences/ByHost/com.apple.iCal.helper.*

Use LDAP directory from ZCS for Mac Addressbook / Mail.App / iCal for Mac 10.4

This is generally for those that aren't using Z-iSync.

First, test on shell that you have ldap connectivity.

ldapsearch -x -H ldap://ZCSserver-name:389 "uid=ajcody"

That returned successfully.

Then Addressbook Preferences

LDAP  + (for new)
Name: anything really
Server: ip/hostname that was used successfully in the ldapsearch string
Search Base:  [leave blank]
Port: 389
Scope: Subtree
No auth needed
* Save

I have no idea what the "Auto Update LDAP Cards" does.

Then setup Mail.App for IMAP to the Zimbra server. Check preferences to use LDAP - it will use the Address Book configuration that you did prior and it should auto-resolve to a username when you do a new message.

iCal will only use address that are in the LOCAL addressbook when you use the attendee field for a new event.

One way around this is to do a wildcard search in the Addressbook and drag those items to the local addressbook.

Goto to Address Book, selected Directories my ldap server and put in the below for the search field:

*.

This search result can then be dragged to the "All" folder in the Group column. It creates a "Last Import" item in the Group column now - it might warn about updating entries that all ready match.

Sync To Do/Tasks Items in Leopard

RFE filed, please see http://bugzilla.zimbra.com/show_bug.cgi?id=12917

No target date, please vote for this RFE.

What's my time and timezone?

I wrote up the steps to make sure the ZCS server is using the correct time and timezone here:

http://wiki.zimbra.com/index.php?title=Time_Zones_in_ZCS#The_server_OS

Hostname resolution issues and testing commands

Allot of failed installs are because administrators are skipping the steps to make sure resolution is working.

Check your /etc/hosts file. You should have the localhost similar to the one below. Your ZCS server name should be replaced with the zimbra.test.com and zimbra fields. The IP address should be the IP address bound to the network interface [ip addr or ifconfig -a to confirm].

127.0.0.1	localhost.localdomain	localhost
192.168.0.1	zimbra.test.com         zimbra

If your ZCS server is behind a firewall or is being NAT'd. Make sure that resolution for the hostname on the ZCS server returns the internal IP information rather than the external IP. To test:

hostname -f
zimbra.test.com

or

domainname -f
zimbra.test.com

As long as one of the above returns the full hostname, use the command for the following. The MX lookups depend on how you are doing your mail domain and server hostname.

host `hostname -f`
 zimbra.test.com has address 192.168.0.1
host -t MX `domainname -f`
 zimbra.test.com mail is handled by 10 zimbra.test.com.
host -t MX `domainname -d`
   test.com mail is handled by 10 zimbra.test.com.

You should also have reverse records (PTR) as well. Replace 192.168.0.1 using your internal ip address, it should return something like:

host 192.168.0.1
1.0.168.192.in-addr.arpa domain name pointer zimbra.test.com

Please review wiki page on split-DNS :

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

and also the variable use of lmtp_host_lookup .

http://bugzilla.zimbra.com/show_bug.cgi?id=27988

Disable LDAP Replica

This is a work in progress, please don't use for production servers at this time.

References:

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

http://www.zimbra.com/docs/os/latest/multi_server_install/LDAP%20Replication.6.1.html

For each server that you want to change:

Stop the Zimbra services on the server, zmcontrol stop.

Check the existing ldap_url value.

zmlocalconfig | grep ldap_url

Update the ldap_url value. Remove the replica LDAP server URL, below assumes you only had one replica.

zmlocalconfig -e ldap_url=”ldap:// ”

If other replica's exist, then the list typed is like:

zmlocalconfig -e ldap_url=”ldap:// ldap:// ldap:// ” 

The hosts are tried in the order listed. The master URL must always be included and is listed last.

Additional Steps for MTA hosts.

After updating the ldap_url, rerun /opt/zimbra/libexe/zmmtainit. This rewrites the Postfix configuration with the updated ldap_url.

To stop the ldap service running on the ldap replica server.

su - zimbra
ldap stop

To now disable ldap from running on the old ldap replica. The - in front of zimbraServiceEnabled is [off], rather than a + for [on].

zmprov ms  -- -zimbraServiceEnabled ldap

IMAPSYNC with admin login

Reference - http://wiki.zimbra.com/index.php?title=User_Migration

imapsync --buffersize 8192000 --nosyncacls --subscribe --syncinternaldates \
--host1 server.gtds.lan --user1 yourAccount --password1 yourPassword \
--user2 yourZimbraAccount --authuser2 admin --password2 adminZimbraPassword --authmech2 LOGIN
I found this description in one of the imapsync files:

"You may authenticate as one user (typically an admin user), but be authorized as someone else, which means you don't need to know every user's personal password. Specify --authuser1 "adminuser" to enable this on host1. In this case, --authmech1 PLAIN will be used, but otherwise, --authmech1 CRAM-MD5 is the default. Same behavior with the --authuser2 option."

ZCO Zimbra Outlook Connector

The complete troubling-shooting guide (dev info requests)

  1. Reproduce
  2. Get zco logs
  3. Check for core dumps - mandatory for all crashes
  4. Winhttp trace (issues where they can't connect - check zco logs first)
  5. Are there any local failures/server failures?
  6. Winmsd (dump of the local environment configuration)
    • Start Run winmsd
      • This might take awhile to bring up the application
      • From app [System Information titled] , File Export
    • What about msinfo32.exe ?
  7. External factors (add-ins, other mapi clients)
  8. Network topology (firewall, proxy, etc)
  9. Server topology (single/multi-node, clustering, nginx, 3rd party lb)
  10. Search bugzilla
  11. Search old support cases
  12. Can we get remote access?
  13. Can we get an account on the server?
  14. Can we access the account in question?
  15. Get the id of the item
    • get the original of the item from the server (mime representation)
    • get the .msg of the item from outlook
  16. Quick analysis of zco logs
    • sync - change record creation "-CHANGE RECORD-"
    • follow soap requests, look for soap faults
    • look for the word "exception"
    • follow soap traces
    • ignore MAPI_E_NOT_FOUND

Public Service Hostname

variable is zimbraPublicServiceHostname , as referenced in /opt/zimbra/openldap/etc/openldap/schema/zimbra.schema

Bugs about the url's for shares that use spaces (%20), the redirection drops the %20

http://bugzilla.zimbra.com/show_bug.cgi?id=27788

http://bugzilla.zimbra.com/show_bug.cgi?id=27477

Jump to: navigation, search