Known Issues for 4.7.0

The following are known issues or limitations in this release:

• PMM mobile app fails login attempts after RHEL updates are applied to the Gateway

  Following Red Hat updates to the Gateway, attempts to log in to the PMM mobile application result in the following error:

  PMM Mobile App (Error 400) after installing RHEL updates.

• No network detected with SuperMicro 250 and 500 servers

  E500, W250, and W500 (SuperMicro 5016I models) are currently not supported due to networking issues.

  What can I do?

  Update the server BIOS, using the guidelines provided by your hardware vendor. This might resolve any hardware compatibility issues.

• Microsoft Edge (Windows 10) browser fails with message tracking

  The Gateway user interface fails when viewing or tracking a message if viewed in Microsoft Edge (build number 40.* onwards). A blank page is displayed, followed by a warning and an error indicating that 'a problem was encountered'.

  What can I do?

  Use a different browser, where possible.

• BATV tag stripping leaves incorrect sender address in PMM

  Sender addresses displayed in PMM might be corrupted with BATVBounce Address Tag Validation tags following tag-stripping. This results in these addresses being unusable as trusted senders.

• SPF checks lookup deprecated SPF RR type

  SPFSender Policy Framework failures might be encountered due to SPF checks looking up SPF RR records. This is probable with more than 5 SPF includes in the owner's domain.

• Adding annotations adds wrong encoding

  It is possible that adding an annotation to messages also adds a language character set to a 'Content-Type' header. This causes problems when displaying the modified message.

• PDFs renamed as 'attachment.pdf' in quarantine

  PDFs containing extended ASCII characters (such as #) might be renamed as 'attachment.pdf' if downloaded following a processing fail.

  What can I do?

  Rename the file using standard characters and save.

• Hyphen not permitted in DKIM selector

  When configuring a DKIMDomainKeys Identified Mail selector, hyphens are not permitted. Lower case characters and numbers are valid.

• Unable to install the Gateway on Generation 2 HyperV virtual machine

  When trying to install the Gateway as a virtual machine using a HyperV 2016 host, the system fails to boot and displays the following error:

  No UEFI-compatible file system was found.

  This is a consequence of ISO installation, which does not support the UEFI boot process.

• Special characters in HTTP proxy user password are not encoded in Server Console

  The following characters are not automatically percentage-encoded when entered as an HTTP proxy password in the HTTP proxy dialog in Server Console:

  <>"#%{}|^~[]`;/?:@=&

  What can I do?

  Enter the character using the solution provided by this article:

  https://access.redhat.com/solutions/47925

  A full list of translated character encoding can also be found here:

  http://unicodelookup.com/.

  Example: http://domain\username:P@$$w:rd@192.168.1.2:8080 should be entered as http://domain\username\:P%40%24%24w%3Ard@192.168.1.2:8080.

• Unable to install on a Dell R430 when booting from a USB device

  Minimal installation of Red Hat 6.9 from a USB removable device fails on a Dell R430 machine. An error message indicates that an 'uncompression error' has halted the installation.

  This is a known issue regarding the support of Red Hat 6.9 on this model.

  What can I do?

  Use a Clearswift installation DVD to install Red Hat 6.9 on a Dell R430. We also recommend updating the BIOS using guidelines provided by your hardware vendor.

• Unable to peer a version 3 Gateway with a version 4 Gateway following RHEL update

  A certificate issue caused by a Java package update issued for RHEL prevents you from peering a version 3 Gateway with a version 4 Gateway.

  What can I do?

  To resolve this issue you must create a new KeyStore on the version 3 system.

  To generate a certificate and deploy it to the KeyStore for Tomcat to use:

  1. Assume root role at the command line.
  2. cd /opt/msw/data/
  3. mv keystore keystore.orig

  4. keytool -genkey -alias tomcat -keyalg RSA -sigalg SHA1withRSA -keystore keystore -storepass changeit --dname "CN=Clearswift,OU=Clearswift,O=Clearswift,L=Reading,S=Berkshire,C=Uk" -validity 3650

     Update the certificate attributes (CN, OU, O, etc.) with your own details

     After entering this command, the system prompts you for the key password for Tomcat. Press RETURN if this is the same as the KeyStore password.

  5. uiservicecontrol restart tomcat

  To get the certificate signed by a certificate authority:

  1. Generate the certificate signing request:

     keytool -certreq -keyalg RSA -sigalg SHA1withRSA -alias tomcat -keystore keystore -file certreq.csr

  2. Once the certificate is signed by the CA, import it into the store:

     keytool -import -alias tomcat -keystore keystore -file server.crt

  3. uiservicecontrol restart tomcat
• Gateway configuration not updated when removing IP address or network adapter using Server Console

  When using Server Console to change your network configuration settings, Server Console is unaware if a Gateway configuration references a particular network adapter or IP address. For example, if PMM references a network adapter or IP address.

  What can I do?

  When disabling network adapters and deleting or changing IP addresses in Server Console, you should update the Gateway configuration immediately after if these network adapters or IP addresses were in use by the Gateway.