Measy configuration

Create a file called measy.json in the measy folder. It will have the following sample structure:

    "exchange": [{
      "alias": "my_alias",
      "server": "",
      "username": "exchange_user",
      "password": "exchange_password",
      "email": "",
      "product_owners": [""],
      "on_unrelated": {
        "action": "trash",
        "recipients": [],
        "subfolder": ""
      "on_success": {
        "action": "trash",
        "recipients": [],
        "subfolder": ""
      "disable_ssl_validation": true
    "earchive_strings": ["<INVOICE", "<cbc:ProfileID>EARSIVFATURA</cbc:ProfileID>"],
    "puller_module": "measy.puller.multi_exchange_earchive",
    "flask": {
      "active": true,
      "port": 5000
    "sap": {
      "wsdl_link": "",
      "binding_address": "",
      "username": "my_sap_user",
      "password": "my_sap_password"

Modify the values to match your own values. Note that Measy supports multiple Exchange accounts.

Most of the fields are very intuitive. on_unrelated and on_success requires special attention though. The first one determines the fate of unrelated E-Mails in the inbox. The second one determines the fate of a successfully received E-Archive E-Mail message. action should be filled with one of the following values:

  • An empty value tells Measy to do nothing. This may make sense for unrelated E-Mails.
  • delete: Deletes the E-Mail completely.
  • trash: Puts the E-Mail into the trash folder.
  • forward: Forwards the E-Mail to the accounts defined in recipients.
  • move_to_inbox_subfolder: Moves the E-Mail to the inbox subfolder defined in subfolder.
  • move_to_root_subfolder: Moves the E-Mail to the root subfolder defined in subfolder.

Being a Databus implementation, Measy can run on either local JSON files or an SQL Server database.

Out of the box, the application will run on local JSON files.

If you prefer to run it on SQL Server, you need to modify accordingly. Check Databus documentation for details.

Databus configuration

Assuming that you will run the application on local JSON files, create the folder structure: measy/data/json_db/clients/my_client. "my_client" symbolizes the name of your company, you can pick another name (preferably without spaces).

Edit so that the literals on DispatcherTicket matches your my_client value; replacing the default "ecztug" value.

    dispatcher_ticket = DispatcherTicket(
            ExternalConfigFile("ecztug", "measy", path.join(databus.get_root_path(), "measy.json"))

Create two subfolders:

  • measy/data/json_db/clients/my_client/log

  • measy/data/json_db/clients/my_client/pqueue

Create a file called measy/data/json_db/clients/my_client/config.json , which has the following structure:

  "log_life_span": 1,
  "passengers": [
      "name": "measy.passenger.email_earchive",
      "pullers": [ "measy.puller.multi_exchange_earchive" ],
      "queue": "databus.pqueue.primal_queue",
      "processors": [ "measy.processor.earchive_filter" ],
      "pushers": [ "measy.pusher.sap_earchive" ],
      "sync_frequency": 1,
      "queue_life_span": 1

Here, you can alter the numeric values to change the behavior of Databus.

  • log_life_span : (days) For how many days should the log files be kept on the server?

  • sync_frequency : (minutes) How often should Measy check the Exchange accounts

  • queue_life_span : (days) For how many days should the finished queue entries be kept on the server?


ABAP components need to be configured on your SAP system manually. You can contact us for that.