> ## Documentation Index > Fetch the complete documentation index at: https://docs.maia.ai/llms.txt > Use this file to discover all available pages before exploring further. # Send Email export const ComponentMetadata = ({warehouses, unsupportedWarehouses = [], componentType, connectionInputs, connectionOutputs}) => { const allWarehouses = [...warehouses.map(w => ({ name: w, supported: true })), ...unsupportedWarehouses.map(w => ({ name: w, supported: false }))]; return

Project Availability	{allWarehouses.map((w, i) => {w.name} {w.supported ? '✅' : '❌'} )}
Component Type	{componentType}
Connection Inputs	{connectionInputs}
Connection Outputs	{connectionOutputs}

; }; The Send Email component allows users to send emails—with or without attachments—via an orchestration pipeline. Users may wish to use this component to send email notifications upon any pipeline failures. Some SMTP servers will not allow the Sender Address property to be different from the SMTP Username (for example, Outlook and Gmail). This means that whatever is shown in the SMTP Username property will be used as the value of the "From" when the email is sent, and the Sender Address property will be ignored. This is beyond our control. Depending on your configuration, it is safest to assume that email is an unencrypted medium. Therefore, it is recommended to avoid including sensitive content in the email Message. Instead, it is recommended to provide trusted URLs through which such context could be securely accessed. Depending on the SMTP server, users may need to have Enable SSL/TLS set to Yes and Enable StartTLS set to No, and vice versa. ## Properties A human-readable name for the component. {/* */} Click **+** to add a recipient to send the email to, and then type the recipient's email address into the field. Each recipient must be its own row. {/* */} Click **+** to add a recipient to send a carbon copy of the email to, and then type the recipient's email address into the field. Each Cc recipient must be its own row. {/* */} A subject for the email. {/* */} The contents of the email body. To use variables in this field, type the name of the variable prefixed by the dollar symbol and surrounded by \{ } brackets, as follows: `${variable}`. Once you type `${`, a drop-down list of autocompleted suggested variables will appear. This list updates as you type; for example, if you type `${date`, functions and variables containing `date` will be listed. {/* */} The email address from which the email is sent. {/* */} The address that will receive any recipient and/or Cc replies. {/* */} The username for your SMTP client. {/* */} Choose the secret definition that represents your credentials for this connector. If you have not already saved your credentials for this connector as a secret definition, click **Add secret** to create a secret definition representing these credentials. Read [Secrets and secret definitions](/docs/guides/secrets-and-secret-definitions) for details about creating a secret definition. {/* */} The host address for your SMTP server. For example, if you use Gmail, the SMTP hostname is smtp.gmail.com. Typically, an SMTP email server address can be found in the "account" or "settings" sections of the email client. {/* */} Set the port. The default port is 25. {/* */} Select whether to enable SSL/TLS encryption. {/* */} StartTLS is an email protocol command that directs an email server that an email client, including an email client running in a web browser, wants to turn an existing insecure connection into a secure one. {/* */} Search for the file in the S3 bucket you want to attach—rather than manually entering the file path—or select a file from the list of available S3 buckets. The URL must be formatted as follows: ``` // ``` The `S3:` prefix isn't required, but will be accepted: ``` S3://// ``` [Project and pipeline variables](/docs/guides/variables) can also be used. This is particularly useful when using them in the URL, for example: ``` ${account}/${containerName}/${path}.${filetype} ``` The file attachment is limited to *one* file and must *not* exceed 10 MB in size.