Update wiki Home page for ms-exchange-online-imap-oauth-source

gitea_admin 2026-10-12 05:33:10 +00:00
parent 8b4cfe54c8
commit e3d97d651e

40
Home.md

@ -1,21 +1,33 @@
# Deploy the Project on CamelX Platform # Microsoft Exchange IMAP OAuth2 Source
Deploy on CamelX Platform in three steps Receive unread emails from an IMAP Microsoft Exchange mail server, marking them as read once they are received.
## Step 1: Create a release ## Metadata
From the project space, click on **"Create a release"**
The new version is automatically available in the list | Property | Value |
|----------|-------|
| Type | source |
| Group | Mail |
| Namespace | Mail |
| Support Level | Stable |
| Provider | Apache Software Foundation |
## Step 2: Deploy ## Properties
Click on **"Deploy"**
- **Version:** Select the desired release | Name | Type | Required | Default | Description |
- **Environment:** Choose `Development`, `Staging`, or `Production` |------|------|----------|---------|-------------|
- **Configuration:** Select the configuration source | `connectionHost` | string | | `outlook.office365.com` | The IMAP server host. |
- **Resources:** Set CPU and Memory | `connectionPort` | string | | `993` | The IMAP server port. |
| `tenantId` | string | ✓ | | Azure Active Directory Tenant ID. |
| `clientId` | string | ✓ | | Azure Active Directory Application Client ID. |
| `clientSecret` | string | ✓ | | The Azure Active Directory Application Client Secret. |
| `username` | string | ✓ | | The username to access the mail box. |
| `fetchSize` | integer | | `10` | The number of messages fetched for each poll (-1 for no limits). |
| `delay` | integer | | `60000` | The delay between fetches in milliseconds. |
## Step 3: Expose ## Dependencies
Enable **"Expose"**
Choose an **API Gateway** (Internal, Public, etc.) - `camel:core`
- `camel:kamelet`
- `camel:mail-microsoft-oauth`
- `camel:mail`