The SMTP send channel enables the connection to an email service. Messages from the message basket (outgoing) are sent to EDI participants via the e-mail account stored in the communication channel.
For the setup and configuration of “OAuth 2.0. with Office 365” see: Setting Up OAuth Client Authentication via Microsoft 365 with eBiss.
Notes:
| Properties | |
|---|---|
| Name | Description |
| Name | The name of the channel |
| Channel type name | The Type of the channel |
| Message direction | For receive channels the direction of the received message (but require also for send channels) |
| Message box | The message box |
| Public | True if the channel should be visible in the sub node |
| Host m | Address of the e-mail server e. g. egate. pranke. com for the eGate service. |
| Port | SMTP port (preferably 25). |
| Authentication | With this option you can set whether authentication is required when logging on to the server. The authentication method is selected using a combo box (None, Optional, Required). |
| SSL handling | Here you can make settings regarding the use of the network protocol: SSL (Secure Sockets Layer). The SSL settings are selected using a combo box (None, Offer, Required). |
| Username m | User name of the email account holder1). |
| Password m | User password of the email account holder2). |
| OAuth client id | The OAuth 2.0 client id3) |
| OAuth client secret | The OAuth 2.0 client secret4) |
| OAuth server URL | The URL with the tenant, e.g. for office 365: https://login.microsoftonline.com/{tenetId}/oauth2/v2.0/token, where {tenetId} must be filled with your ID5). |
| OAuth authorization url | The OAuth 2.0 authorization link, e.g. for office 365: https://outlook.office365.com/.default 6) |
| Change logs | The changes to the element are logged. The logging is activated in the System settings, which is possible if a versioning license is available. |
| Properties (advanced) | |
| Name | Description |
| Sender validation | How the sender address should be validated |
| Default sender | The default sender |
| Recipient validation | How the recipient address should be validated |
| Default recipient | The default recipient |
| Immediate retries | Retries, used by send channels. For some receive channels, the number of pickup attempts. |
| Auto uncompress | Unpacking is only performed on the receive channel in the ChannelReceiver. This setting has no effect on the send channels. If enabled for the receive channel, the file is checked for the ZIP (GZIP) and PKZIP formats and unpacked during analysis. It only works if the compressed file contains exactly one file. |
| Use partner address | |
| Fixed sender address | The sender address can be entered here if option UseSenderAddressAsFrom has not been selected. |
| Recipients m | Attention, if the recipient is set, this will be used instead of the addresses from the partner! Multiple recipients can be separated by comma or semicolon. |
| CC m | Enter multiple e-mail addresses separated by ',' or ';' as CC addresses. |
| Reply to | If necessary, another recipient can be specified here for answering the e-mail. |
| BCC | Enter multiple e-mail addresses, separated by ',' or ';' as BCC addresses. |
| Send single attachments as body | |
| Content type | |
| SSL client cert PFX file | This option allows you to specify the path of the Pfx file. The file contains the private key to encrypt the message to be sent. |
| SSL client cert PFX password | Specification of the password to guarantee access to the Pfx file. The password specification depends on the configuration of the file. |
| Request notification | |
| Notification hash | |
| HELO/EHLO hostname | |
| Write log | |
For integration with eGate. pranke. com via SMTP, ports 25 and 995 must be open outgoing.