Show Table of Contents
13.7.16. E.-Mail WireTap
| Class | org.jboss.soa.esb.actions.routing.email.EmailWiretap |
Table 13.29. E.-Mail WireTap Properties
| Property | Description |
|---|---|
| host |
The host name of the SMTP server. If not specified, will default to the property 'org.jboss.soa.esb.mail.smtp.host' in jbossesb-properties.xml.
|
| port |
The port for the SMTP server. If not specified, will default to the property 'org.jboss.soa.esb.mail.smtp.port' in jbossesb-properties.xml.
|
| username |
The username for the SMTP server. If not specified, will default to the property 'org.jboss.soa.esb.mail.smtp.user' in jbossesb-properties.xml.
|
| password |
The password for the above username on the SMTP server. If not specified, will default to the property 'org.jboss.soa.esb.mail.smtp.password' in jbossesb-properties.xml.
|
| auth |
If true will attempt to authenticate the user using the AUTH command. If not specified, will default to the property 'org.jboss.soa.esb.mail.smtp.auth' in jbossesb-properties.xml.
|
| from |
The "from" email address.
|
| sendTo |
The destination email account.
|
| subject |
The subject of the email.
|
| messageAttachmentName |
The filename of an attachment containing the message payload (optional). If not specified the message payload will be included in the message body.
|
| message |
A string to be prepended to the ESB message contents which make up the e-mail message (optional).
|
| ccTo |
Comma-separated list of email addresses (optional).
|
| attachment |
Child elements that contain file that will be added as attachments to the email sent.
|
<action name="send-email" class="org.jboss.soa.esb.actions.routing.email.EmailWiretap">
<property name="host" value="smtpHost" />
<property name="port" value="25" />
<property name="username" value="smtpUser" />
<property name="password" value="smtpPassword" />
<property name="from" value="jbossesb@xyz.com" />
<property name="sendTo" value="systemX@xyz.com" />
<property name="subject" value="Important message" />
</action>
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.