RSS Feed
Knowledgebase : NotifyLink Enterprise Server > Zimbra
Zimbra: Certain attachments on email messages appear on the device as EmailvCard.txt When email messages are being sent internally from the Zimbra web client all attachments appear as EmailvCard.txt and not process properly. This only occurs with the...
Zimbra: This issue applies to contacts that are not in the user's Default Address Book. The default address book is defined on the user's Contact Sync Settings > Choose Address Books page in the NotifyLink web. If a contact that is not part of the def...
If an address book (contact folder) is deleted on the Zimbra server or in Outlook, the contacts associated with it should be deleted from the device.  This is not happening, however, unless the Trash folder is emptied first.
Zimbra: When an event or task created on the device occurs or is due on a date beyond the Look Ahead range, the event/task is not deleted until midnight or until the LookBack/LookAhead range changes. Events or tasks created on a device verify agains...
Zimbra:Issue: If you rename a folder on a Scalix or Zimbra mail server that is marked for synchronization, the iPhone will continue to receive mail for that folder, but the name will not be updated on the device. It will still reflect the original folder ...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for Zimbra Pre-Installation Guide  under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components are w...
Zimbra: An event created on the device set to recur on the 31st of each month does not have an instance on the server in months that do not have this date (Feb, April, etc).  All instances are created on the device
Zimbra: Shared address books are only listed on the Choose Address Books page for pim processing when the NLES user is the creator of the shared address book. This is due to shared address books being returned as a link rather than a folder to other ...
Zimbra: Users that have been added to the Zimbra server with "Hide in GAL" checked, will appear without information in the available users list when adding the user to the NotifyLink server.  User entries made like this in Zimbra appear ...
With NotifyLink Enterprise Server 4.3.1 for Zimbra 4.5.0...All day events or all day meeting requests originating on the server show up on the device as an all day event for today's date.  Creating an all day event, however, on the device shows up corr...
Zimbra: Calendar event reminders created on the device do not synchronize correctly to Zimbra Connector for Outlook. The event reminder time appears in Outlook as 15 minutes prior to the event, no matter what the reminder was set for on the device.  A ...
If an address book (contact folder) is deleted on the Zimbra server or in Outlook, the contacts associated with it should be deleted from the device.  This is not happening, however, unless the Trash folder is emptied first.
Zimbra: If a completed task's status is changed back to incomplete on the device, the Date Completed field does not get cleared in Outlook 2003.  Task Status and Percent Complete change in Outlook 2003, but the Date Completed remains the same. This may...
Zimbra: This issue applies to iPhone/iPod users who have tagged their trash folder for synchronization in the NotifyLink Enterprise Server web.  For Zimbra users, email with no body which is synchronized to an iPhone/iPod touch and subsequently deleted...
On Oracle Beehive 2.0.1.1.0, when a single calendar event and a recurring calendar event are deleted in the same PIM cycle via Zimbra Web access, GO!NotifyLink receives only the deletion for the recurring event. The result is that the items are deleted...
Zimbra:A change made on the device to any instance (first, middle, or last) of a recurring event creates a duplicate instance instead of processing the change.
Zimbra:A change made on the device to any instance (first, middle, or last) of a recurring event creates a duplicate instance instead of processing the change.
Zimbra: A change made on the device to any instance (first, middle, or last) of a recurring event creates a duplicate instance instead of processing the change.
Zimbra: When an event or task created on the device occurs or is due on a date beyond the Look Ahead range, the event/task is not deleted until midnight or until the LookBack/LookAhead range changes. Events or tasks created on a device verify against ...
Zimbra:This issue involves meeting invitations that have not been responded to prior to midnight.  If the Zimbra user does not respond before midnight, the calendar event for the meeting is deleted from the device.  The event still appears on the server, ...
Zimbra: This issue involves PIM items (calendar events, contacts, and tasks) created on the Zimbra server and then modified on the device.  When changes are made to the PIM item on the device and synchronized to the server, any content in fields unsu...
This issue applies to address books created in Outlook, not address books created in Zimbra Web Access.Pre-existing contacts in multiple address books (address books other than the default) will not synchronize to the device.  New contacts added to the ad...
Zimbra:When using NotifyLink for Zimbra, I receive multiple meeting invitations for one single appointment. If multiple folders are selected to process for a user's account, they will receive one Accept/Decline message for each folder selected. In additi...
Zimbra:This issue involves individual or recurring events created on the device with dates beyond the look-ahead range.  When events created on a device exceed the look-ahead range, they should be deleted when they verify against the look-ahead cutoff on ...
Zimbra: This issue involves individual or recurring events created on the device with dates beyond the look-ahead range.  When events created on a device exceed the look-ahead range, they should be deleted when they verify against the look-ahead cuto...
Zimbra: When the time of a recurring event is changed on a device to now occur in the Greenwich Mean Time (GMT) shadow, an extra instance may appear at the end of the series when viewed in Outlook connector.  In the Zimbra web client it appears correctly...
Zimbra:This issue involves recurring series events, created on the device, which cross over the Daylight Saving Time (DST) range.   - Those created outside DST (Nov-March):  Occurrences which then fall during DST (March-Nov) synchronize to the server 1 h...
Zimbra:This issue involves recurring events created on the device which occur in the GMT shadow and are set for relative monthly dates (example: last Tuesday of each month). Recurring events with these characteristics may not always appear on the date int...
Zimbra: This issue involves recurring events created on the server that do not have any instances in the look-back/look-ahead range.  Instances that occur outside the look-back/look-ahead range should not be sent to the device.  However, the server ...
Zimbra: Russian or Chinese characters used to enter a calendar event or task in Outlook Connector are synchronized correctly to the device, except in the notes field.  Russian and Chinese characters appear as question marks in the notes field.
Zimbra: Task reminders created on the device do not synchronize correctly to Zimbra Connector for Outlook. The task reminder time appears in Outlook at 8 a.m. on the day a task is set, no matter what the reminder was set for on the device.  It also ap...
Zimbra: When an event or task with Upper ASCII characters in the "notes" field is created or modified on the device and is subsequently modified using Outlook, the ASCII characters synchronized back to the device are UTF-8 encoded (appear as u...
Zimbra:Zimbra users with usernames that start with something other than an alpha character will only display on the NotifyLink available users list if you select "View All." NOTE:  The "available users" list appears when adding new us...
Zimbra:Contacts created or modified in Zimbra Connector for Outlook with the "web page address" filled in, synchronize that address to both the "work web address" and the "home web address" fields on the device.  This does no...