---
title: Graph Mail Project
slug: en/graph-mail-project
description: This document offers a comprehensive guide on how to configure the config.properties file, docker-compose.yml file, and dependencies for the Graph Mail Project. It explains the project's functionality, highlighting its methods for obtaining email messages
docTags: 
createdAt: 2023-03-02T11:29:55.000Z
---

## Config File

The following properties must be set in the config.properties file of the Graph Mail Project, according to the client scenario:

:::BlockQuote
*JMS\_CONNECTION\_FACTORY\_JNDI = jms/RemoteConnectionFactory
JMS\_WILDFLY\_REMOTING\_URL = http-remoting://172.18.0.4:8080
JMS\_QUEUE\_JNDI = jms/queue/queue/graphMailQueue
JMS\_READ\_MAIL\_QUEUE\_JNDI = jms/queue/queue/readGraphMailQueue
JMS\_USERNAME = jmsuser&#xA;*&#x4A;MS\_PASSWORD = 352TEDDWtHpfRObR166VOuOBI1F4
GRAPH\_APP\_ID = 51255c25-165446-25d5sd5d5-dssdsd
GRAPH\_USERNAME = [seue-mail@seudominio.gov.br](#)
GRAPH\_PASSWORD = QsPlWSOK
GRAPH\_MAIL\_FOLDERS\_LIST = Inbox
:::

### docker-compose.yml

The correct file localization in the docker-compose.yml file from the Graph Mail Project must be set. Also, set the defined folders for image and attachment sharing.

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/zjcNOXXIHDUbahrK5c_Ks_image.png)

### Dependency

The Graph Mail Project depends on the Service Management project, so it should only be executed when the Service Management one is running.

**Functioning**

- A Thread or Job:
  - Obtains the e-mail messages occasionally and extracts the: **sender**, **subject**, **body**, and **attachments&#x20;**&#x66;rom the parameterized list of folders;
  - Registers messages received in a specific queue for registration of tickets in WildFly, containing the name of the folder, the queue, and the content of the email, including the list of attachments;
  - Etches the attachments to a mapped folder on a volume that SM is able to access;
  - Performs the "Email control procedure":
    - Processing control: the system reads a predefined folder, allowing the user to create filtering rules, specific to the ticket registration. It can be an incident, problem, change or release ticket: what determines it is the automatic action registration;
    - ﻿<font color="#ff0004">Destination of the processed message\: the system marks the already processed message as read.﻿</font>
    - Mailbox sharing:&#x20;
      - It can be used by the user and the system - if the folder for reading is implemented;
      - It will also be used for sending e-mails.

