1.1.2 Released!

With this release, we have introduced support for adding the personal name of the sender.

We have introduced a new parameter named personalName that allows users to specify the name of the email sender. Please note that this parameter is optional. For more information, please refer Email Connector Documentation

1.1.1 Released!

With this release we have provided the support to send inline images in the HTML Content.

We have introduced a new parameter named inlineImages, which is an JSONArray to insert inline image details. There are 2 methods where the user can add images

1. Providing file path
2. Base64Content

Sample payloads are as follows

1. Providing file path

{
    "from": "[email protected]",
    "to": "[email protected]",
    "subject": "Sample email subject",
    "content": "<H1>Image1</H1><img src=\"cid:image1\" alt=\"this is image of image1\"><br/><H1>Image2</H1><img src=\"cid:image2\" alt=\"this is image of image2\">",
    "inlineImages": [
        {
            "contentID": "image1",
            "filePath": "/Users/user/Documents/images/image1.jpeg"
        },
        {
            "contentID": "image2",
            "filePath": "/Users/user/Documents/images/image2.jpeg"
        }
    ],
    "contentType": "text/html"
}

2. Base64Content

{
    "from": "abc@wso2com",
    "to": "[email protected]",
    "subject": "Sample email subject",
    "content": "<H1>Image1</H1><img src=\"cid:image1\" alt=\"this is image of a image1\"><br/><H1>Image2</H1><img src=\"cid:image2\" alt=\"this is a image2\">",
    "inlineImages": [
        {
            "contentID": "image1",
            "fileName": "image1.jpeg",
            "base64Content": "/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAY......"
        },
        {
            "contentID": "image2",
            "fileName": "image2.jpeg",
            "base64Content": "/9j/4AAQSkZJRgABAQEBLAEsAAD/4QBbRXhp...."
        }
    ],
    "contentType": "text/html"
}

1.1.0 Released!

With this release we have introduced OAuth2 Authentication for IMAP and IMAPS connections

Following are the set of introduced parameters to enable OAuth2 Authentication using email connector. These parameters can be provided using the integration studio.

Parameter	Description	Possible Values	Default Value	Required
enableOAuth2	Whether to enable OAuth2 Authentication	true, false	false	Default is set to false.
grantType	grant type	AUTHORIZATION_CODE, CLIENT_CREDENTIALS	-	Required if enableOAuth2Authentication is true
clientId	Value of the Client ID you obtained when you register your application	-	-	Required if enableOAuth2Authentication is true
clientSecret	Value of the Client Secret you obtained when you register your application	-	-	Required if enableOAuth2Authentication is true
tokenUrl	The token endpoint URL to generate access token	-	-	Required if enableOAuth2Authentication is true
scope	scope	-	-	Required if the grantType is CLIENT_CREDENTIALS
refreshToken	The refresh token generated	-	-	Required if the grantType is AUTHORIZATION_CODE

1.0.2 Released!!

This release adds support to add the attachment from payload.
e.g:

    "attachments": [{"name": "sampletextfile.txt", "content": "text content goes inside attachment"}, 
                    {"name": "sampleimagefile.png", "content": "iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg=="}]

1.0.1 Released!

This release adds support to establish connection with an SMTP server that does not require authentication.

1.0.0 Released!

This release supports IMAP, POP3 and SMTP protocols for working with emails. This release requires Integration Studio version 7.1.0 onwards for development and is compatible with EI version 7.1.0 onwards.