...
Transport Input Parameters
| Parameter Name | Description |
| to | The user to add to the email TO field. |
| cc | The user to add to the email CC field. |
| bcc | The user to add to the email BCC field. |
| toList | The list of users to add to the email TO field. |
| ccList | The list of users to add to the email CC field. |
| bccList | The list of users to add to the email BCC field. |
| host | The host name of the email server. |
| port | The port to use to connect to the email server. |
| forceSSL | Forces the email to be sent using SSL. Valid values are "true" or "false", default is "false". |
| sender | The email address to use for the sender of the email. |
| subject | The text to send as the email subject. |
| body | The content to send in the email. |
| emailFormat | Format can be "text" or "html", default is "text". |
| user | The user id to use for the user sending the email. |
| password | The password for the user specified. |
Transport Output Parameters
| Parameter Name | Description |
| errMessage | If the service fails the reason for the failure is available from this parameter. |
Design Considerations
The reason that FEB as of 8.6.2) does not allow a user to redefine the sender of an email is because it can pose a security risk. Depending on how the email server is configured a user could potentially send an email as someone else. This custom transport passes the control from the FEB server to the application designer. If you are going to use this service (or one like it) then you need to make sure that your form designers understand the concerns associated with it.
...