Overview:
eCertify works by emailing a PDF of the required document, a control file in XML format and sometimes a data XML file to ecertdirect@ecertify.com which are then forwarded to the Chamber for stamping, and returned in the form of an XML and PDF.
They have an odd system that is extremely stubborn around email addresses, to the point where if your company switches domains you literally have to register brand new eCertify accounts because your email address has changed.
In order to submit Certificates for verification via eCertify you must have what eCertify calls a “Vendor Central Email Address” which is a centralised whitelisted email address that all submissions must come from. The mail filter must allow XMLs and PDFs to pass to and from this email address freely.
Customer Actions:
-
Create a service email address for this purpose, probably called prodoc@[company].[tld]
-
Ensure XMLs (txts) and PDFs are allowed to pass unmolested, amendments can go out with a BOM and Mimecast loses its mind over txt files with a BOM.
-
Mail Server credentials must match that of the users (this will be opened up in the future)
-
The service account cannot use two-factor authentication, please generate an app-password if your organisation uses two-factor authentication or switch 2fa/mfa off on the account.
Required Files:
None
Outcome:
-
Mail server and service email details passed to Prodoc.