MailTo parameters¶

When implementing an integration use case that requires the capability to send emails (via SMTP) or receive emails (over POP3 or IMAP), you can use the following parameters in your proxy service artifact.

Info

MailTo transport can be used only if the transport listener and sender are enabled and configured at the server level. Read about the MailTo transport.

To add service-level transport parameters to a proxy service:

Open your proxy service artifact in MI VS Code extension.
In the Design View, click on the Edit button and expand the Advanced Options section and navigate to Service Parameters.
Click the Add Parameter text button to open the following form to add the parameter name and value as a key-value pair:

See Creating a Proxy Service for instructions.

Service-Level parameters¶

Parameter Name	Description	e.g.Required	Possible Values	Default Value
`transport.mail.Address`	The mail address from which this service should fetch incoming mails.	Yes	A valid e-mail address
`transport.mail.bodyWhenAttached`	The content of the body of the mail when sending a mail with an attachment.	No	The text you want to appear in the mail body
`transport.mail.Folder`	The mail folder on the server from which the listener should fetch incoming mails.	No	A valid mail folder name (e.g., inbox)	inbox folder if that is available or else the root folder
`transport.mail.Protocol`	The mail protocol to be used to receive messages.	No	pop3, imap	imap
`transport.mail.PreserveHeaders`	A comma separated list of mail header names that this receiver should preserve in all incoming messages.	No	A comma separated list
`transport.mail.RemoveHeaders`	A comma separated list of mail header names that this receiver should remove from incoming messages.	No	A comma separated list
`transport.mail.ActionAfterProcess`	Action to perform on the mails after processing them.	No	MOVE, DELETE	DELETE
`transport.mail.ActionAfterFailure`	Action to perform on the mails after a failure occurs while processing them.	No	MOVE, DELETE	DELETE
`transport.mail.MoveAfterProcess`	Folder to move the mails after processing them.	Required if ActionAfterProcess is MOVE	A valid mail folder name
`transport.mail.MoveAfterFailure`	Folder to move the mails after encountering a failure.	Required if ActionAfterFailure is MOVE	A valid mail folder name
`transport.mail.ProcessInParallel`	Whether the receiver should process incoming mails in parallel or not. This works only if the mail protocol supports processing incoming mails in parallel. (e.g., IMAP)	No	true, false	false
`transport.ConcurrentPollingAllowed`	Whether the receiver should poll for multiple messages concurrently.	No	true, false	false
`transport.mail.MaxRetryCount`	Maximum number of retry operations to be performed when fetching incoming mails.	Yes	A positive integer
`transport.mail.ReconnectTimeout`	The reconnect timeout in milliseconds to be used when fetching incoming mails.	Yes	A positive integer