This readme describes how to configure Micro Focus Email Connector. Refer to the Micro Focus Community and Micro Focus Connect Help Center for further configuration instructions.
The Micro Focus Email for Micro Focus Connect (Micro Focus Email Connector) lets you synchronize Email assets to assets in OpenText Products, for example assets found in the Micro Focus Octane Connector.
Copyright 2018 - 2024 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors ("Open Text") are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Except as specifically indicated otherwise, this document contains confidential information and a valid license is required for possession, use or copying. If this work is provided to the U.S. Government, consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
AccuRev Connector for Micro Focus Connect (AccuRev Connector) lets you synchronize AccuWork assets like stories, tasks, and change requests with those in other Micro Focus Hub repositories and clients like StarTeam Agile.
| Contents | ||
|---|---|---|
| Installation and Upgrade Information | Technical Notes | |
| Prerequisites | Known Issues | Need assistance with the product? |
This version of the connector supports general Email protocols
Unless otherwise specified, for any given MF Connect connector from OpenText, all versions of the connector product that are officially released and supported by it's vendor both four months before the time of the release of the connector as well as at the time of using the connector, are supported by OpenText. Not all product versions will be tested and validated by OpenText for each connector release. Instead, OpenText chooses a subset of versions that we deem representative or most important to run validation and certification tests against. These selected versions are mentioned in the respective connector read-me, clearly identifying them as "validated" or "certified". As stated above, this does not mean that Micro Focus Connect does not support other product versions – it only means that no validation test cycle was executed for the other versions.
This version of the connector supports emails as an asset type.
This connector requires at least build 24.2 of Micro Focus Connect and can be configured using the Micro Focus Connect UI.
The thesaurus.properties file should be copied to the Micro Focus Connect's AppData\data folder.
This connector is an update to the installed connector, you should remove (or move to a directory outside of the connectors) and replace the AppData\connectors\mfcConnectorEmail\mfcConnectorEmail*.jar file with the one provided.
The following information contains notes regarding installation, but does not replace the entire process.
When upgrading to 4.1.1, you need to remove all emails from the configured mailbox. Otherwise, the email connector will create duplicate items. This is caused by a Java-11 bug: JDK-8211750
In order to use this connector, you will need to collect and enter this information in the Micro Focus Connect user interface:
Email's attachments are not supported. Any kind of attachments will not be part of the synced email content.
When selecting a fallback user a message will state there are no users.
The project map syntax for the email connector is address:password. For example, john@foo.com:foopassword. If the password isn't in the project, e.g. there is no colon, Connect uses the password in the Datasource.
Due to the nature of how Pop3 handles emails once they are read on the server, when you use the Pop3 protocol, you cannot have multiple email connectors linking to a single inbox.
When using the email Connector with Gmail, you need to enable the Allow less secure apps setting in Gmail.
The email connector allows email content to be synchronized between systems.
The ProjectMap value for a Synchronization using the Email Connector is the email user name and password separated with a ":". If you have only 1 email source then these will be the values from the DataSource definition.
The email connector supports properties below for the Email type:
Get support enables you to open a support incident or to submit a bug. You can also browse many helpful support resources.