Wiki source code of Serveur email
Last modified by Aurelie Bertrand on 2025/11/14 11:59
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | (% class="wikigeneratedid" id="HServeuremail" %) | ||
| 2 | You can specify an email server to be used for sending email, particularly for email devices. To do this: | ||
| 3 | |||
| 4 | 1. Enter the following parameters: | ||
| 5 | 1*. **Mail protocol**: smtp, smtps or imap | ||
| 6 | 1*. **Mail server**: address of your email server | ||
| 7 | 1*. **Port **: server network port: 587 (TLS/STARTTLS), 465 (SSL) | ||
| 8 | |||
| 9 | (% class="box infomessage" %) | ||
| 10 | ((( | ||
| 11 | ℹ Recommendations regarding the port to use change regularly and may depend on the mail service, so check with your mail service provider for more information about the ports to use. | ||
| 12 | ))) | ||
| 13 | |||
| 14 | (% start="2" %) | ||
| 15 | 1. Check the** Use TLS/SSL protocol** for secure communication box. | ||
| 16 | SSL and TLS both provide a means of encrypting a communication channel between two computers (for example your computer and a server). TLS is the successor to SSL and the terms SSL and TLS are used interchangeably unless you are referring to a specific version of the protocol. | ||
| 17 | 1. Enter the** From mail address**: this will appear as the sender of the email. | ||
| 18 | 1. Select the authentication type: | ||
| 19 | 1*. Check the **Authentication required (STARTTLS)** box to initiate an encrypted connection via TLS (usually via port 587). In this case, several email servers require authentication to protect against email address spoofing. | ||
| 20 | 1**. **Usr login**: identifier for authentication with the server | ||
| 21 | 1**. **Mail account password**: authentication password | ||
| 22 | 1*. Check the **Use OAuth** box to use Google or Microsoft OAuth authentication configured on the [[OAuth>>doc:Digdash.deployment.configuration.configuration_guide.oAuth.WebHome]]. | ||
| 23 | |||
| 24 | (% class="box infomessage" %) | ||
| 25 | ((( | ||
| 26 | Successful delivery depends on the SMTP server configuration. Sending can fail if the connection/authentication attempt is made from an application that could present a "risk" (in this case DigDash). One way of dealing with this is to authorise the application in the mail server settings. | ||
| 27 | ))) | ||
| 28 | |||
| 29 | (% start="5" %) | ||
| 30 | 1. Click **Save **to accept the changes you have made. | ||
| 31 | If you have chosen to use OAuth authentication and it is configured on the [[OAuth>>doc:Digdash.deployment.configuration.configuration_guide.oAuth.WebHome]] page, you will be redirected to Google / Microsoft. Follow the steps to verify your information and authorise DigDash to access your Google / Microsoft account. This gives the application created during the OAuth configuration the right to send emails via GMail / Exchange and to access your account information in order to use your email address. | ||
| 32 | ➡ You can then send an email via an [[Email device>>doc:Digdash.user_guide.studio.managers.devices.WebHome]]. | ||
| 33 | |||
| 34 | [[image:Mail_server_EN.png]] | ||
| 35 | |||
| 36 | = Email sending debugging = | ||
| 37 | |||
| 38 | The debugging of email sending can be activated in the system.xml file: | ||
| 39 | |||
| 40 | 1. On the server workstation, edit the system.xml file located in: | ||
| 41 | **<digdash.appdata>/Enterprise Server/ddenterpriseapi/config** | ||
| 42 | 1. Add the line : | ||
| 43 | |||
| 44 | {{code language="xml"}} | ||
| 45 | <Property key="PROP_USE_DEBUG_MAIL_SENDER" value="true"></Property> | ||
| 46 | {{/code}} | ||
| 47 | |||
| 48 | Between {{code language="xml"}}<SystemProperties>{{/code}}and {{code language="xml"}}</SystemProperties>{{/code}} | ||
| 49 | |||
| 50 | (% start="3" %) | ||
| 51 | 1. [[Restart the>>doc:Digdash.deployment.installation.upgrade_dde.WebHome||anchor="Start_server"]] DigDash server. |