Known Issues Articles

 

Known Issue#: EPHE-9238

Topic/Category: Email Import

Ephesoft version(s) Affected: 4.0.2.0 – 4.0.2.1

Issue: When configuring Email Import in Ephesoft, if the username used to connect to your mail server does not require the fully qualified email address, Ephesoft will not allow you to save the settings. This is based on the required information for the email server. We have seen this when Microsoft Exchange is configured to allow usernames without the @sample.com extension.

 

In the example here, the username for the email import does not contain the @sample.com part of the email address and will not allow you to save your settings.(notice the red background on the text box)

EmailImport2

 

In order to save the email import details, the username must have the @sample.com after the username of the email address. See screenshot here:

EmailImport1

 

 

Root Cause: Change in the validation of the field in 4.0.2.0. This did not effect 3.1.X.X versions.

Solution:

Workaround:

Instructions

  1. Test the email import settings without the @sample.com(insert your domain instead of sample.com) by using the Test Email button.
  2. If this succeeds, enter the fully qualified email address in this field in order to save the settings
  3. Once the settings are saved, open the ephesoft database in HeidiSQL or your SQL client of choice (MS SQL studio, phpMyAdmin, DBeaver, MySQL)
  4. Navigate to the batch_class_email_configuration table
  5. Find the entry for the specific email import settings that you just saved, and remove the @sample.com domain extension and save the row.
    EmailImport5
  6. This should start the email import on the cron schedule that is configured.

 

 

< BackKnown Issues Main PageNext Known Issue #? >

 

 

 

Was this article helpful to you?

J.D. Abbey