Jump to: navigation, search

Known Issues and Recommendations

E-mail Server

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of E-mail Server. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.

In release and later, embedded images are not supported in Thunderbird clients. They are displayed as attachments.

When E-mail Server is working with Exchange Web Services, to ensure that it correctly converts CP932 to MS932 in the Subject line, set the Locale to Japan: Control Panel -> Region and Language -> Administrative -> Change system locale... -> Japanese (Japan).

Email file attachments with the docx extension are not supported by the UCS-X (UCSX solution. Inbound emails containing these file attachments are delivered to agents, but without the attached file. Agents cannot upload the attachment with the . docx extension in Workspace Web Edition (WWE) when composing an outbound email. A Standard Response does not allow the .docx extension attachments.

ID: ESR-15335 Found In: Fixed In: 

A configured attachment in a Standard Response cannot be uploaded in the UCS-X (UCSX solution. The email is delivered to the recipient, but without the attached file.

ID: ESR-15326 Found In: Fixed In: 

The UCS-X (UCSX solution does not support outbound email interactions containing a Standard Response with a Field Code. These emails will fail and not be delivered to the recipient.

ID: ESR-15325 Found In: Fixed In: 

When the feature of splitting the To and CC email recipient list is enabled (copy-message-to-recipients is set to true), if there is any invalid email address in the recipient list, E-mail Server does not create any interactions even for the valid recipients.

ID: ESR-15034 Found In: Fixed In: 

E-mail Server does not send a chat transcript of the chat that is empty.

ID: ESR-15224 Found In: Fixed In: 

The startup file JavaEmailServerDriver.ini of E-mail Server contains some Java arguments that cause E-mail Server to handle OutboundAcknowledgement emails incorrectly and reply to requests in Unicode instead of expected STG values.

ID: ESR-14733 Found In: Fixed In:

The Installation Wizard incorrectly allows you to pick Java 8 as a supported version. Java 7 is the only supported version.

ID: ESR-11063 Found In: Fixed In:

When operating with Exchange 2007, there is the following issue when an email with an attachment is sent to multiple users: if one of the recipient email addresses is not valid, delivery fails for all recipients. As a workaround, upgrade to Exchange version 2010 or higher.

ID: ESR-10974 Found In: Fixed In: 

The exchange-version option is missing from the [smtp-client] section of the E-mail Server template. This option specifies the version of the corporate Exchange Server that E-mail Server connects to.

Default Value: No default value
Valid Values: A valid exchange server version, such as Exchange2007_SP1, Exchange2010, Exchange2010_SP1, Exchange2010_SP2, Exchange2010_SP3, Exchange2013, Office365
Changes Take Effect: At the next pop cycle
ID: ESR-10859 Found In: Fixed In:

E-mail Server does not connect to the expected Configuration Server port in the following scenario:

  1. Configuration Server has an 'autodetect' port configured in addition to a 'default' port.
  2. At startup E-mail Server connects to the 'autodetect' port.
  3. The primary Configuration Server is stopped.
  4. E-mail Server reconnects to the 'default' port of Configuration Server backup instead of the 'autodetect' port.

As a workaround, in the E-mail Server Application configure a connection to the Configuration Server Application, selecting the 'autodetect' port.

ID: ESR-10692 Found In: Fixed In: 

After disconnecting from Configuration Server, E-mail Server is unable to process both inbound and outbound emails until the connection is re-established.

ID: ESR-9563 Found In: Fixed In: 

Configuring E-mail Server to use Java 1.6 does not enable IPv6. When E-mail Server is configured to use Java 1.6, it uses IPv4 to listen on its ESP port and connect to other servers. IPv6 is enabled with Java 1.7 only.

ID: ESR-10327 Found In: 8.1.400.10 Fixed In: 

For E-mail Server to use an Exchange Web Server connector, you must select JDK 1.7 (or higher when available) when installing E-mail Server.

ID: ESR-7706 Found In: 8.1.400.09 Fixed In: 

When using E-mail Server with an Exchange Web Services connector, in the rare case of an e-mail with an HTML part formatted as UTF-7 and containing a Byte Order Mark (BOM) character, an incorrect character may be displayed at the beginning of the text.

ID: ESR-7645 Found In: 8.1.400.06 Fixed In: 

In some Non-Delivery Reports (NDR), Exchange Server puts the wrong address in the 'to' field of the e-mail header.

ID: ESR-7406 Found In: 8.1.400.01 Fixed In: 

Under high loads on the database, to avoid inconsistencies such as duplicated inbound e-mails, E-mail Server should have the timeout of its connection to UCS set to a higher value than the sum of the two following values:

-The timeout of UCS's connection to its Database Access Point (DAP). Default value is 60s.

-The value of the UCS option third-party-max-queueing-time (in the 'settings' section). Default value is 15,000 ms.

This means that the E-mail Server option settings/ucs-reconnect-timeout should be higher than 75,000 ms; for example, 80,000 ms.

ID: ESR-8351 Found In: Fixed In: 

Internationalization Issues

Information in this section is included for international customers.

There are no internationalization issues for this product.

This page was last edited on February 22, 2021, at 19:10.
blog comments powered by Disqus